← Back to team overview

oship-dev team mailing list archive

Re: Releases

 

On Fri, 2009-05-22 at 00:41 +0200, Roger Erens wrote:

> I would favor to have some trunk snapshot (a 'revision') be tagged 
> 'version-1.0a1' or whatever label you like. And skip the trouble of 
> exporting to a tar.gz release.
> 
> Roger


Thanks for the feedback.  I have to say that I agree with all of your
comments. 

Now for the work part.

There are a number of Blueprints that I have assigned to release 1.0  
Of course that means 1.0b1 - feature freeze, looking for bugs.  

So, where are the breaks in features that we need for 1.0a(xxx) tags?  
IMHO, if we are going to have these then they need to be discussed and
planned.  Then they (the Blueprints) should be attached to those release
tags so developers can easily look and see what they are supposed to be
building against and testing.  

Do you (the collective you) want me to be solely responsible for making
those determinations?  I can and will.  I would prefer your input
though.

Cheers,
Tim

Attachment: signature.asc
Description: This is a digitally signed message part


Follow ups

References