You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2012/06/11 20:57:19 UTC
[jira] [Created] (LUCENE-4134) modify release process/scripts to
use svn for rc/release publishing (svnpubsub)
Hoss Man created LUCENE-4134:
--------------------------------
Summary: modify release process/scripts to use svn for rc/release publishing (svnpubsub)
Key: LUCENE-4134
URL: https://issues.apache.org/jira/browse/LUCENE-4134
Project: Lucene - Java
Issue Type: Task
Reporter: Hoss Man
By the end of 2012, all of www.apache.org *INCLUDING THE DIST DIR* must be entirely managed using "svnpubsub" ... our use of the Apache CMS for lucene.apache.org puts us in compliance for our main website, but the dist dir use for publishing release artifacts also needs to be manaved via svn.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-4134) modify release process/scripts to
use svn for rc/release publishing (svnpubsub)
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293001#comment-13293001 ]
Hoss Man commented on LUCENE-4134:
----------------------------------
Ah ... sorry ... i thought you were saying "we shouldn't add automation for this" ... didn't realize you ment "i don't use the automation we currently have"
bq. I think we should still lay out the new instructions on the wiki for people who dont want scripts svn committing for them, thats all.
+1
> modify release process/scripts to use svn for rc/release publishing (svnpubsub)
> -------------------------------------------------------------------------------
>
> Key: LUCENE-4134
> URL: https://issues.apache.org/jira/browse/LUCENE-4134
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Hoss Man
>
> By the end of 2012, all of www.apache.org *INCLUDING THE DIST DIR* must be entirely managed using "svnpubsub" ... our use of the Apache CMS for lucene.apache.org puts us in compliance for our main website, but the dist dir use for publishing release artifacts also needs to be manaved via svn.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-4134) modify release process/scripts to
use svn for rc/release publishing (svnpubsub)
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292997#comment-13292997 ]
Robert Muir commented on LUCENE-4134:
-------------------------------------
Hoss: right I'm saying i dont use that script :)
I think we should still lay out the new instructions on the wiki for people who dont want scripts svn committing for them, thats all.
> modify release process/scripts to use svn for rc/release publishing (svnpubsub)
> -------------------------------------------------------------------------------
>
> Key: LUCENE-4134
> URL: https://issues.apache.org/jira/browse/LUCENE-4134
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Hoss Man
>
> By the end of 2012, all of www.apache.org *INCLUDING THE DIST DIR* must be entirely managed using "svnpubsub" ... our use of the Apache CMS for lucene.apache.org puts us in compliance for our main website, but the dist dir use for publishing release artifacts also needs to be manaved via svn.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-4134) modify release process/scripts to
use svn for rc/release publishing (svnpubsub)
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292988#comment-13292988 ]
Robert Muir commented on LUCENE-4134:
-------------------------------------
I agree we should do the first part. As for the second part, i personally dont want to use any scripts that ssh or svn commit automatically so its no problem for me.
I think instead we should just have instructions on where we should commit things manually in ReleaseTODO etc. If someone wants to add automation thats great, but I just don't like automation when it comes to my passwords.
> modify release process/scripts to use svn for rc/release publishing (svnpubsub)
> -------------------------------------------------------------------------------
>
> Key: LUCENE-4134
> URL: https://issues.apache.org/jira/browse/LUCENE-4134
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Hoss Man
>
> By the end of 2012, all of www.apache.org *INCLUDING THE DIST DIR* must be entirely managed using "svnpubsub" ... our use of the Apache CMS for lucene.apache.org puts us in compliance for our main website, but the dist dir use for publishing release artifacts also needs to be manaved via svn.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-4134) modify release process/scripts to
use svn for rc/release publishing (svnpubsub)
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292994#comment-13292994 ]
Hoss Man commented on LUCENE-4134:
----------------------------------
rmuir: doesn't the automation already exist in "buildAndPushrelease.py" ? ... doesn't that automatically scp to RCs to people.apache.org:~you/public_html/staging_area/ ?
i'm just suggesting we change that to do the svn commit to https://dist.apache.org/repos/dist/dev/lucene ... the RCs are still "uploaded" automaticly, they would just start geting "uploaded" to an INFRA blessed location that would make it easier to (manually) publish them post-VOTE with an "svn mv"
> modify release process/scripts to use svn for rc/release publishing (svnpubsub)
> -------------------------------------------------------------------------------
>
> Key: LUCENE-4134
> URL: https://issues.apache.org/jira/browse/LUCENE-4134
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Hoss Man
>
> By the end of 2012, all of www.apache.org *INCLUDING THE DIST DIR* must be entirely managed using "svnpubsub" ... our use of the Apache CMS for lucene.apache.org puts us in compliance for our main website, but the dist dir use for publishing release artifacts also needs to be manaved via svn.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-4134) modify release process/scripts to
use svn for rc/release publishing (svnpubsub)
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292986#comment-13292986 ]
Hoss Man commented on LUCENE-4134:
----------------------------------
Recent email from INFRA...
{noformat}
> 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
...
> 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.
{noformat}
Some docs...
http://www.apache.org/dev/release.html#upload-ci
At a minimum we need to open a Jira with INFRA when we are ready for them to setup "https://dist.apache.org/repos/dist/release/lucene" and start using it for subsequent release publishing (instead of copying to the magic "dist" dir on people.apache.org and waiting for rsync. But as part of this new process there will also be a "https://dist.apache.org/repos/dist/dev/lucene" directory where release candidates can be put for review (instead of people.apache.org/~releasemanager/...), and if/when they are voted successfully a simple "svn mv" to dist/release/lucene makes them official and pushes them to the mirrors.
So we should also change our release scripts to start svn committing the release candidates there instead of scping to people.apache.org
> modify release process/scripts to use svn for rc/release publishing (svnpubsub)
> -------------------------------------------------------------------------------
>
> Key: LUCENE-4134
> URL: https://issues.apache.org/jira/browse/LUCENE-4134
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Hoss Man
>
> By the end of 2012, all of www.apache.org *INCLUDING THE DIST DIR* must be entirely managed using "svnpubsub" ... our use of the Apache CMS for lucene.apache.org puts us in compliance for our main website, but the dist dir use for publishing release artifacts also needs to be manaved via svn.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org