← Back to team overview

gtg team mailing list archive

Re: Release and dev process

 

We really need a wiki I think.

Le dimanche 08 mars 2009 à 23:30 +0100, Bertrand Rousseau a écrit :
> Ok, I'm fine with this. I think we need a "development" page on our
> website to store such information.
> 
> On Sun, Mar 8, 2009 at 11:55 AM, Lionel Dricot <ploum@xxxxxxxxx> wrote:
> > Hello,
> >
> > This is how I see the dev/bug fixing/release process from now.
> >
> > 1) When developing, always put in CHANGELOG a little explanation about
> > your change and the number of fixed bugs.
> >
> > 2) When commiting a bug fix, mark the bug as "Fix commited" (not fix
> > released)
> >
> >
> > Loop on this until we decide for a release
> >
> > Release :
> >
> > 3) Create a milestone for this release if it doesn't exist yet.
> >
> > 4) Take all the bug marked as "Fix commited" and assign them to the
> > milestone. This way, if we are releasing an unexpected 0.1.1, even if we
> > fixed a bug due for 0.3 the bug will appear fixed in 0.1.1.
> >
> > 5) Do the release. In the release note, include a link to the bug
> > related to this milestone. For 0.1, it would have been :
> > https://edge.launchpad.net/gtg/+milestone/0.1
> > (but this one is not complete are we closed several bugs without
> > assigning them to 0.1)
> > So, when reading the release note, people have a quick access to the
> > list of bug fixed in a particular release.
> >
> > 6) Mark all "Fix commited" bugs as "Fix released".
> >
> > 7) Do the GTG dance
> >
> > Lionel
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~gtg
> > Post to     : gtg@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~gtg
> > More help   : https://help.launchpad.net/ListHelp
> >
> 
> 
> 




References