[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[mat-dev] Is the cbi-mat-nightly build job still needed?
- From: "Tsvetkov, Krum" <krum.tsvetkov@xxxxxxx>
- Date: Mon, 19 Sep 2011 15:45:37 +0200
- Accept-language: en-US, de-DE
- Acceptlanguage: en-US, de-DE
- Delivered-to: email@example.com
- Thread-index: Acxy8dzQ7JzrXwy8T6uAdVsm89QPNAD3jbkw
- Thread-topic: Is the cbi-mat-nightly build job still needed?
I am forwarding an e-mail from the cross-project-issues-dev list.
As it seems the Athena CBI is going to be terminated.
I would like to delete also the MAT Hudson job building with Athena - https://hudson.eclipse.org/hudson/job/cbi-mat-nightly/. We have made already the last release out of the Tycho build job, and I personally do not see any reason to keep the CBI build also.
Are there any objections to delete the job, or any reasons not to do it?
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Mittwoch, 14. September 2011 17:21
Subject: [cross-project-issues-dev] Is it time to terminate/archive Athena Common Build project?
Development on Athena stopped some time ago and the project is quite
dead. It's time to start the termination/archival process.
I see several jobs in Hudson that appear to use the Athena CBI. I'm not
sure how these jobs might be affected by termination but given that
there has been no activity on the Athena project itself, I tend to
believe that these jobs are either old and stale themselves, or
A few of those jobs haven't run in months. Perhaps this is a good
opportunity to kill those old jobs if they're not required. Can somebody
speak up regarding how we go about doing that?
The termination process tends to take a while (months), so there's no
urgency here if you have an Athena-based build that you feel needs to be
migrated to something like Maven/Tycho/Minerva. Realistically, we
likely won't run the actual Termination Review until the end of December
or early January.
There's plenty of time for somebody to step up and tell us to stop. Of
course, given that development on the project has completely dried up,
we'll need somebody to step-up and take over development responsibilities.
I think that it's fair to say that Athena helped a lot of projects
create successful builds. Athena was only ever intended to be a step
towards an improved build experience, and I think that it's fair to say
that the intentions were exceeded. Much thanks to Nick, Kim, Andrew,
Andrew, and Denis for making it happen.
The Eclipse Foundation
cross-project-issues-dev mailing list