A few years ago, in Ozon, it could take three months between two releases of an application on the same platform. We planned that we want to release with a certain big feature and until we do it, we will not release it.
What we encountered while releasing releases according to this scheme:
It is difficult to predict when the feature will be released . Ok, we somehow figured out the deadlines, but the more the developed functionality was, the more difficult it is to accurately estimate the deadline. Tracking the progress of a feature is also not very convenient, because “it's done there” , and intermediate builds with something ready “to watch” are difficult to assemble.
Long time to fix bugs . In code, they can be fixed quickly. But the fix comes to users with the same global feature.
It hurts to turn off legacy . We must wait until the number of users on the new versions is already large enough. With rare updates, it sometimes takes years to wait.
. - , . , , «», .
. , , , , , , … , …
. , . . - , – (, - ).
, . «» , – . , : « … ».
:« , , Apple -- . , , , ?». : “ ”.
:
, .
. . , 1 , 1 .
, . , . . .
. , . , . , .
. . , . . : , , . , , — . , , . -.
: -
, , . , ... . – ! , - .
…
– .
, - :
.
– , .
«» .
.
: , – . . , . «», , , , .
QA. , .
, . , , , – .
– !
. :
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
«-». , , , develop. dev, . , – . , , . , - - . |
QA, . , – , . - .
- , - , .
, , –
;
;
.
- – .
, . :
.
( , ).
, . , , , – .
. , . , , . , dev.
, - , .
. – in progress. merge request – code review. review – QA.
, .
UI- . «» merge request. Jira.
merge request dev Jira. , . , .
QA Notes
QA Notes. :
.
.
.
.
— , - ( , ).
QA Notes . : QA - .
. QA . , . . , . .
. , . dev, . , - dev. – .
, QA , . .
«QA ». - – :
.
. , , – - .
.
-, - .
.
, , .
:
, :
. - , , . . -, . -, - , , , .
. , , , .
. , -, , ( – :) ).
. . . – . Ozon , , .
. , . -, «» dev, .
– , - . , .. - . . , .
. , . . . – , -.
. . .
, , :
.
.
.
.
, , , : , , .