RE: [higgins-dev] Procedure for pushing fixes into 1.0

["Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx>]

Jim,

Here are my thoughts:

1) I think component owners need to gain the consensus on the higgins-dev
list for breaking changes. I think they can contribute bug fixes to a
release branch (e.g. 1-0-0) (in addition to, of course, putting the fix in
HEAD!) unilaterally. 

2) Weekly telecon calls. We expect to have release builds every 6 weeks or
so with intermediate "stable" builds as needed. Let's see how that goes and
adjust accordingly.

3) The HEAD will contain all fixes and be available in non-stable form until
#2 happens

BTW see my next email for my decision about version numbering.

-Paul
________________________________________
From: higgins-dev-bounces@xxxxxxxxxxx
[mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim
Sent: Friday, February 29, 2008 2:12 PM
To: Higgins dev <higgins-dev@xxxxxxxxxxx
Subject: [higgins-dev] Procedure for pushing fixes into 1.0

When we come across a bug that we feel needs to be also fixed in 1.0, what
is the procedure? 

1) Do we need to get some consensus on whether the fix really ought to be
pushed into the 1.0 branch? 
2) How will we decide when it's time to "ship" 1.0.x versions which will
contain these fixes 
3) Will 1.0.x versions be available in a non-stable form until #2 happens? 

Jim