One big release or a few small ones?

When you are working on improvements to your existing line of business applications, do you think it's better to translate changes to less frequent larger releases or constantly send new features to smaller versions? Assuming there are hardware updates or database updates, do you also make these changes in releases or keep them separate?

Everyone who has all the advantages has the advantage that in this case there are fewer problems with the business and less time to work, but any problem that you encountered later may be related to updating the database, hardware, or any number of software changes.

Exemption is small and often makes it easier to track any issues that arise as a result of the release, but leads to a greater failure and longer regression testing.

What's better?

+3
source share
7 answers

Consider how each issue affects customers. Will frequent small releases make them happier due to quick resolution of critical tasks? Will it improve your sales and reputation? If he will carefully evaluate if these advantages exceed the extra work, otherwise just follow the path that is more convenient for you.

+3
source

It really depends on the environment in which you are. Some scenarios:

: , , . , , . db.

" ": , .

, , -, , .

1-2 , .

+2

, : .

, "ajaxy" , , , "" . , .

, , , "", OR, , .

, , , - LESS , , , .

+2

.

, . , , , .

, :

+1

, , .

, , , . .

, , . , Adobe Photoshop, , , , .

+1

, . , . - , , , , , .

, . .

+1

- .
DEVEL RELEASE? REL . REL ​​ DEV ( : - REL , DEV , DEV, , , DEV REL).
When the development of the new version is completed, you will have to test the new features and patches ported from REL. If everything is in order, you can deploy a completely new large version and archive the current DEV in the REL, while the old REL will be closed.

0
source

Source: https://habr.com/ru/post/1708254/


All Articles