Re: [orbit-dev] R build for Galileo SR2

[David M Williams <david_williams@xxxxxxxxxx>]

No, we never know unless someone tells
us they need a bundle for maintenance, if an Orbit committer doesn't know.
But that reminds me another part of my plan is to announce our plan on
cross-project first of next week ... after we (Orbit) commit to a plan.


And this is a great opportunity for
me to remind everyone -- especially any new committers to Orbit, that perhaps
haven't been through maintenance before -- we only want to include changes
that are to fix pretty bad, well known problems, that consuming projects
say they really need. The reason, of course, not to just include "the
latest" automatically (or even minor fixes), is that for many projects
or companies this might mean an increase in effort ... to re-test the functionality,
even if it is known the new version is (supposed to be) compatible. In
other words, Projects are not in complete control. For example, WTP might
not include latest of log4j, thinking they didn't want to retest a change,
but if Orbit provides it, perhaps Datatools might end up installing it,
thus impacting WTP as well. If it really is needed, that's fine ... great
even ... all Projects know that. But ... we don't want to make changes
if there are no hard requirement to. 

There's no hard and fast rule ... but
if anyone has a question about if a new bundle should be include, then
the answer is "no". (ha ha) But seriously, if there's a question,
feel free to ask for others advice and opinions ... such as your fellow
Orbit committers. 

Much thanks!

From:	Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
To:	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Date:	01/07/2010 05:29 AM
Subject:	Re: [orbit-dev] R build for Galileo SR2
Sent by:	orbit-dev-bounces@xxxxxxxxxxx

---

Am 07.01.2010 00:04, schrieb David M Williams:
> org.apache.commons.jxpath_1.2.0.v20080604-1500.jar
> org.apache.log4j_1.2.13.v200903072027.jar
> org.junit_3.8.2.v20090203-1005.jar
> org.mozilla.rhino_1.7.1.v20090521.jar (same _packages_ as the new
> org.mozilla._javascript_ bundle)
> 
> = = = = = =
> 
> What this comes down to is what do Orbit Committers want?

Do we know if any of the downstream consumers requires any of the
upgrades above in a maintenance release?

For example, I could imagine that the Log4J update from 1.2.13 to 1.2.15
might be desired for a maintenance release but that's just my guess.

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev