Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Last day for Juno SR1 contributions

Ok, so looks like your contribution is in build # 664 which will be done about 6:30 or 7:00. I'll promote that one to staging, unless anyone else speaks up (soon).
(And, if soon enough, I'd stop current one and restart, so keep us informed if anyone else is "late").
Thanks,




From:        Jeff Johnston <jjohnstn@xxxxxxxxxx>
To:        cross-project-issues-dev@xxxxxxxxxxx,
Date:        09/19/2012 04:56 PM
Subject:        Re: [cross-project-issues-dev] Last day for Juno SR1 contributions
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx




I made a change to Linux Tools b3aggrcon for RC4 and updated our repo,
but another aggregation build was already started and it appears it
won't finish until after 5 pm.

If another build doesn't get in by then, can you please start another  one?

Thanks,

-- Jeff J.

On 09/19/2012 03:03 AM, David M Williams wrote:
> Here we are already, Juno SR1 RC4 +3.
>
> I did have to temporarily disable Jubula to get a green build but I know
> they are working on the issue, if not fixed already.
>
> 5 PM today, Wednesday, (Eastern) is the deadline, unless someone speaks
> up that they need a few extra hours.
>
> And then we begin "quiet week". This is a good time for committers and
> adopters to do some final testing. Even if a bad bug or regression was
> found, and could not be fixed in "common repo" due to being too late,
> projects can always produce their own update sites with patched
> features, or work on documenting workarounds.  Better to know ahead of
> time, than be surprised. Remember, any requests for respins need to go
> through the formal exception process, and it has to be something pretty
> big that can not be fixed by a normal patch feature, or similar.
>
> While there is no formal "Final Daze" document for service releases, it
> would be good for simrel engineers to review the main one for Juno, at
>
http://wiki.eclipse.org/Juno/Final_Daze
>
> The principles are the same ... clean up old stuff so mirrors don't get
> full. Promote zips and repositories early to make sure they get well
> propagated to mirrors but "leave invisible" until Friday, 9/28, so we do
> not prematurely "release" anything before its time, in an uncoordinated
> fashion that's confusing to end-users (if not the rest of us).
>
> Don't forget, if any of you changed or fixed substantial parts of your
> "help docs", you may want to open a bug in cross-project list to have
> webmasters update the info center for Juno SR1.
>
> Lastly, remember to change the repository reports ... I still see one
> missing "about.html" file ....
>
http://build.eclipse.org/simrel/juno/reporeports/
>
> Thanks everyone,
>
>
> _______________________________________________
> 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