RE: [platform-releng-dev] releasing to HEAD for 3.0.1 and 3.1

[<eclipse@xxxxxxxxxx>]

I think most users would split the development at the 3.0 tag, and develop
either 3.1 or 3.0.x in a branch and the other in head. Mixing the two is
very confusing.
You cannot hold people for a long time from committing the changes, or they
will
create private branches that will only add to confuston.

I believe it would be easier for everybody to understand the project
development 
if 3.0.1 branch would start at 3.0 tag.

Genady

> -----Original Message-----
> From: Mike Wilson [mailto:Mike_Wilson@xxxxxxxxxx] 
> Sent: Tuesday, June 29, 2004 10:03 PM
> To: platform-releng-dev@xxxxxxxxxxx
> Subject: Re: [platform-releng-dev] releasing to HEAD for 3.0.1 and 3.1
> 
> Or you could pull the code and put it in a branch now.
> 
> McQ.
> 
> 
> 
> 
> Jared Burns <jaredburns@xxxxxxx> 
> Sent by: platform-releng-dev-admin@xxxxxxxxxxx
> 29/06/04 15:46
> Please respond to
> platform-releng-dev
> 
> 
> To
> platform-releng-dev@xxxxxxxxxxx
> cc
> 
> Subject
> Re: [platform-releng-dev] releasing to HEAD for 3.0.1 and 3.1
> 
> 
> 
> 
> 
> 
> Too late. :(
> 
> Our team's already been releasing new code to HEAD.
> 
> I don't see how this could really be a problem, though. We'll just
> create the 3.0.1 branch off the 3.0 version (if needed).
> 
> - Jared
> 
> On Tue, 2004-06-29 at 11:08, Jim des Rivieres wrote:
> > Reminders:
> > 
> > - Do not release new functionality or API into HEAD at this time.
> > 
> > - Only release to HEAD those changes that you intend to end 
> up in both 
> the 
> > next maintenance release (3.0.1) and the next major release (3.1). 
> > 
> > - Maintenance releases are intended to address serious 
> problems that are 
> 
> > blocking product teams building atop Eclipse. Maintenance 
> releases are 
> not 
> > an appropriate place to introduce new functionality or API. 
> > 
> > - The 3.0.* maintenance release schedule is here:
> > 
> http://eclipse.org/eclipse/development/eclipse_maintenance_sch
edule_3_0_x.html

> 
> - At some point down the road once the 3.1 plan is in place, we will be 
> creating a separate CVS branch just for the maintenance release work.
> 
> _______________________________________________
> platform-releng-dev mailing list
> platform-releng-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev