Hi Christophe, Le lundi 09 janv. 2012 à 08:10:18 (+0100 CET), Christophe Monniez a écrit : > Le samedi 07 janvier 2012 à 17:10 +0100, Julien Valroff a écrit : [...] > > BTW, is there any good reason you use git-dch? I find it very hard to follow > > the work because of it (but may be due to the fact I am not used to using > > it). > > Well, I have no good reason to use it. We really should update our > workflow to see who works on what.
Does it really matter? I am OK to work on any package but I do not use all of them which explains why I always prefer a regular user tests the changes I have made before uploading. The packages for which I am an uploader means I use it and I am OK to take care of it on a regular basis (ie. follow upstream development, package new releases, fix bugs ASAP etc.). But if someone of the team steps up and upload such a package before I can do it, I am perfectly fine with it. Maybe what we should do is make sure nobody else works on a given package before doing it ourselves (this would avoid duplicate work, but I do not think it has happened in the recent past). > It was once said that it's up to the uploader to maintain the changelog > because it's automatically generated by git (I suppose git-dch). > So, when I work on a package, I don't update the changelog, to not > interfere with the uploader work. > > Am I wrong ? What is the "good" way of doing it ? I am not used to using git-dch and *I* think it is not needed in our workflow, but I was not aware of the discussion you already had on this point. Remember I am new in the team, and still must have to learn your habits ;) Sorry if I have broken these rules. Now, my question was also on a practical level: what do you see as advantage working with git-dch? I am personally used to debcommit which allows me to keep the standard workflow (eg. dch --team) while still making git commit logs useful. Cheers, Julien -- .''`. Julien Valroff ~ <[email protected]> ~ <[email protected]> : :' : Debian Developer & Free software contributor `. `'` http://www.kirya.net/ `- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1 _______________________________________________ forensics-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel
