I tag them 1.XX.YY but I do not put the R in front. I use in fact the logs to manually extract important changes and edit the README files used to build the changelog above. Not completed automated yet.
On Apr 9, 4:25 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com> wrote: > On Apr 9, 4:16 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > I did follow the advice you gave me some time ago: > > >https://www.web2py.com/examples/default/changelog > > Ah - yes, to reverse the order of release comments (for most recent at > the top); very nice... thanks.... > > I don't know what your personal process is for checkin / push, but if > you tagged released versions before pushing to google code, that would > be a useful marker also. > > Regards, > - Yarko > > > > > On Apr 9, 2:11 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com> > > wrote: > > > > On Apr 9, 2:09 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com> > > > wrote: > > > > > Massimo: > > > > > I don't see that you have checkins in your Makefile, but if you made a > > > > "release" that used your "mdp" entry - that is, after hg commit, but > > > > before hg push, add something like this in what you do: > > > > > hg tag $(cat VERSION | python -c 'import sys; print > > > > sys.stdin.readline().split()[1]') > > > > > (or whatever way you want to get that "1.76.5" part out of the > > > > VERSION file). > > > > Just to be clear: For this to be useful, it would have to be for > > > released versions; You could also come up with some other > > > convention, such as released versions starting with "R", e.g. > > > R-1.76.5 > > > > The point is to TAG actual releases in some useful way in the > > > repository. > > > > > This would allow people to see what changed since a release in the > > > > repository browser (as well as checkout specific versions, and make > > > > tests). > > > > > Regards, > > > > - Yarko > > > > > On Apr 9, 1:29 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > > >http://web2py.com/examples/static/<xxx>/web2py_src.zip > > > > > > <xxx> is one of > > > > > > 1.67.2: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.68.2: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.71.2: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.72.3: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.73.1: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.74.11: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.74.9: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.75.4: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.76.1: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.76.2: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.76.3: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.76.4: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.76.5: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.76.5.1.b: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.76.5.2.b: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.76.5.3.b: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > 1.76.5b: > > > > > web2py_osx.zip web2py_src.zip web2py_win.zip > > > > > > On Apr 9, 1:25 pm, 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.
