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?

> so did I get you right that we need an M-build adding
>
> apache.commons.compress 1.6.0

> JavaEWAH 0.7.9
>
> to reach an enhanced R-build with these updates soon (in Kepler SR2
> timeframe) ?

>  

Yes.

> > Again, if there's questions about what you need to do to get
> > maintenance items into M-builds, let us know. 

>
> Yes, let us know what's needed to bring these new versions into M-builds.

> I guess we need to update the list of bundles to be included on the Kepler
> maintenance branch. I am not sure what exactly needs to be done for that.

Once you load up the Kepler_maintenance branch of the two projects I previously mentioned (for maps, and feature), then conceptually, you do the exact same thing you'd always do.

The only slight twist is the little understood short cut that the map entries for the "new ones" can use of the exact same tag that was used in HEAD, for Luna. (That is, builds are entirely tag driven ... those bundles themselves do not need a new branch or a new tag, etc.) But would need new entry lines in the map files, and changes to the feature.xml (thus the feature project must be re-tagged with a new tag that goes in the map files. And, of course, the xml files in IP_log directory need to be updated ... likely exactly the same as the specific entry added to for those bundles in HEAD, for Luna.

Hope that's enough to get you started ... but if further questions, glad to answer those too.

In the end, we want our M-build to be "just like" the R build used for Kepler SR1 (R20130827064939) except for these three (so far) additions.

Thanks,









From:        Matthias Sohn <matthias.sohn@xxxxxxxxx>
To:        Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>,
Date:        01/13/2014 05:06 PM
Subject:        Re: [orbit-dev] Ready for Kepler SR2?
Sent by:        orbit-dev-bounces@xxxxxxxxxxx




On Mon, Jan 13, 2014 at 3:57 PM, David M Williams <david_williams@xxxxxxxxxx> wrote:
> +1 for build promotion

This does not mean anything, in this Kepler SR context.

So far, in our "M builds", the only difference, compared to previous R-build, is

> com.jcraft.jsch.source [0.1.50.v201310081430]
> com.jcraft.jsch [0.1.50.v201310081430]

And that's the way we want it, for Kepler SR ... very few changes.

And sounds like a few more are desired. That is fine.

But in our I-builds (which will eventually be promoted to S-build, and then eventually R build for Luna, there have been 40 to 50 changes so far ... too many to "suddenly" spring on everyone for an SR2 release.

Hope that helps explain the situation.


so did I get you right that we need an M-build adding

apache.commons.compress 1.6.0
JavaEWAH 0.7.9

to reach an enhanced R-build with these updates soon (in Kepler SR2 timeframe) ?
 
Again, if there's questions about what you need to do to get maintenance items into M-builds, let us know. 

Yes, let us know what's needed to bring these new versions into M-builds.
I guess we need to update the list of bundles to be included on the Kepler
maintenance branch. I am not sure what exactly needs to be done for that.

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


Back to the top