Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Kepler's final staging repository is complete

Hi All,

It's totally embarrassing but a user's have just reported that I made a fatal typo in a last minute fix. I fear we can't ship with this typo in place. Is there any chance to get a contribution into Kepler with a fix to this fix?

The bug that was found late and that I fixed two days ago is:

	410409: CDOClientIndications can arrive before session is fully active

Instead of checking for LifecycleState.ACTIVATING I wrote DEACTIVATING in a moment of pressure and unconciousness:

    if (session.getLifecycleState() == LifecycleState.ACTIVATING)
      LifecycleUtil.waitForActive(session, 10000L);

That not only doesn't fix the (timing-related, hard to test) original problem, worse, it tends to add 10 second delays in other situations. I already wondered why our tests took so much longer than usual, but I blamed the build server load during the last contribution opportunities ;-(

I'm very sorry for the inconvenience that I might cause!!!!!!!!



Am 13.06.2013 00:36, schrieb David M Williams:
Here we are, at (near) the end of RC4 already! EPP packages will be complete in a day or two.
Everyone, and especially anyone who pushed changes late in the day, should confirm the staging repo contains what you
expect it to.

The final repo-reports are available at the usual place:

For those of you with "missing legal files" ... it is between you and the EMO if they will grant an exception for the
I know of only one project that as requested it (bug 401273).

As for other things, such as unsigned jars, technically you should work with your PMC and planning representative to ask
for exceptions,
but suspect if you have not done so by now, it's simply a matter that you don't care. But, if you do, the reference is
Beyond that, I'll leave it up to the rest of the Planning Council to raise objections if they think any violations are
so egregious it deserves discussing whether or not to included in the common repo.

Remember that as we enter "quiet week" we do NOT promote the builds to their usual place,  since to do so is basically
making the release available early.
The purpose of "quiet week" is partially to allow adopters to do final acceptance testing, but to also serve as a buffer
in case a build is required -- but, rebuilds are very risky, and rare, so has to be an especially bad bug (such as one
which prevents install or update from working, or perhaps where one project prevents another project from working).
Otherwise, the extra time is for projects to prepare "hot fix" feature patches to be available from their own project

If you like to read wordy, but possibly educational, documents, don't forget about

Thanks everyone. Good luck with your final testing and wrap-up.

cross-project-issues-dev mailing list

Back to the top