I need to be educated. Here is my problem. I gave myself a rule of tagging releases as 1.XX.YY. The fact is that I commit before I build the binaries. It occasionally happens that I commit 1.XX.YY, build the binary and then I discover a problem (for example a file was missing because I forgot to hg add it). So I make the change and I commit again with the same tag. I can put the R in front as you suggest but this is not going to avoid this occasional problem.
In the recent times I have automated the build process of binaries and these errors are going to be minimized if not disappear and release tags will be unique as you suggest. Massimo On Apr 9, 7:52 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com> wrote: > On Apr 9, 7:31 pm, Richard <richar...@gmail.com> wrote: > > > alternatively you could check out specific versions from the mercurial > > repository:http://code.google.com/p/web2py/source/checkout > > I just browsed through the comments, pages of commits to find 3 > comments that say 1.76.4. > > I assume these are the release (and the latest one is it). > > If I have a client w/ 1.65.1, I have a lot of paging / date guessing > to go thru. > > That is why tagging release would be a good thing, and a service to > the community: I would be able to checkout by tag, and just get the > right thing. > If I wasn't sure of the right thing, I could check the hgtags file and > see what the significant checkins (i.e. the tagged ones) were. > > I am surprised this even elicits discussion, alternatives, rather than > simple agreement. > > - Yarko > > > > > On Apr 10, 4:25 am, Kenneth <kenneth.t.lundst...@gmail.com> wrote: > > > > Is there a place where I could download older versions of web2py? > > > Source version. > > > > I get still problems with the new version and can´t understand why. So > > > I thought that by trying to upgrade one version a time I could maybe > > > find out whats the problem. > > > > Kenneth -- To unsubscribe, reply using "remove me" as the subject.
