Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] Fwd: [cross-project-issues-dev] Be sure to stay on the Helios train ...


All MDT component leads should be subscribed to the cross-project mailing list, but just in case some aren't, please see below.

It's time to start thinking about concrete plans for the Helios release. If you haven't done so yet, I'd suggest subscribing to the planning council calendar (see to keep on top of milestones and deliverables for Galileo and Helios.



---------- Forwarded message ----------
From: David M Williams <david_williams@xxxxxxxxxx>
Date: Wed, Aug 12, 2009 at 10:44 AM
Subject: [cross-project-issues-dev] Be sure to stay on the Helios train ...
To: cross-project-issues-dev@xxxxxxxxxxx

Hopefully everyone has seen our Helios schedule.

Here's two important dates:

Release: 6/23/2010 (fourth Wednesday of June).

Milestone 1: 8/7 to 8/21 completion window. That's right ... we're halfway
through completing M1!

Part of the spirit of our yearly Simultaneous Release Train is that we all
chug along at the same speed, not only that we all arrive at the same
place at the same time, at the end.

Thus, I'm assuming we are all able and willing to keep the Simultaneous
Milestones going, starting with M1 -- for the first time ever! Naturally,
there may be some new projects that join later, but anyone that was in the
Galileo Release, should have no trouble keeping the coal burning. The
process is nearly identical.

The new project to find your .build files is (same cvs repository)

I seeded the files there with whatever was in
(as of a few days ago). I changed most occurrences of 'galileo' to
'helios' and it seems to build fine ... but, it needs current input from
everyone, especially as you produce your M1 deliverables.

I'll turn on "fail mail" this afternoon, so don't be surprised if you
start getting notices from hundsonbuild: helios.

This early start will hopefully lead to improved release engineering,
improved testing, and more time to deal with issue of substance, instead
of just "how to build".

The Planning Council (with representatives from PMCs and Strategic
members) will still be working on evaluation criteria and general
processes over the next few months, but there's nothing that should hold
up getting builds going.

So please update your milestone files as soon as possible and ... as
always ... let me know if questions or issues.

cross-project-issues-dev mailing list

Back to the top