[orbit-dev] Orbit build for Indigo SR1 -- change in plans

[David M Williams <david_williams@xxxxxxxxxx>]

I propose we not have an Orbit maintenance
release for Indigo SR1, after all. 

The ICU change, that was motivating
the Orbit SR1 release, is going to wait for SR2 ... see 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=348616

If I have missed something (some other
reason to have an SR1 from Orbit), let us know quick!

Now for the complicated part: 

If we do not have a maintenance release
for SR1, then the presence of our "M-build" on downloads page
is misleading at best, and might cause others to "pick up" a
change not intended for Indigo SR1. 

Hence I will plan to remove that M-build
from "downloads" page. I'll announce this on cross-project list
too, and wait 24 hours (till noon Thursday), so anyone that is already
referencing that "M-build" URL will have a chance to "back
out" the change from their build scripts without a sudden break.  

If you know anyone that might "cache
bundles" for re-use in their builds or packaging, please pass along
the message so they can flush their cache for this case.

To be explicit: 

Orbit to use for Indigo SR1 (same as
used for Indigo SR0): 
    R20110523182458
ICU to use for SR1 (same as used for
Indigo SR0):
    com.ibm.icu_4.4.2.v20110208.jar

ICU to flush from caches, if any, (that
is, if this bundles appears in your builds or distributions then you (or
p2?) are picking up the wrong one). 
    com.ibm.icu_4.4.2.v20110823.jar

The maintenance build/branch will continue
to run, since sounds like we will need it for Indigo SR2, but we will not
have any "M builds" on downloads until after SR1.  

Let us know if questions, or if I have
missed anything. 

Sorry for the churn, 

Thanks, 





From:      
 David M Williams/Raleigh/IBM@IBMUS
To:      
 Orbit Developer discussion
<orbit-dev@xxxxxxxxxxx>
Date:      
 08/23/2011 03:57 PM
Subject:    
   Re: [orbit-dev]
Do we need an Orbit build and stream for Indigo SR1?
Sent by:    
   orbit-dev-bounces@xxxxxxxxxxx

---

I am running a test build now, and am
documenting the mechanics of creating the build in 
355559
- Create maintenance build for Indigo_maintenance 

In short, anything for Indigo maintenance should be "released"
to maps in Indigo_maintenance branch. 

Longer version: if anyone has anything for Indigo SR1, please

1. make sure it is completely safe and risk free and (since that's impossible)
make sure it is really important or urgent or blocking, 

2. open a bug with an Indigo SR1 "milestone target", so we (and
consumers) can easily see what is going into maintenance release, so they'll
have better idea if it effects them. 

3. Commit, tag, and update map file (in org.eclipse.orbit.releng project)
in both Indigo_maintenance, and HEAD (in nearly all cases). 

4. Be sure to update ip_log files in both stream. 

5. Test well :) 

Schedule: 

Working backwards from Indigo SR1 GA, SR1 RC4 +0 is on 9/12, which implies
the last possible time for us to have our "final R build" ready
is on 9/5. I propose we plan on declaring our Orbit Indigo SR1 "Recommended"
build on 9/2. Until then, we will produce "M builds" and rename
it to an "R build" on 9/2, so that "R build" URL will
be our long lived URL. Naturally, it is desired to be finished before 9/2,
so please get any maintenance work done soon, and let us (and community)
know if it will be "late" in RCs. Unless I hear otherwise, I'll
promote just about every "M-build" to the downloads page, since
there shouldn't be too many  of them, and time is short. 

Let us know if questions or issues. 

Thanks, 






From:        DJ
Houghton <DJ_Houghton@xxxxxxxxxx> 
To:        Orbit
Developer discussion <orbit-dev@xxxxxxxxxxx>
Date:        08/23/2011
02:52 PM 
Subject:        Re:
[orbit-dev] Do we need an Orbit build and stream for Indigo SR1?
Sent by:        orbit-dev-bounces@xxxxxxxxxxx

---

Hi David, 

Hot off the presses (released today) we have a new ICU4J bundle that is
updated to include support for Java7. I have opened a bug report [1] and
CQ [2] for adding the new bundle to the repository and would like to include
it in an Orbit build as soon as it is approved. 

Thanks.

[1] https://bugs.eclipse.org/355555
[2] https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5529

David
M Williams ---2011/08/10 03:02:13 PM---I've seen some hints in bugzilla
entries that some might want a new Orbit M build for Indigo SR1. T

From:	David M Williams <david_williams@xxxxxxxxxx>
To:	orbit-dev@xxxxxxxxxxx
Date:	2011/08/10 03:02 PM
Subject:	[orbit-dev] Do we need an Orbit build and stream for Indigo SR1?
Sent by:	orbit-dev-bounces@xxxxxxxxxxx

---

I've seen some hints in bugzilla entries that some might want a new Orbit
M build for Indigo SR1. Time to speak up if you need one. 

I have created new targets in our bugzilla component, including Indigo
SR1, just in case its needed. 

To review, we in Orbit would prefer not to have a maintenance build, but
of course can, if there is a blocking (or really bad) problem. 

If you, or the projects you work with, need such a fix, please open a bug
... or, clone original bug ... to specifically target it to "Indigo
SR1". Doing so makes it much easier for adopters and users (and us)
to see what's changed between Indigo and Indigo SR1. 

If a maintenance build is required, I will create a branch of what was
released for Indigo, so that way, we can release the bare minimum of changes
into the maintenance stream. 

I'm happy to set the build up, if needed ... so let me know. 

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

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