Re: [e4-dev] [releng] Next week is 0.9 M4 week

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

When I created this schedule, I just
thought we would redefine what kind of change is acceptable at particular
points in the end-game. I.e., if we're still adding features and API during
the RC period, that would be fine. I'm sure we won't have the same number
of test passes as 3.x, so much of that end-game period would still be free
for doing real development. Anyway, if the consensus is to change the schedule
that's fine with me. We can also add a week by using the last week of July,
since there is no coordination with other projects to worry about.

John

Kevin McGuire/Ottawa/IBM@IBMCA
Sent by: e4-dev-bounces@xxxxxxxxxxx

06/08/2009 02:35 PM

Please respond to
E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>

To	E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
cc
Subject	Re: [e4-dev] [releng] Next week is 0.9 M4 week

Just to clarify what I was proposing wrt schedule:

Current: 
M4 06/19/2009   0.9M4 (Feature Freeze) 
RC1 07/03/2009   0.9RC1 
RC2 07/10/2009  0.9RC2 
RC3 07/17/2009  0.9RC3 
RC4 07/24/2009  0.9RC4 

Proposed: 
M4 07/10/2009   0.9M4 (Feature Freeze) 
RC1 07/17/2009  0.9RC3 
RC2 07/24/2009  0.9RC4 

Boris and I discussed briefly whether we should add M5 so that M4 doesn't
stretch so long.  My feeling is that for many of us we effectively
just started M4 so adding another milestone is of limited value.  However,
since we're not doing one week of test/fix/etc. with the milestones, I'm
ok adding an M5 under the belief that adding a milestone removes nothing
from our development pace. 

Kevin

Kevin McGuire/Ottawa/IBM@IBMCA
Sent by: e4-dev-bounces@xxxxxxxxxxx

06/08/2009 02:20 PM

Please respond to
E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>

To	E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
cc
Subject	Re: [e4-dev] [releng] Next week is 0.9 M4 week

Great! What would you suggest as an end game approach?
A) What I proposed (take two weeks away from RC and move to M4)
B) One week only of RC at the end?
C) Hack like mad until last minute (actually, I like this one <g>)
D) Other? 

Kevin

Boris Bokowski/Ottawa/IBM@IBMCA
Sent by: e4-dev-bounces@xxxxxxxxxxx

06/08/2009 02:08 PM

Please respond to
E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>

To	E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
cc
Subject	Re: [e4-dev] [releng] Next week is 0.9 M4 week

+1 on not doing the usual Eclipse end game for e4 0.9. We should be building
a tech preview, not a stable product.

Boris

e4-dev-bounces@xxxxxxxxxxx wrote on 06/08/2009 02:05:33 PM:

> 
> >Since we are approaching our 0.9 M4 (feature freeze) next week
> 
> I'd like us to discuss whether we believe we should be applying the
> normal Eclipse shutdown pattern to e4.  That pattern is in place
to 
> ensure that we ship a stable framework which products can, with high
> confidence, build on.  We purposely trade innovation for stability.
> 
> However, e4 is an incubator. As such, its goal *is* innovation with
> no product level promises of stability. 
> 
> I believe this shutdown process will prematurely force us to 
> converge on what we basically have today. Those of us working on 3.x
> are only now able to move our focus to e4, just in time for there
to
> be no time. 
> 
> My specific suggestion is to eliminate RC3 and RC4, moving the two
> weeks to the front, so M4 in +2 weeks, etc.  That should give
us 
> some period of stabilization to ensure say we don't bust the demos
> in the 11th hour, but still provide some runway to do new work. 
> 
> I am open to other suggestions.  Your thoughts? 
> 
> Kevin 
> 
> 

> 
> Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx> 
> Sent by: e4-dev-bounces@xxxxxxxxxxx 
> 06/08/2009 01:08 PM 
> 
> Please respond to
> E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
> 
> To
> 
> E4 Project developer mailing list <e4-dev@xxxxxxxxxxx> 
> 
> cc
> 
> Subject
> 
> [e4-dev] [releng] Next week is 0.9 M4 week
> 
> 
> 
> 
> http://www.eclipse.org/projects/project-plan.php?projectid=eclipse.e4
> 
> Since we are approaching our 0.9 M4 (feature freeze) next week and
I
> have platform downloads for win32, linux gtk, and macosx cocoa (all
> x86) I've started I builds every night.  Because they are I-builds
you
> will need to release changes to see them in the nightly build:
> http://wiki.eclipse.org/E4/Builds
> 
> I'll be updating our builds to comply with
> http://wiki.eclipse.
> org/Development_Resources/HOWTO/Conforming_Incubation_Branding.
> I'll try to announce any changes on the e4-dev@xxxxxxxxxxx mailing
> list.
> 
> I'll be posting a couple of updates and reminders over the next 2
> weeks.   It's important that we act on them sooner, rather than
later
> so we are in good shape for next week.
> 
> PW
> 
> 
> -- 
> Paul Webster
> Hi floor.  Make me a sammich! - GIR
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev