Fw: [orbit-dev] Reminder: Orbit M3ish S build to be declaredtomorrowarou

[DJ Houghton <DJ_Houghton@xxxxxxxxxx>]

Sorry, I think I confused the situation...I thought that we were talking
about a maintenance build, not a milestone build.

If we want to release only the changes to the axis bundle to the next
S-build, I believe that would require:
- branching the map file from the version that was used to create the last
S-build
- making only the axis changes
- changing the builder to use that version/branch of the map file to run
the build

If we could do that, that would be great but I think all the work falls in
David's hands so its really up to him. :-)


----- Forwarded by DJ Houghton/Ottawa/IBM on 11/07/2007 11:25 AM -----

DJ Houghton/Ottawa/IBM wrote on 11/07/2007 11:21:57 AM:

> Yeah, I had thought of the source bundle change when I saw David's
> message. After thinking about it a bit I think that it might be best
> to wait and not release the changes to the source bundle right now.
> There is going to be a new format for source bundles soon (just
> working out the final kinks in the platform) and the bundles will
> have to be changed again for the spring release.
>
> The main reason that I wouldn't want to release the new source
> bundles to the maintenance build is because the bundles might
> contain other changes, I didn't do any branching.
>
> So I would recommend:
> - not releasing the source bundle changes for the maintenance build
> - changing the source bundles to the new format for the spring release
>
> Here is the source bundle bug report fyi:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=206596
>
> orbit-dev-bounces@xxxxxxxxxxx wrote on 11/07/2007 10:26:48 AM:
>
> > Hi again,
> >
> > Sorry, forget my comment -- looks like DJ did release the changes for
> > bug 208475 for all the bundles. They are all now tagged as
> > v200711021015
> > I did not notice immediately because I had looked at the
Europa_Maintenace
> > branch of the Orbit mapfile project, where the change is not released.
> > Anyways, this means that a new S-build will have new versions of pretty
> > much all the bundles due to this "global" change. Hope that's OK for
> > everyone, because I'd think it means that all the projects in Ganymede
> > will need to pick up the "new" S-build or the versions they deliver of
the
> > "Orbit'ed" bundles are different.
> > Or am I missing something?
> > Cheers,
> > --
> > Martin Oberhuber
> > Wind River Systems, Inc.
> > Target Management Project Lead, DSDP PMC Member
> > http://www.eclipse.org/dsdp/tm
> >
> >
> > From: orbit-dev-bounces@xxxxxxxxxxx
[mailto:orbit-dev-bounces@xxxxxxxxxxx]
> > On Behalf Of Oberhuber, Martin
> > Sent: Wednesday, November 07, 2007 4:21 PM
> > To: Orbit Developer discussion
> > Subject: RE: [orbit-dev] Reminder: Orbit M3ish S build to be
> > declaredtomorrowaround noon

> > Hi Dave,
> >
> > I belive that most bundles were changed in order to address
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=208475
> > ("Source bundles should be marked as singletons")
> >
> > But it looks like none of these changes have been released yet.
> > Would your creating a new S-build be a chance to pick up these
> > changes?
> >
> > For apache commons.net and ORO I'm releasing the change now.
> > Cheers,
> > --
> > Martin Oberhuber
> > Wind River Systems, Inc.
> > Target Management Project Lead, DSDP PMC Member
> > http://www.eclipse.org/dsdp/tm
> >
> >
> > From: orbit-dev-bounces@xxxxxxxxxxx
[mailto:orbit-dev-bounces@xxxxxxxxxxx]
> > On Behalf Of David M Williams
> > Sent: Wednesday, November 07, 2007 7:53 AM
> > To: Orbit Developer discussion
> > Subject: Re: [orbit-dev] Reminder: Orbit M3ish S build to be
> > declared tomorrowaround noon

> >
> > Really ... I said "M3ish" for a reason :)
> > I really wanted to avoid this, but ... when it's since it's WTP that
> > needs it .... :)
> >
> > I'd like to promote another build to an S-build, to pick up the
> > apache.axis changes described in
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=208658
> >
> > I've posted to cross-project as well, and no one responded, so guess
> > it won't effect anyone else.
> >
> > I don't think there's been much change in Orbit since the last S-
> > build, so seems unlikely anything would
> > be "broken" ... and those already picking up the previous S build
> > would have no reason to change,
> > unless you did indeed use org.apache.axis.
> >
> > So, unless I hear objections, I'll produce another S-build Wednesday
> > afternoon for immediate promotion.
> >
> > Thanks,
> >
> >
> >
> >

> >
> > David M Williams/Raleigh/IBM@IBMUS
> > Sent by: orbit-dev-bounces@xxxxxxxxxxx
> > 10/25/2007 03:21 PM
> >
> > Please respond to
> > Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
> >
> > To
> >
> > <orbit-dev@xxxxxxxxxxx>
> >
> > cc
> >
> > Subject
> >
> > [orbit-dev] Reminder: Orbit M3ish S build to be declared tomorrow
> > around noon
> >
> >
> >
> >
> > Remember that our S build for Ganymede M3 will be declared around
> > noon tomorrow, Friday 10/26.
> >
> > Candiate:
> > http://download.eclipse.org/tools/orbit/committers/drops/S200710221836/
> >
> > Please check your favorite bundles to be sure they are in order,
> > especially if added recently.
> >
> > And, let us know here on this list if it is not ready, or if you
> > have issues with declaring this S-build at this time.
> >
> > Thanks,_______________________________________________
> > 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