Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [e4-dev] [releng] Next week is 0.9 M4 week

I don't feel strongly about it. The *rate* at which we try to converge is a separate question from when we start the process; I certainly believe we will be allowing much more radical/dangerous changes close to the e4 0.9 ship date than we would in the comparable R3.5 timeframe.

I do think we need to treat the fact that _we_are_going_to_ship_something_ seriously, though.

McQ.

Inactive hide details for Kevin McGuire---08/06/2009 14:05:57--->Since we are approaching our 0.9 M4 (feature freeze) next weekKevin McGuire---08/06/2009 14:05:57--->Since we are approaching our 0.9 M4 (feature freeze) next week


From:

Kevin McGuire/Ottawa/IBM@IBMCA

To:

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

Date:

08/06/2009 14:05

Subject:

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





>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



GIF image

GIF image


Back to the top