[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Proposed build schedule for month of July

> .. The only potential problem is
> having two 4.3 integration builds a week, since some teams have a
> manual process for doing build input and it could create extra work
> for people. I would suggest making the Monday build an N-build
> rather than an I-build. ...


Well, I probably have a limited memory (joining near the end of this cycle) .... I thought there were lots of I-builds through-out the week, some being pseudo warm-ups for the main one on Tuesday.

But, I'd be quite happy with one scheduled one (and respins upon request) ... so I'll schedule that I-build for Tuesday 8 AM and convert the Monday one to an N-build.
Now ... if we are doing N-builds leading up to I-build on Tuesday at 8 AM should they all be at 8 AM? I and N builds that is (I know ... "nightlies at 8 AM?" ... but, I bet it would be night somewhere where we have committers :)

I'd recommend this since webmasters used to advice to avoid heavy use from midnight to 6 AM (not sure if that's still true ... it no longer is in shell banner as it used to be) but, more important, the tests would be running while I (and other North Americans) were awake, and might be  easier to "watch" them to fix the many issues we have with them.

But, if 8 PM is preferred, then I'd recommend both N and I builds move to 8 PM (making the I-build on Monday 8 PM, ready for inspection/test on Tuesday morning, Eastern time). [I'd probably be awake, in either case :) ]

Apologies if the right answer or pattern is obvious to others, but ... I'm not sure how its been done in past, existing habits and mechanisms, and needs of committers. (I'm not used to scheduled builds nor N builds ... in WTP, we just did I builds "continuously" when ever there was a change :/ )

So, feel free to say what's desired. But, if I don't hear other suggestions, complaints, advice, I'll schedule (Eastern times)
N builds, 8 AM, Friday, Sat, Sun, Mon
I build, 8 AM Tuesday
3.8 M build Thursday 8 AM
4.2 M build Thursday 10 AM
This leaves Wednesday as a sort of an "evaluation day", see what you think of the I build, ask for respins if needed, decide what to cherry pick for M builds, if anything.

And, again, I'm thinking of this as the July schedule ... we can always redo in August as we start meeting again, have firm delivery dates in hand, etc.

Thanks,









From:        John Arthorne <John_Arthorne@xxxxxxxxxx>
To:        "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>,
Date:        06/27/2012 01:24 PM
Subject:        Re: [eclipse-dev] Proposed build schedule for month of July
Sent by:        eclipse-dev-bounces@xxxxxxxxxxx




This looks reasonable to me David. The only potential problem is having two 4.3 integration builds a week, since some teams have a manual process for doing build input and it could create extra work for people. I would suggest making the Monday build an N-build rather than an I-build. Unless you were thinking that Monday I-build would be a slot for extra test builds that we don't publish?

For dates, I think a reasonable guess is that Kepler M1 will be August 10th. For Juno SR1, I expect we will have RC1 on August 15th, and RC2 on August 29th. David and I will work with the planning council to finalize those dates and get a plan posted over the coming weeks.


John


David M Williams <david_williams@xxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx

06/27/2012 10:23 AM

Please respond to
"General development mailing list of the Eclipse project."        <eclipse-dev@xxxxxxxxxxx>

To
"General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>
cc
Subject
[eclipse-dev] Proposed build schedule for month of July







Potential Discussion Topic for status/planning/architecture call:

I present this as a "straw man" proposal. I'd be fine with about anything the team would find useful, but think we have a few constraints: we have more builds than in the past, our unit test cycle takes (much) longer than in the past. So, initially (month of July) I'd like to leave plenty of "open time" to do special "test builds" to more easily investigate unit test machines setup and issues.  


proposed build schedule ... for month of July:

Assumptions:

Kepler M1: mid-August-ish

Juno SR1: fourth Friday of September (assuming we'll keep 4.2.1 and 3.8.1 "simultaneous") (so RC1 near end of August).

Goal, for July:

provide some regular builds for fixes/integration, etc., but also allow time for deep investigation into unit tests setup/failures (which often may require re-testing, without re-building, testing a limited set of suites, and similar).

Proposed Schedule:

4.3 N builds: 8 PM Thursday, Friday, Sunday (none Saturday, assuming Hudson is restarted overnight, so tests would not finish)


4.3 I builds: Monday, Tuesday 8 AM (and on demand)

3.8.1 Maintenance Thursday 10 AM (and on demand)


4.2.1 Maintenance Thursday 12 AM (noon) (and on demand)


Adjust at end of July as schedules better known, regular work rhythms resume, and, we hope, unit test cycle reduced.
_______________________________________________
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