[cross-project-issues-dev] latest aggregation build results
Where can I find the p2 repository created by the latest succeeded aggregation build https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/570/ ? The build log lists the correct JGit and EGit IUs for RC4 with version 3.0.0.201306101825-r but I can't find them in the staging repository http://download.eclipse.org/releases/staging -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] latest aggregation build results
The log file of the aggregator build shows: [echoproperties] AGGREGATOR_RESULTS=/shared/simrel/kepler/aggregation … [exec] Making the aggregated metadata repository final at file:/shared/simrel/kepler/aggregation/final [exec] Making the aggregated artifact repository final at file:/shared/simrel/kepler/aggregation/final so I would assume that you’ll find it below of /shared/simrel/kepler/aggregation/final/ ;) Sven Von: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von Matthias Sohn Gesendet: Dienstag, 11. Juni 2013 13:52 An: Cross project issues Betreff: [cross-project-issues-dev] latest aggregation build results Where can I find the p2 repository created by the latest succeeded aggregation build https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/570/ ? The build log lists the correct JGit and EGit IUs for RC4 with version 3.0.0.201306101825-r but I can't find them in the staging repository http://download.eclipse.org/releases/staging -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] latest aggregation build results
Forgotten to mention…the last /releases/staging publishing was done at 2013-06-10 09:13 so I would assume that the next publish task will be done soon (the current time at build.eclipse.org is Tue Jun 11 08:36:50 EDT 2013). Von: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von sven.rottst...@sungard.com Gesendet: Dienstag, 11. Juni 2013 14:16 An: cross-project-issues-dev@eclipse.org Betreff: Re: [cross-project-issues-dev] latest aggregation build results The log file of the aggregator build shows: [echoproperties] AGGREGATOR_RESULTS=/shared/simrel/kepler/aggregation … [exec] Making the aggregated metadata repository final at file:/shared/simrel/kepler/aggregation/final [exec] Making the aggregated artifact repository final at file:/shared/simrel/kepler/aggregation/final so I would assume that you’ll find it below of /shared/simrel/kepler/aggregation/final/ ;) Sven Von: cross-project-issues-dev-boun...@eclipse.orgmailto:cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von Matthias Sohn Gesendet: Dienstag, 11. Juni 2013 13:52 An: Cross project issues Betreff: [cross-project-issues-dev] latest aggregation build results Where can I find the p2 repository created by the latest succeeded aggregation build https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/570/ ? The build log lists the correct JGit and EGit IUs for RC4 with version 3.0.0.201306101825-r but I can't find them in the staging repository http://download.eclipse.org/releases/staging -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] latest aggregation build results
Steffen pointed me here http://build.eclipse.org/simrel/kepler/aggregation/final/ and this looks good, thanks for the hints -- Matthias On Tue, Jun 11, 2013 at 2:37 PM, sven.rottst...@sungard.com wrote: Forgotten to mention…the last /releases/staging publishing was done at 2013-06-10 09:13 so I would assume that the next publish task will be done soon (the current time at build.eclipse.org is Tue Jun 11 08:36:50 EDT 2013). ** ** *Von:* cross-project-issues-dev-boun...@eclipse.org [mailto: cross-project-issues-dev-boun...@eclipse.org] *Im Auftrag von * sven.rottst...@sungard.com *Gesendet:* Dienstag, 11. Juni 2013 14:16 *An:* cross-project-issues-dev@eclipse.org *Betreff:* Re: [cross-project-issues-dev] latest aggregation build results ** ** The log file of the aggregator build shows: [echoproperties] AGGREGATOR_RESULTS=/shared/simrel/kepler/aggregation … [exec] Making the aggregated metadata repository final at file:/shared/simrel/kepler/aggregation/final [exec] Making the aggregated artifact repository final at file:/shared/simrel/kepler/aggregation/final ** ** so I would assume that you’ll find it below of /shared/simrel/kepler/aggregation/final/ ;) ** ** Sven ** ** *Von:* cross-project-issues-dev-boun...@eclipse.org [ mailto:cross-project-issues-dev-boun...@eclipse.orgcross-project-issues-dev-boun...@eclipse.org] *Im Auftrag von *Matthias Sohn *Gesendet:* Dienstag, 11. Juni 2013 13:52 *An:* Cross project issues *Betreff:* [cross-project-issues-dev] latest aggregation build results ** ** Where can I find the p2 repository created by the latest succeeded aggregation build https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/570/ ?** ** The build log lists the correct JGit and EGit IUs for RC4 with version 3.0.0.201306101825-r but I can't find them in the staging repository http://download.eclipse.org/releases/staging ** ** -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Missing release information for some Kepler projects
On Tue, Jun 11, 2013 at 11:13 PM, Ed Willink e...@willink.me.uk wrote: Hi I think a certain amount of self-policing is possible for the many 'minor' projects. Their consumers are surely well aware how stable builds are and how much credible development is going on. Concerned projects should perhaps contact the EMO at M6 to complain about the lack of M4 project plan and request a firm commitment to either a frozen/point/minor/major release. For 'major' projects I'm not sure what can be done. Surely EGIT has enough experienced committers to know that a major new release at SR2 RC3 is not the way maintenance is done? Perhaps the EMO should enforce only PMC-approved major or point version changes after M6, and AB-approved after M7. NB thais includes SR1 and SR2 that should be maintence. If there is a new release it is new not maintenance. I am not aware of any EGit major release we would have done for a SR2. We release roughly every 3 months and we don't have the bandwidth to maintain several versions in parallel. So far we did major versions with SR0 and delivered minor version releases with SR1, SR2 and an additional one in Dec. -- Matthias ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Missing release information for some Kepler projects
I don't know about the SRs but I remember that EGit updated from 1.3 to 2.0 in Juno RC2 or RC3. For me this feels like a pretty risky change for an RC. I don't mean to point the finger at EGit, I just think we should agree that RC1 should really be a release candidate, i.e. almost the thing that is going to be released except for some minor fixes. The code should cool down after that point. At least major versions should not change anymore. Ralf ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
