Author: stefanegli
Date: Tue Sep 22 09:43:04 2015
New Revision: 1704495
URL: http://svn.apache.org/viewvc?rev=1704495&view=rev
Log:
@no-jira : added commend about making sure end-of-line encoding does not change
on svn import
Modified:
sling/site/trunk/content/documentation/development/release-management.mdtext
Modified:
sling/site/trunk/content/documentation/development/release-management.mdtext
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/release-management.mdtext?rev=1704495&r1=1704494&r2=1704495&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/development/release-management.mdtext
(original)
+++
sling/site/trunk/content/documentation/development/release-management.mdtext
Tue Sep 22 09:43:04 2015
@@ -178,6 +178,7 @@ If the vote fails, or you decide to redo
If the vote passes:
1. Commit the released artifacts to
[https://dist.apache.org/repos/dist/release/sling/](https://dist.apache.org/repos/dist/release/sling/)
which is replicated to
[http://www.apache.org/dist/sling/](http://www.apache.org/dist/sling/) quickly
via svnpubsub. Hint: use svn import to avoid having to checkout the whole
folder first. The easiest to do this is to get the released artifact using the
check script (check_staged_release.sh) and then simply copy the
artifacts from the downloaded folder to your local checkout folder. Make sure
to not add the checksum files for the signature file \*.asc.\*).
+ * Make sure to *not* change the end-of-line encoding of the .pom when
uploaded via svn import! Eg when a windows style eol encoded file is uploaded
with the setting '*.pom = svn:eol-style=native' this would later fail the
signature checks!
1. Delete the old release artifacts from that same dist.apache.org svn folder
(the dist directory is archived)
1. Login to [https://repository.apache.org](https://repository.apache.org)
with your Apache SVN credentials. Click on *Staging*. Find your closed staging
repository and select it by checking the select box. Select the *Releases*
repository from the drop-down list and click *Release* from the menu above.
1. Once the release is promoted click on *Repositories*, select the *Releases*
repository and validate that your artifacts are all there.
