[Nagiosplug-devel] RFC: making a 1.4.1 release?

[sean finney]

On Wed, Jul 06, 2005 at 06:53:49AM +0100, Ton Voon wrote:
> The idea is that major enhancements or breakages are put into  
> CHANGES. This is the high level "what's in a new release". The  
> ChangeLog is the detailed changes from comments in CVS.

aha...

> So I think you are saying:
> 
> - stay with r1_4 and HEAD
> - bugfixes and security updates to r1_4, all other development to HEAD
> - create a r1_5 branch from HEAD at some point (so there is r1_4,  
> r1_5 and HEAD)
> - release r1_5
> - close r1_4 at some point

more like

 - stay with r1_4 and HEAD
 - bugfixes and security updates to r1_4, all other development to HEAD
 - close r1_4 at some point
 - create a r1_5 branch from HEAD at some point (so there is r1_5 and HEAD)
 - release r1_5

the idea being that we close up shop and store away 1.4.x for good at
some point, that point being shortly before officially starting work on
making a new 1.5.x series.

> I have a (maybe oversimplified) equation in my head where "more  
> branches" = "more work", so I'm trying to keep the number of branches  
> to two.

i'd say that's probably a good idea.  no reason not to also tag versions
to any of the 1.4.x and 1.5.x point releases as well, but i think two
actively maintained branches (one stable, one development) is ideal.


	sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://www.monitoring-plugins.org/archive/devel/attachments/20050705/b855f808/attachment.sig>