[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-commits
Subject:    svn commit: r1915016 - /subversion/site/staging/docs/community-guide/releasing.part.html
From:       dsahlberg () apache ! org
Date:       2023-12-31 10:10:40
Message-ID: 20231231101040.A877217BE2D () svn01-us-east ! apache ! org
[Download RAW message or body]

Author: dsahlberg
Date: Sun Dec 31 10:10:40 2023
New Revision: 1915016

URL: http://svn.apache.org/viewvc?rev=1915016&view=rev
Log:
In site/staging:

* docs/community-guide/releasing.part.html
  (#releasing-release): Add note how to add the release to reporter.a.o on the \
command line.


Modified:
    subversion/site/staging/docs/community-guide/releasing.part.html

Modified: subversion/site/staging/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1915016&r1=1915015&r2=1915016&view=diff
 ==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Sun Dec 31 \
10:10:40 2023 @@ -1249,7 +1249,11 @@ release.py clean-dist
 </p>
 <p>Submit the version number of the new release on <a
 href="https://reporter.apache.org/addrelease.html?subversion"
->reporter.apache.org</a>. (Can we automate that?)</p>
+>reporter.apache.org</a>. The following command 
+<pre>
+curl -u <b>USERNAME</b> "https://reporter.apache.org/addrelease.py?date=`date \
+%s`&committee=subversion&version=<b>VERSION</b>&xdate=`date +%F`" +</pre>
+will add the release, it should probably be added to release.py.</p>
 
 </div> <!-- releasing-upload -->
 


[prev in list] [next in list] [prev in thread] [next in thread]