The ca2 software development process is quite loosely-coupled.
It means it is used as a guiding rule, masterly guided by the main subjectivity: love and wellfare for all.

Pay attention to the following picture and to the following explanation:

basis means the main branch and the creative work, of development, tests, enhancements made upon it.

stage means the release branch and the work of small and specif corrections and localized tests.

The temperature - with red color - indicates the level of modifications, of creative works that are inserted in a same period of time to the main branch.

It is indicated in red to show that it is in the basis that are made the great changes. And that it passes by a phase of new features insertion. And after it, passes by a phase of cooling and polishing, to generate a new release.

After it is "very cooled", the work in basis is released in a new stage. The past stage exists, but it s not supported anymore and does not receive changes anymore.

At stage, it is done only small corrections - bug fixes.

The official ca2 process is restricted to this.

Certain compensatory mechanisms - generally used to attend specific needs of s specific end user - or heavier creative works may be necessary in branches that live parallel to basis. So care should be taken to avoid too much delay to return from the derivd branch to basis, because the quantilty and level of the changes in basis may lead to a hard-to-do merge, requiring a lot of work, or may be practicaly disabling the generated work by the new ideas, requiring then a rework based on the ideas - instead of also reusing the work.

>> join: developer.camilothomas.com

1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	1	2	3	4	5

UTC