[parted-edge] [Parted-edge] [RFC] Proposal: 1.9.0 release as stable

David Cantrell dcantrell at redhat.com
Mon Nov 5 03:49:22 UTC 2007


On Fri, 02 Nov 2007 19:34:53 -0200
Otavio Salvador <otavio at debian.org> wrote:

> Hello,
> 
> Today I did a look on the changes we have on master and they're really
> small comparing with stable branch. It looks like we'll take years to
> release this code if we don't change our plans now and then I propose
> the following:
> 
>  - work on history patch from Matt;
>  - check API and hide architecture and disk specific things as
>    possible;
>  - release 1.9.0 as stable

I completely agree with this idea.  Release often, release early.

> Once it's done, I think we ought to change the way we work to _aways_
> use stable-1.9.x (since it's going to be the stable one) as work basis
> and after every stable release, merge it on master.

I'm not sure that work flow makes the most sense.  I think we should be using master for the main work (even for stable) and when we do a new major release (as in, a new parted-X.Y.0 release), make a branch from that.

Major new overhauls should be done as branches from master and then merged in right away.  The stable branches will receive the minor bug fixes and we can roll those back to master.  But the focus should be on master.

> The things that we ought to start to work for "next master" could be:
> 
>  - new VFS
>  - new command line utility using modules
>  - spliting of fat code on a library

I think all of these should be worked on, but as branches off master and then rolled back in when they are ready.  A new command line utility (please, someone say a replacement for the parted(8) utility) is a good example.  Work on that, when it's ready, it gets merged in to master.

-- 
David Cantrell <dcantrell at redhat.com>
Red Hat / Westford, MA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/parted-edge/attachments/20071104/881194cb/attachment.pgp 


More information about the parted-edge mailing list