Re: [cross-project-issues-dev] Thanks for M3, on to M4!

[David M Williams <david_williams@xxxxxxxxxx>]

Thanks for volunteering to do this extra work, Paul .. I've opened bug 330134
https://bugs.eclipse.org/bugs/show_bug.cgi?id=330134

Just kidding (mostly) ... but your idea has some good points and not so good points. The not so good ... it really doesn't give much of an "early test" of our long term required UI and workflow, which is I think the main purpose for retaining several milestones.

But ... the good point ... it did remind me that not all artifacts have to be taking up prime, mirrored real estate, and that during these milestone rollouts would be a good time to experiment investigate moving some artifacts to the "archives server". Eventually of course, we will remove the milestones repositories (they do not need to be literally archived long term) but that might give us some confidence to start archiving some "real", released p2 repositories ... which we all should do at some point, eventually.

Is anyone archiving p2 repositories yet? Any volunteers for bug 330134 scripts (besides Paul? :)

Thanks for the discussion,




Paul Webster ---11/12/2010 02:11:41 PM---With space being a real issue (especially when mirroring) why not switch to a 2 repo system.

From: Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 11/12/2010 02:11 PM
Subject: Re: [cross-project-issues-dev] Thanks for M3, on to M4!
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

---

With space being a real issue (especially when mirroring) why not switch to a 2 repo system.

http://download.eclipse.org/releases/indigo would always contain the latest milestone, and only the one.  That way all the products' early adopters would not have to deal with the complexity of multiple repos/to many choices.

Then, an indigo milestone repo could be created to hold all of the Indigo milestones.  This second repo would be for those that need to go back for testing purposes, or people like me that have a 1-off problem that I haven't quite solved yet.  We all know we have to take extra steps, anyway.  As an added bonus, the webmasters can specifically exclude this rather large repo from mirroring ... on the expectation it's lower traffic than the current milestone of Indigo.  Indigo gets released, milestone repo goes away.

What do you think, should I open a bug to discuss?

Later,
PW

-- 
Paul Webster
Hi floor.  Make me a sammich! - GIR_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev