Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] For Helios, please use R-builds from Orbit .. for Indigo the latest S-build
I can't say for sure if you should respin, but I'd lean that way.

I thought this was common knowledge .... but, maybe only if you've been doing it for 7 years :)

For the maintenance stream, Helios, we always want people to use the latest R-build from Orbit, to minimize all changes from previous releases. That is currently
http://download.eclipse.org/tools/orbit/downloads/drops/R20100519200754/
If we (or anyone) ever needed a fix in Orbit for maintenance stream, we (or you) would request a new R-build, which would have the minimally required changes.

For Indigo, always use the latest S-build, which is currently
http://download.eclipse.org/tools/orbit/downloads/drops/S20110124210048/

No wonder we've been getting such a mix of third party bundles.

My apologies for not making this clearer and more explicit.





From:        Eike Stepper <stepper@xxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        02/03/2011 10:43 AM
Subject:        Re: [cross-project-issues-dev] Status and outlook for Helios SR2, RC2
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx



Am 03.02.2011 16:24, schrieb David M Williams:
> > Was I right in expecting that this can become a problem. If so, wasn't I even required to fix that?
>
> Yes, old Orbit bundles can be a problem and IMHO this would be a good fix to make in RC2, even if a day late, since a) would likely not impact your downstream adopters, and b) then for RC2 we can better figure out who else, if anyone, references old Orbit bundles.
>
> But ... no need to reply if you just have a special case ... but, old Orbit bundles in Helios stream?! Everyone knows to use the "R-build" from Orbit, right? That hasn't changed in a long time.
No, I did not know ;-(

I used the S build. Shall I respin?

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


>
> Thanks,
>
>
>
>
>
> From: Eike Stepper <stepper@xxxxxxxxxx>
> To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
> Date: 02/03/2011 09:52 AM
> Subject: Re: [cross-project-issues-dev] Status and outlook for Helios SR2, RC2
> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------! ----
--
>
>
>
> Am 03.02.2011 15:14, schrieb David M Williams:
> > You didn't ask ... but ...
> >
> > > I just realized that our RC2+2 build failed after 16 hours.
> >
> > How long do they normally take. Please use the "timeout" plugin on hudson. There's a check box on a job's configuration page labeled "Abort the build if it's stuck". A good value is to set the maximum time to double the time it would normally take. And, normally, you'd want to check the "fail the build" if it times out ... so you get a failed notice, that something went wrong.
> I'm sure I had this setting on the old hudson server. Thanks for pointing this out. I assumed that hudson itself was not working properly due to the full disk issue.
>
>
> >
> > > ... if I may contribute CDO today ... May I or not?
> >
> > Yes, you may, or not :) As a general rule, I recommend projects do not contribute after their +n day unless a) they need to fix a blocking bug, or to have a valid contribution (which for an RC build is tricky to weigh since we do want them to be true release candidates ... but, you will get a chance next week too. And b) you keep everyone informed, as you are doing. Thanks! It does depend on your own judgement of what you and your adopters need. We definitely don't want to limit anyone from doing what they need ... just to use care and recognize its downstream impacts (which can be good or bad, depending on the importance of the fix, vs. the cost of others having to respin, etc.). While I don't know details, since you "missed RC1", I'd say that also increases the importance of doing a contribution today.
> Seems everything went well: https://hudson.eclipse.org/hudson/job/helios.runAggregator/472/
>
> BTW. my new build did not contain any important changes except that the former build contained features which in turn referenced the old Orbit versions. Was I right in expecting that this can become a problem. If so, wasn't I even required to fix that?
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de <http://www.esc-net.de/>
> http://thegordian.blogspot.com <http://thegordian.blogspot.com/>
> http://twitter.com/eikestepper
>
>
> >
> >
> >
> >
> >
> >
> >
> > From: Eike Stepper <stepper@xxxxxxxxxx>
> > To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
> > Date: 02/03/2011 03:45 AM
> > Subject: Re: [cross-project-issues-dev] Status and outlook for Helios SR2, RC2
> > Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
> > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------! -----!
----
> --
> >
> >
> >
> > Am 03.02.2011 09:36, schrieb Nicolas Bros:
> > >
> > >     So I have left the Helios aggregation builds enabled, if anyone has any last minute (+3) contributions?
> > >
> > > I am surprised. Don't you expect all +3 projects to contribute today? MoDisco is +3, and I was waiting until today for our final RC2 contributed build, in case a +2 project on which we depend updated their contribution yesterday.
> > > Is this not the right way to proceed?
> >
> > I just realized that our RC2+2 build failed after 16 hours. Probably due to the disk space issue. Since I've missed RC1 already (for other reasons, my former releng just resigned) I would like to ask if I may contribute CDO today. I know that Modisco depends on CDO but it cold also be the case that a new CDO is needed because the Orbit versions have increased (no clue how that would affect the train). My new build would be available in ~30 minutes plus signing plus promotion/contribution...
> >
> > May I or not?
> >
> > Cheers
> > /Eike
> >
> > ----
> > http://www.esc-net.de <http://www.esc-net.de/><http://www.esc-net.de/>
> > http://thegordian.blogspot.com <http://thegordian.blogspot.com/><http://thegordian.blogspot.com/>
> > http://twitter.com/eikestepper
> >
> >
> > _______________________________________________
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >
> >
> > _______________________________________________
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Back to the top