[
https://issues.apache.org/jira/browse/SQOOP-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-1536:
-----------------------------------
Fix Version/s: no-release
> Suggestion for release process
> ------------------------------
>
> Key: SQOOP-1536
> URL: https://issues.apache.org/jira/browse/SQOOP-1536
> Project: Sqoop
> Issue Type: Improvement
> Environment:
> https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release#HowtoRelease-Stagethereleaseartifacts
> https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release+Sqoop2
> Reporter: Sebb
> Priority: Minor
> Fix For: no-release
>
>
> The release process notes suggest using people.apache.org home directory for
> staging release votes. This is the traditional way to do things.
> However there is now a specific area in SVN that can be used for this purpose:
> https://dist.apache.org/repos/dist/dev/sqoop/
> (writable by all sqoop committers)
> The advantage of this is that it is in the same SVN repo as the release tree,
> i.e.
> https://dist.apache.org/repos/dist/release/sqoop/
> This means that when the vote passes, there is no need to checkout the
> existing release tree in order to update it. Nor is it necessary to upload
> the artifacts again.
> Instead, one can use "svn move" to move the files across. And one can use
> svnmucc to batch the moves so they all occur as part of a single transaction.
> This method reduces the need to upload/download files, and makes it easier to
> ensure that the files that were voted on are the ones that are eventually
> published.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
