Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] Re: [cross-project-issues-dev] Re-spin process

Pascal (and everyone),
Good questions. Just FYI, so far the Europa bits have not changed - there have been requests for re-spins and withdrawn requests and lots of email about it, but currently the Europa-matic is broken RED due to MDT/EODM. Once we have a green Europa-matic, then we have the additional question of what do we do with those bits - that's where your excellent questions come in...

First, let me answer a few of your questions:

Pascal Rapicault wrote:
- Are those re-spins put in place and lieu of where the Europa bytes were?
No, not yet; not until we (the Planning Council) decides that is a good idea.
If I try to download all of Europa now, what do/should I get?
The same bits you got on June 28th.
- Are the EPP packages rebuilt and should they be?
I think that if we release new bits via the Europa discovery site, we should release new EPP packages with those bits. But that's just my opinion.

Second, my opinions:
Personally I like the approach where Europa is a just a name and the
content is a moving target representing the latest and greatest versions of
the 21 projects that initially contributed until Ganymede ships. Of course
it is harder for developers to know which versions of a plug-in someone was
using, but the benefits for the community seems to be pretty high, and it
also means that we regularly re-spin putting a higher burden on the
I like this approach a lot - it matches well with the ease of distribution that the internet provides us. I'm not clear on your "harder for developers to know which versions of a plug-in" because each plug-in has a unique four part version number. Each re-spin that contributes new bits would provide a new four-part version number for those new bits. (I'm probably missing something subtle.)

As for the Europa coordinator: the overhead is fairly low, especially if the re-spins are not emergencies, and the overhead for Ganymede will be even lower. The "distribute to the leaves" philosophy of Europa and now Ganymede is a big help here: for Ganymede, the Gan-omatic will do a build, if the build fails, it will automatically remove the offending project and then build again; it will continue doing this until it gets a green build. It will notify all the project owners by email that they failed the build and were removed from the Ganymede update site. Very low overhead for me (the coordinator) because the computer is going to do all the work. Thomas Hallgren (Cloudsmith, Buckminster) is going to help me set this up.

- Bjorn

Back to the top