----- Original Nachricht ---- Von: Merlijn van Deen <[email protected]> An: Pywikipedia discussion list <[email protected]> Datum: 10.08.2013 16:21 Betreff: Re: [Pywikipedia-l] Release number under git/gerrit
> Hi xqt and dr. trigon, > > On 1 August 2013 13:33, <[email protected]> wrote: > > > Hi folks, > > > > unfortunately the git Id numer is not a sequential release number as in > > svn but a hash. I find it a good idea to have a release number in the > code > > as it was before git migration. A git statement generates it: > > > > git rev-list HEAD | wc -l > > > > which is the revision number. A better idea would be the gerrit number > > which gives us the last and actual change for that code. It is posible to > > merge such a number to the __version__ header of the script instead or in > > addition to the hash? > > > > > Although this is possible, I'm not sure what we gain by doing this - is the > problem the length of the hash? Or do you want a number that increases? If > so - why? > > I see it can be useful to quickly determine how old someone's version is, > but we can add logic to version.py to do that (e.g. including date). In my > experience, it was never very useful to see who touched a file for the last > time - and it's quickly available using git log <filename> (although this > might be harder on windows?) > > Merlijn > The has is unwieldy and in past there where a lot of cases like "... it worked with release 3815 but it failed after 4711". Unfortunately the repository log only shows the hash and not any chronological number. I believe I still perserve in the old svn workflow and I probably have to rethink these things. xqt _______________________________________________ Pywikipedia-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
