Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Platform Juno SR2 freeze plan

Thank you Dani. I've made the changes you suggested.

Plus, I've now added the builds up to Kepler M5 (no nightlies, two I -builds per day) ... that's going to be a busy week!

Feedback/corrections welcome.




From:        Daniel Megert <daniel_megert@xxxxxxxxxx>
To:        "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>,
Date:        01/11/2013 07:48 AM
Subject:        Re: [eclipse-dev] Platform Juno SR2 freeze plan
Sent by:        eclipse-dev-bounces@xxxxxxxxxxx




Yes, the Friday build is meant to be an extra (final) test candidate build for the Monday January 28 RC3 test pass. Also, after that test pass, some fixes might have to be made and a build be needed. It's usually easier if the build time is known rather than having to jump on a requested build. So, we should just keep the known rhythm, except for the extra RC3 build.

I would do the sign-off for RC2 earlier than Thursday January 24, e.g. Tuesday. For RC3 we can't do it earlier than Thursday since we also have to deliver Kepler M5 in that week,.


Dani

From: David M Williams <david_williams@xxxxxxxxxx>
To: "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>,
Date: 09.01.2013 19:10
Subject: Re: [eclipse-dev] Platform Juno SR2 freeze plan






Team, I've updated the
build schedule calendar [1], for this Juno SR2 freeze plan, adding "test days" and "sign off days".

I know some of you are very good at proof reading my calendar mistakes, so any corrections are very welcome.

The only "ambiguous" part, I might have misinterpreted, was around the change in rhythm around RC3 ... to avoid conflicting with Kepler M4, we'll have RC3 build on Friday, January 25. I am assuming then we will not have the builds that were previously scheduled for the Wednesday before, and after (January 23, and January 30). Naturally, we'd still do builds "upon request", if needed. But, thought I'd mention this change in schedule case the Friday build was intended to be purely an "extra" build, with no change in scheduled Wednesday builds.

Thanks,

[1]
http://www.eclipse.org/eclipse/platform-releng/buildSchedule.html




From:        
John Arthorne <John_Arthorne@xxxxxxxxxx>
To:        
eclipse-dev@xxxxxxxxxxx,
Date:        
01/04/2013 02:08 PM
Subject:        
[eclipse-dev] Platform Juno SR2 freeze plan
Sent by:        
eclipse-dev-bounces@xxxxxxxxxxx




The end-game plan for Eclipse Platform Juno service release 2 is now available:


http://www.eclipse.org/eclipse/development/plans/freeze_plan_4_2_2.php

Our next maintenance build will be release candidate 1. Now is a good time to review the remaining open 4.2.2 bugs and defer all but the most critical. We currently have 50 remaining bugs still open:


https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Equinox&product=JDT&product=PDE&product=Platform&target_milestone=4.2.2&target_milestone=Juno%20SR2

John
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/eclipse-dev
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/eclipse-dev

_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev


Back to the top