Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Respin RC4 or Test Spin Request

Thanks Ed. I approve so ecoretools can (try) and re-join the train.

I'll start the rebuild approximately 2 pm eastern. I would expect it to complete approx. 4 pm eastern.

We will count this as the first "on demand exception" for final builds. But, if it is successful (early enough), I will promote to staging, and
roll out that new version of staging to mirrors for our official RC4 common site. I'd suggest that only the modeling EPP package
be rebuilt, if that's possible? [But, that's up to Markus, and I'm very open to suggestions ,,, but, we should be explicit].

Keep in mind, if anyone has changed anything in their repos, the build might still fail (for reasons unrelated to ecoretools)
and any other project will (still) be expected to fix any issues immediately (e.g. with an hour or so).  (See bug 316501 for
an example of a pesky project, web tools, changing their repo :)  ... just being open and honest.

So ... let's set a deadline ... if we have not gotten a good respin by, say, 9 PM Eastern, then RC4 will remain as it is. And the
modeling epp package will be built without it? Sound reasonable? I'd still be willing to work on a "final rebuild" that includes ecoretools  ...
but am reluctant to stay up all night baby-sitting it like last night. :)

Thanks everyone, good luck.

From: Ed Merks <ed.merks@xxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 06/10/2010 01:10 PM
Subject: [cross-project-issues-dev] Respin RC4 or Test Spin Request
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx


Given the issues with bad bits in the RC4 Ecore Tools build, and potentially even bad (though unreported) bits in RC3 build, it would seem like a good thing to respin RC4 or at least do a test spin to ensure that the final release builds will be problem free.  The Amalgamation Modeling depends on Ecore Tools so testing that this package is properly produced is especially important.

For those interested, please see this bugzilla for the details:

cross-project-issues-dev mailing list

Back to the top