RE: using R- as a prefix to release number (especially if adding "RELEASE" as a tag that always points to the LATEST RELEASE):
Note that the "RELEASE" tag will move: it essentially will be re- tagging at each release. As relases move along, having a "R-" prefix will leave past releases marked conspicuously. If ONLY releases will be tagged, this might be superfluous - BUT is patches, or test posts are (at any point in the future) tagged, then a way to clearly, unambiguously be able to find Release tags will be important. There may be other ways to approach this, but this is common, simple, allows tagging a release as beta, release candidate, and (potentially) release, without the need to add any revisions, for example: B2-1.99.99, RC-1.99.99, and R-1.99.99 might all be different changesets - OR the same changeset that passed all these gates. The discussion of a tag format of the form: [Release state]-[Release number] is useful. It should not be mixed up with discussion of having ONE tag which always marks the latest release - these are separate concerns. Hope that helps clarify. Regards, - Yarko On Apr 20, 11:27 am, mdipierro <[email protected]> wrote: > This is easier than I thought. Thanks to yarko for insisting about > this. Please make sure I do it properly. > > On Apr 20, 10:27 am, Thadeus Burgess <[email protected]> wrote: > > > You mean, I will finally have a way to run stable versions of web2py > > but easily update them !? w00t! > > > -- > > Thadeus > > > On Tue, Apr 20, 2010 at 12:26 AM, Yarko Tymciurak > > > <[email protected]> wrote: > > > heckings, so you can ALWAYS get the latest release from Goog > > > -- > > Subscription settings:http://groups.google.com/group/web2py/subscribe?hl=en
