Re: [orbit-dev] Orbit and Indigo SR2 schedule: proposing R build on Jan

[DJ Houghton <DJ_Houghton@xxxxxxxxxx>]

Hi David,

The Platform has one more change to include in the maintenance branch. [1]
I'll do that today so it is available in tomorrow's promoted build.
Thanks.

dj

[1] https://bugs.eclipse.org/369098


David M Williams ---2012/01/18 09:01:25 AM---Indigo SR2 is coming right up soon; the RC1 warm-up aggregation build is this week. We already have,

From:	David M Williams <david_williams@xxxxxxxxxx>
To:	orbit-dev@xxxxxxxxxxx
Date:	2012/01/18 09:01 AM
Subject:	[orbit-dev] Orbit and Indigo SR2 schedule: proposing R build on Jan 27
Sent by:	orbit-dev-bounces@xxxxxxxxxxx

---

Indigo SR2 is coming right up soon; the RC1 warm-up aggregation build is
this week. We already have, as far as I know, the final Orbit M-build for
Indigo SR2. At some point soon, we need to rename it to an R-build so
participating projects could update their maps, scripts, builds, POMs?, or
what ever else they use to get the latest Orbit bits.

These are the two changes for Indigo SR2, the latter (derby) change is not
one of function, just a fix to how its versioning is computed. Any other
changes anyone wants to propose? If so, please let us know this week!

355555 Add ICU4J 4.4.2.v20110823 to Orbit
355586 derby's qualifier increases each build

In any case, we need to decide when to call Orbit "final" and rename the M
build to R build. We typically like to do ours "early" to give everyone
plenty of time to get up to date. I'll spell out the candidate dates in
detail, to make it more likely someone could spot any errors in my
assumptions or reasoning.

Indigo SR2 +0 days:

RC2: Jan 27
RC3: Feb 03
RC4: Feb 10

So, considering Orbit as "-1", the candidate critical dates for us would be

RC2: Jan. 20
RC3: Jan. 27
RC4: Feb. 03

I propose we produce (rename) our final Indigo R build on 1/27. This will
allow the Platform (and others) to move to the final URL for their RC3
build. (Of course, people can and should use the M-build URL before that,
so the content would not change once they move to final R-build URL ... we
just want to reduce any churn of any kind those final few weeks.)

Sound like a reasonable date? Only 9 days away! Anyone want to propose
earlier? Later?

Unless there are objections or suggestions, we'll go with Jan. 27 as the
day to produce our R build for use with Indigo SR2.

Be sure to say soon, if you have other candidate changes for Indigo SR2.

And, this reminds me, we need to archive some of our previous R-builds. I
plan to move 4 of the 5 R-builds to archives [1] this week. Be sure to
comment on bug 366251 [2] if you have any concerns or suggestions about
that.

Thanks,

[1] http://archive.eclipse.org/tools/orbit/downloads/
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=366251






_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev