Re: Mandatory svnpubsub migration by Jan 2013
On 2012-03-13, Nicolas Lalevée wrote: Our ant dist has been migrated. Thank you Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Mandatory svnpubsub migration by Jan 2013
Our ant dist has been migrated. Nicolas Le 2 mars 2012 à 14:14, Nicolas Lalevée a écrit : By the way, I have noticed that some symlinks still exist: antlibs/antunit/apache-ant-antunit-current-* - binaries/* et - source/* antlibs/dotnet/apache-ant-dotnet-current-* - binaries/* et - source/* antlibs/antunit/binaries/README.html - ../README.html antlibs/antunit/source/README.html - ../README.html When I'll push our artifacts to the new svn, by default I won't create copies of symlinked files. But if somebody thinks copies are deserved, he could do svn cp after the migration. Nicolas Le 2 mars 2012 à 14:00, Nicolas Lalevée a écrit : issue created: https://issues.apache.org/jira/browse/INFRA-4509 Nicolas Le 23 févr. 2012 à 17:29, Nicolas Lalevée a écrit : Le 21 févr. 2012 à 16:52, Stefan Bodewig a écrit : On 2012-02-20, Nicolas Lalevée wrote: We then just need to create an INFRA ticket asking for the transition. I guess we want the svn notifications sent to notificati...@ant.apache.org. Once the infra has created our space, we would just need to check in the current content of our dist. Currently KEYS is a (sym)link to a checked out copy from somewhere else. Once we have svnpubsub in place I'd suggest we make the dist repository the canonical place for storing PGP keys. +1 A side effect will probably that ivy/updatesite/trunk/dist will disappeared from our svn. Maybe it would help in the management of the new Eclipse update site [3] [4]. Is this something that has to be resolved before the transition? No it doesn't. It is quite independant. And finally I don't think having it in svn will help much technically. But for this new Eclipse update site, I'll need to write some doc about it; I prefer write it once with already reference to the dist-svn. Just me being a little lazy :) Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Mandatory svnpubsub migration by Jan 2013
issue created: https://issues.apache.org/jira/browse/INFRA-4509 Nicolas Le 23 févr. 2012 à 17:29, Nicolas Lalevée a écrit : Le 21 févr. 2012 à 16:52, Stefan Bodewig a écrit : On 2012-02-20, Nicolas Lalevée wrote: We then just need to create an INFRA ticket asking for the transition. I guess we want the svn notifications sent to notificati...@ant.apache.org. Once the infra has created our space, we would just need to check in the current content of our dist. Currently KEYS is a (sym)link to a checked out copy from somewhere else. Once we have svnpubsub in place I'd suggest we make the dist repository the canonical place for storing PGP keys. +1 A side effect will probably that ivy/updatesite/trunk/dist will disappeared from our svn. Maybe it would help in the management of the new Eclipse update site [3] [4]. Is this something that has to be resolved before the transition? No it doesn't. It is quite independant. And finally I don't think having it in svn will help much technically. But for this new Eclipse update site, I'll need to write some doc about it; I prefer write it once with already reference to the dist-svn. Just me being a little lazy :) Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Mandatory svnpubsub migration by Jan 2013
By the way, I have noticed that some symlinks still exist: antlibs/antunit/apache-ant-antunit-current-* - binaries/* et - source/* antlibs/dotnet/apache-ant-dotnet-current-* - binaries/* et - source/* antlibs/antunit/binaries/README.html - ../README.html antlibs/antunit/source/README.html - ../README.html When I'll push our artifacts to the new svn, by default I won't create copies of symlinked files. But if somebody thinks copies are deserved, he could do svn cp after the migration. Nicolas Le 2 mars 2012 à 14:00, Nicolas Lalevée a écrit : issue created: https://issues.apache.org/jira/browse/INFRA-4509 Nicolas Le 23 févr. 2012 à 17:29, Nicolas Lalevée a écrit : Le 21 févr. 2012 à 16:52, Stefan Bodewig a écrit : On 2012-02-20, Nicolas Lalevée wrote: We then just need to create an INFRA ticket asking for the transition. I guess we want the svn notifications sent to notificati...@ant.apache.org. Once the infra has created our space, we would just need to check in the current content of our dist. Currently KEYS is a (sym)link to a checked out copy from somewhere else. Once we have svnpubsub in place I'd suggest we make the dist repository the canonical place for storing PGP keys. +1 A side effect will probably that ivy/updatesite/trunk/dist will disappeared from our svn. Maybe it would help in the management of the new Eclipse update site [3] [4]. Is this something that has to be resolved before the transition? No it doesn't. It is quite independant. And finally I don't think having it in svn will help much technically. But for this new Eclipse update site, I'll need to write some doc about it; I prefer write it once with already reference to the dist-svn. Just me being a little lazy :) Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Mandatory svnpubsub migration by Jan 2013
Le 21 févr. 2012 à 16:52, Stefan Bodewig a écrit : On 2012-02-20, Nicolas Lalevée wrote: We then just need to create an INFRA ticket asking for the transition. I guess we want the svn notifications sent to notificati...@ant.apache.org. Once the infra has created our space, we would just need to check in the current content of our dist. Currently KEYS is a (sym)link to a checked out copy from somewhere else. Once we have svnpubsub in place I'd suggest we make the dist repository the canonical place for storing PGP keys. +1 A side effect will probably that ivy/updatesite/trunk/dist will disappeared from our svn. Maybe it would help in the management of the new Eclipse update site [3] [4]. Is this something that has to be resolved before the transition? No it doesn't. It is quite independant. And finally I don't think having it in svn will help much technically. But for this new Eclipse update site, I'll need to write some doc about it; I prefer write it once with already reference to the dist-svn. Just me being a little lazy :) Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Mandatory svnpubsub migration by Jan 2013
On 2012-02-20, Nicolas Lalevée wrote: We already did the migration of our sites to svnpubsub. We still need to migrate our dist folder. AFAIU it is quite trivial. Instead of putting files manually into people.a.o:/www/www.apache.org/dist/ant/ we would have to commit them into a svn [1]. Deleting files from our main dist is just about doing some svn rm. And the ASF archive doesn't apply the svn rm so everything committed once gets into the archive. That's my understanding as well. And if we are willing to, we have at our disposal de dev space where release to be voted upon can be staged [2]. And once the vote pass, just a svn cp dev/xxx release/xxx svn rm dev/xxx does the actually publishing (it seems there are restrictions on svn mv). I know I'd be using that rather than my user space on people.ao A thing to note though: I guess that with svnpubsub, we cannot have symlinks The -current symlinks are frownded upon by now anyway. They seem to mess up mirrors. We could easily live without them IMHO. We then just need to create an INFRA ticket asking for the transition. I guess we want the svn notifications sent to notificati...@ant.apache.org. Once the infra has created our space, we would just need to check in the current content of our dist. Currently KEYS is a (sym)link to a checked out copy from somewhere else. Once we have svnpubsub in place I'd suggest we make the dist repository the canonical place for storing PGP keys. A side effect will probably that ivy/updatesite/trunk/dist will disappeared from our svn. Maybe it would help in the management of the new Eclipse update site [3] [4]. Is this something that has to be resolved before the transition? If so, don't rush it - we still have a few months until the migration must be complete. I willing to ask for the migration this week unless there's some concern. No concerns except for the Eclipse update site that I don't understand anyway ;-) Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Mandatory svnpubsub migration by Jan 2013
We already did the migration of our sites to svnpubsub. We still need to migrate our dist folder. AFAIU it is quite trivial. Instead of putting files manually into people.a.o:/www/www.apache.org/dist/ant/ we would have to commit them into a svn [1]. Deleting files from our main dist is just about doing some svn rm. And the ASF archive doesn't apply the svn rm so everything committed once gets into the archive. As it would be managed by svnpubsub, changes will be reflected quite immediately to www.apache.org, as it does for our website. It won't change the mirroring delay though. And if we are willing to, we have at our disposal de dev space where release to be voted upon can be staged [2]. And once the vote pass, just a svn cp dev/xxx release/xxx svn rm dev/xxx does the actually publishing (it seems there are restrictions on svn mv). A thing to note though: I guess that with svnpubsub, we cannot have symlinks (I have not ask the infra, not find any mention of them in the sparse doc). We have some in people.a.o:/www/www.apache.org/dist/ant/. On the other hand they doesn't appear on the site http://www.apache.org/dist/ant/. I guess it's OK. We then just need to create an INFRA ticket asking for the transition. I guess we want the svn notifications sent to notificati...@ant.apache.org. Once the infra has created our space, we would just need to check in the current content of our dist. A side effect will probably that ivy/updatesite/trunk/dist will disappeared from our svn. Maybe it would help in the management of the new Eclipse update site [3] [4]. I willing to ask for the migration this week unless there's some concern. Nicolas [1] https://dist.apache.org/repos/dist/release/ [2] https://dist.apache.org/repos/dist/dev/ [3] http://svn.apache.org/repos/asf/ant/ivy/updatesite/branches/p2repo-only/ [4] https://issues.apache.org/jira/browse/IVYDE-281 Le 8 févr. 2012 à 13:26, Joe Schaefer a écrit : [PLEASE DO NOT RESPOND TO THIS POST! DIRECT ALL FURTHER INQUIRIES TO infrastruct...@apache.org] FYI: infrastructure policy regarding website hosting has changed as of November 2011: we are requiring all websites and dist/ dirs to be svnpubsub or ASF CMS backed by the end of 2012. If your PMC has already met this requirement congratulations, you can ignore the remainder of this post. As stated on http://www.apache.org/dev/project-site.html#svnpubsub we are migrating our webserver infrastructure to 100% svnpubsub over the course of 2012. If your site does not currently make use of this technology, it is time to consider a migration effort, as rsync-based sites will be PERMANENTLY FROZEN in Jan 2013 due to infra disabling the hourly rsync jobs. While we recommend migrating to the ASF CMS [0] for Anakia based or Confluence based sites, and have provided tooling [1] to help facilitate this, we are only mandating svnpubsub (which the CMS uses itself). svnpubsub is a client-server system whereby a client watches an svn working copy for relevant commit notifications from the svn server. It subsequently runs svn up on the working copy, bringing in the relevant changes. sites that use static build technologies that commit the build results to svn are naturally compatible with svnpubsub; simply file a JIRA ticket with INFRA to request a migration: any commits to the resulting build tree will be instantly picked up on the live site. The CMS is a more elaborate system based on svnpubsub which provides a webgui for convenient online editing. Dozens of sites have already successfully deployed using the CMS and are quite happy with the results. The system is sufficiently flexible to accommodate a wide variety of choices regarding templating systems and storage formats, but most sites have standardized on the combination of Django and Markdown. Talk to infra if you would like to use the CMS in this or some other fashion, we'll see what we can do. NOTE: the policy for dist/ dirs for managing project releases is similar. We have setup a dedicated svn server for handling this, please contact infra when you are ready to start using it. HTH [0]: http://www.apache.org/dev/cms [1]: https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/ - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
