I didn't want to confuse anyone... http://download.eclipse.org/releases/staging/ - unfortunately both is 'kind of' true ;-)
Staging is used for making aggregation build results available whenever there is a change in the org.eclipse.simrel.build Git repository and the aggregation build is successful, UNLESS we are in the last phase of the milestone like now. Between +3 day and the release on Friday the content in staging isn't updated and the Hudson aggregation jobs are disabled. One reason for this is to allow to build the EPP packages, another reason is to allow for better testing of the p2 repository. In other words: At the moment /releases/staging contains what will be released as "M3" tomorrow. Before the release day the content of staging is being copied to the release directory (in that case a directory below /releases/mars/...) to give the Eclipse mirrors some time to sync. On release day the new content is added to /releases/mars/... and made available to the public. /releases/mars itself is a composite p2 repository and contains the last milestone builds. Usually at the weekend after the release the Hudson aggregation jobs for /releases/staging are enabled again. From this point on it is possible that the content of this repository changes. Maybe this explains better how it works... if not... feel free to ask again. Regards, Markus On Thu, Nov 13, 2014 at 2:54 PM, Mickael Istria <mist...@redhat.com> wrote: > On 11/13/2014 02:27 PM, Markus Knauer wrote: > > Hi Mickael, > > Hi, > > this document in the wiki should describe what you are looking for: > https://wiki.eclipse.org/SimRel/Overview > > The 'nightly' aggregation build output of the current Simultaneous > Release is always available from the p2 repository at > http://download.eclipse.org/releases/staging/. > Hope that helps, > > Kind of ;) > So I'm a bit confused now. An earlier mail said that releases/staging was > the M3 build candidate (build candidate == staging in my understanding of > staging). And now you tell me that staging is actually the latest snapshot > from CI... That seems strange to me as I would expect the build > candidate/staging site to be immutable until build is released, whereas I > would expect the snapshot site to change independently of the staging > repository status. > Aren't we missing a step here? > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> > My blog <http://mickaelistria.wordpress.com> - My Tweets > <http://twitter.com/mickaelistria> > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
