Thanks for your comments.
I have checked most of test cases, everything is fine. Now to complete the check list, I need to convince our release engineer to be sympathetic ;-)
And I have also updated the BREE and the build file (just in case).
-----orbit-dev-bounces@xxxxxxxxxxx a écrit : -----
A : Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
De : David M Williams <david_williams@xxxxxxxxxx>
Envoyé par : orbit-dev-bounces@xxxxxxxxxxx
Date : 14/05/2010 15:26
Objet : Re: [orbit-dev] Reminder of final few weeks for Oribt ...
> Before promoting it into Helios, is it possible to test/validate it ?
Depends on what you mean, exactly, but I think there are a few approaches to this. In order approximately easiest to hardest:
- Hey, it did build, and passed our modest layout test! What more could you want? :) [really, just joking]
- Download the jar from the committers area today and inspect it "manually" to be sure all looks correct.
http://download.eclipse.org/tools/orbit/committers/drops/S20100514103823/
- Try dropping that jar into an application that needs/uses it and make sure it works (this isn't always easy, depending on how your application is "installed". At worst, you'd have to make your own, temporary "feature patch" from your workbench).
- If you have sympathetic, experienced "releng team" it is possible to point your build to things in the "committers" area, so you'd pick up this jar during a build today, and then test in your own context. The downside is these "committers builds" can disappear quickly, so your sympathetic releng team has to be prepared to switch back to "download" builds at a moments notice.
- Import into your workspace (or, better, workspace target) and make sure you can write code against its API. (This tests that the "output" and "classpath" have correct settings for use within the IDE, which is a little different that a pure OSGi runtime.
Or ... did you mean something else?
I took a quick peek and saw two minor problems: a) the BREE is set to Java 1.5, but the doc (readme) says 1.4 or higher, so better to use a 1.4 BREE. b) I noticed your bin.includes includes the "build.properties" file itself. This is unnecessary and best not to include (I don't know if it does specific harm, but I have heard rumors PDE sometimes infers certain things depending on whether or not it is present ... but, just rumors ... don't know for sure ... but, definitely not required at runtime so best not to include it).
Thanks for your care,
| From: | GBarbier@xxxxxxxxxxxxxxxx |
| To: | Orbit Developer discussion <orbit-dev@xxxxxxxxxxx> |
| Date: | 05/14/2010 04:48 AM |
| Subject: | Re: [orbit-dev] Reminder of final few weeks for Oribt ... |
| Sent by: | orbit-dev-bounces@xxxxxxxxxxx |
Hello,
I have added a new bundle (org.prefuse), as it will be used by the eclipse.modeling.mdt.MoDisco project.
Before promoting it into Helios, is it possible to test/validate it ? Even if everything should be ok (migration of existing bundle from MoDisco to Orbit), it would be great to have a validation.
All informations needed to build Orbit with this new bundle as been tagged "v20100514-1000" in CVS repository.
Regards,
Gabriel
-----orbit-dev-bounces@xxxxxxxxxxx a écrit : -----
A : Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
De : David M Williams <david_williams@xxxxxxxxxx>
Envoyé par : orbit-dev-bounces@xxxxxxxxxxx
Date : 11/05/2010 18:15
Objet : [orbit-dev] Reminder of final few weeks for Oribt ...
We've never published a "ramp down policy" for Orbit, but I was thinking maybe we should, since there are so many Orbit committers and over time, our knowledge base gets more diverse, if not diluted.
Hence, I've codified a few thoughts at
http://wiki.eclipse.org/Orbit_Rampdown_Policy
No new processes, per se, ... just reminders of what our goals are.
And ... one good reminder is our deadlines! This is basically "end of day" each Friday, so be sure to say if you need some small adjustments.
05/07 (one week before RC1 +0) [done]
05/14 (one week before RC2 +0)
05/21 (one week before RC3 +0)
05/28 (one week before RC4 +0)
06/04 (one week before Final +0)
Remember as each week passes, the criteria for making a change should get tighter.
I'm aware of a few possible reasons we might need a new build before our final one .... but please keep us informed here on this list if you are planning changes or fixes.
_______________________________________________
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
