Re: [orbit-dev] Request for promotion

[David M Williams <david_williams@xxxxxxxxxx>]

To be explicit, I didn't mean to advise
anyone use an I-build for a release. :) Just that, that was the only alternative
"for next week". If the project wants to use that I-build in
their release, that's up to them, but I recommend them saving a copy (or,
small subset of) in case you need to reproduce, say in 3 or 8 weeks for
a patch or something, and/or them keep their eye open for it changing qualifiers
for the next release.). 

But, at your request, I'll remove the
current I builds on "downloads" and promote latest I-build on
"build". 

For  the record, project builds
for Kepler M4 should still use the latest S-build, for consistency. Not
sure if anything (else) has changed since then, but  if you wanted
to be "most consistent", that S-build, S20121207152029, would
be the build to use. 

For future reference, if any projects
ever want an Orbit R-build for an off-cycle release that's fine, but would
take about a months notice. (We then create a stream that's just like the
previous R-build, except for the few things required to be changed for
that off-cycle release). 

Thanks, 





From:      
 Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx>
To:      
 orbit-dev@xxxxxxxxxxx,

Date:      
 12/12/2012 05:29 PM
Subject:    
   [orbit-dev]
Request for promotion
Sent by:    
   orbit-dev-bounces@xxxxxxxxxxx

---

Following David's advise in [1] the JGit
project would like to request the promotion of the latest continuous
build [2] to an I-Build in order to consume "Apache Commons Compress"
[3] in its 2.2 release planned for next week.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=396199#c11
[2] http://build.eclipse.org/orbit/committers/orbit-I/20121212174845/I20121212174845/
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=396199

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