Community
Participate
Working Groups
The appropriate install for use by a milestone build are in http://download.eclipse.org/releases/staging but this is not listed in the default update sites, rather an inappropriate release site. Therefore every user of a milestone build must correct this 'bug' before proceding. Suggest that Milestone builds use staging or a redirection to staging, and that the Release Candidate builds use the target update site.
No, release train milestones are found in the same location where the final release train will appear, for example: http://download.eclipse.org/releases/juno The staging repository contains a random pre-milestone release train build which is quite possibly broken. David correct me if I'm wrong, but I don't think we should add this.
correct, "staging" is a frequently changed pre-(next)-milestone build and wouldn't be suitable for majority of people to use as target or to get automatic updates from. It is really for early testing by a small subset of committers, and certainly not for routine use by users, even "early tester" users.
Perhaps staging is the wrong suggestion, or perhaps it should be provided but as a disabled entry. (I always have to Google the correct spelling.) The current state of the art is that at M4 an install gets Indigo plugins. In the case of EGIT, which doesn't provide downloadable repo ZIPs, this is really bad news. Surely an install on M4 should get a best approximation to M4 all round?
(In reply to comment #3) > The current state of the art is that at M4 an install gets Indigo plugins. In > the case of EGIT, which doesn't provide downloadable repo ZIPs, this is really > bad news. Surely an install on M4 should get a best approximation to M4 all > round? Hmm, it just dawned on me this could be an EPP issue. The M4 Eclipse SDK includes only the "Juno" repository which contains the M4 contents from the entire release train. What download are you using? I certainly agree with your intent that using M4 I should be able to easily install other M4 content without having to know a magic URL.
Between +1 and EPP I use the platform plus some downloaded P2 All-In-One repos with "Available Sites" to fill in the gaps. Thereafter I sometimes use EPP, with P2 repos and again "Available Sites". But eventually I revert to 3.8Mx since 4.2Mx is not yet acceptable to me ergonomically (bug 344029). For all of the above, "Available Sites" tends to give poor choices requiring the downloaded repos.
(In reply to comment #5) I suspect there are several issues going on with what Edward sees, and I'll try to sort some of them out, inline, below ... but, no improvements would add "staging" to any of the built-in repos. > Between +1 and EPP I use the platform ... "between +1 and EPP" will always be a tough time; there is no single repo, yet, that has all the right (pre-milestone) content (if nothing else, at end of +2 day, staging might have +2 content, but not yet +3, etc.). But, on/after the simultaneioius milestone, then the repo at http://download.eclipse.org/releases/juno/ does have the milestone content, as John said. And that repo is "built-in" to the Eclipse SDK ... at least, the one for the 4.2 stream, for the Juno release. Not sure what the "3.8 platform" has built in, but think its the same for now, but being discussed some in bug 363948. > plus some downloaded P2 All-In-One repos > with "Available Sites" to fill in the gaps. > .... > For all of the above, "Available Sites" tends to give poor choices requiring > the downloaded repos. Not sure what you mean by "all in one repos", but suspect you mean zipped up p2 repositories from the project's download pages? If so, the "poor choices" are coming from the them and you'd need to open bugs on them. We purposely no longer "clutter up" the main common repo with everyone's "suggested repos" ... partially since they were so inaccurate, as discussed in bug 358415, and partially since there were so many that have a cascading effect, and since we want it to be the "products" responsibility to provide the repos they want their users to use, ... not each and every project feature. > The current state of the art is that at M4 an install gets Indigo plugins. I do not see how this can be true ... so, maybe I am misunderstanding? > In the case of EGIT, which doesn't provide downloadable repo ZIPs, this is > really bad news. I suggest you open an EGIT bug or feature request for them to provide a zipped repo. > Surely an install on M4 should get a best approximation to M4 all > round? In certainly should after the simultaneious milestone ... as mentioned above, the days between +1 and EPP will not and not sure how we could ever make that work very well for anyone (at most, only fit a few's requirements) ... but will suggest you just book mark http://download.eclipse.org/releases/staging/ either in your browser for copy/paste, or, better yet, in an exported "book marked repositories" from your IDE so next time you start fresh, you can import your own list of favorites oF commonly used sites. So, unless I'm misunderstanding ... I suggest this be closed as "won't fix" and then more specific bugs opened for other cases as I suggest above. And do let us (or, at least me :) know what those other bugs are. These are definitely important issues you are mentioning ... just not related to "staging".
Agreed, closing.
