On Dec 22, 2010, at 8:01 PM, Luther Goh Lu Feng wrote: > > To clarify, what I am saying is, no change to current release system, > except to label stable and testing branches. It's a little like the > branches of Debian Linux > http://wiki.linuxquestions.org/wiki/Debian#Stable.2C_Testing.2C_Unstable.2C_and_Experimental
It requires some kind of change, since we'd need a branch for the release and the trunk for continued development. A simple mechanism is to have the trunk (unstable) be 1.90.0, 1.91.0, 1.92.0, ... From each of those, we branch from (for example) 1.91.0 to 1.91.1, 1.91.2, ... for bug fixes only: stable. Not all of the stable branches would be maintained indefinitely. The mechanism is simple, but patches to the trunk would have to be single-subject, and identified a little better as to content. > > web2py probably don't need so many branches. > > On Dec 23, 11:52 am, Luther Goh Lu Feng <elf...@yahoo.com> wrote: >> I think the suggested versioning works great >> >> What I suggest is perhaps label the latest release as the testing >> branch eg 1.91 is the testing branch. 1.90 will be the stable branch. >> These will of course increment by 0.01 in the next web2py release. >> >> In the admin panel, have the option for the user to upgrade/downgrade >> to/from the testing/stable branches. >> >> On Dec 23, 11:07 am, VP <vtp2...@gmail.com> wrote: >> >> >> >> >> >> >> >>> In my humble opinion, the word "Enterprise" demands a more systematic >>> approach to dealing with this issue. I think the simplest way is >>> perhaps has a numbering scheme that is understood by everyone. For >>> example, increment the third number (e.g. from 1.90.2 to 1.90.3) only >>> for bug fixes, and increment the second number (e.g. from 1.90.3 to >>> 1.91.0) for major releases or addition of new features.
