Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] Ready for Kepler SR2?
+1 for build promotion


On Mon, Jan 13, 2014 at 4:42 AM, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
On Mon, Jan 13, 2014 at 6:31 AM, David M Williams <david_williams@xxxxxxxxxx> wrote:
I'm promoting that I-build now ... but ... are these intended for Kepler SR2? If so, they'll need to go into an M-build. That's what we'll promote for Kepler SR2. (Recall, we do it that way to minimize changes from one R build to another ... for maintenance).

There is a Kepler_maintenance branch of 'org.eclipse.orbit.releng'. and 'org.eclipse.orbit.build.feature.set1', if you need it. The "bundle versions" in map files, can (usually) be the same as what you just used for the I-build, but you may need to tweak the feature.xml file and use a different version/tag of that, or maintenance build. Please ask if anything isn't clear.

This is my indirect answer to the original question. If anyone releases anything (even if not in "Kepler SR2") its best to request an R-build of Orbit with the specific changes you need, so you have that for long term retention. Since your "3.3" is so close to Kepler SR2, I feel ok about putting them in that R-build ... unless someone knows of complications that would cause. 

I successfully tested jgit 3.3-SNAPSHOT using the I-build you promoted
hence I'd like to request an R-build containing

apache.commons.compress 1.6.0
JavaEWAH 0.7.9
com.jcraft.jsch 0.1.50

anything I need to do in order to get this created beyond asking here ?

--
Matthias

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




--
Cheers,

Chris Aniszczyk
http://aniszczyk.org
+1 512 961 6719

Back to the top