You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ju...@apache.org on 2019/03/11 11:35:43 UTC
svn commit: r1855211 -
/subversion/site/publish/docs/community-guide/releasing.part.html
Author: julianfoad
Date: Mon Mar 11 11:35:43 2019
New Revision: 1855211
URL: http://svn.apache.org/viewvc?rev=1855211&view=rev
Log:
* publish/docs/community-guide/releasing.part.html:
Don't use reporter.apache.org for pre-releases.
Modified:
subversion/site/publish/docs/community-guide/releasing.part.html
Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1855211&r1=1855210&r2=1855211&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Mon Mar 11 11:35:43 2019
@@ -1107,9 +1107,6 @@ releases using:
release.py clean-dist
</pre>
</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>
</div> <!-- releasing-upload -->
@@ -1195,6 +1192,9 @@ update links to the release announcement
<li><p>List the new release on
<tt>^/subversion/site/publish/docs/release-notes/release-history.html</tt>
</p></li>
+ <li><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></li>
</ul>
<p>In addition, if this is a new minor release X.Y.0:</p>
Re: svn commit: r1855211 - /subversion/site/publish/docs/community-guide/releasing.part.html
Posted by Julian Foad <ju...@apache.org>.
Daniel Shahaf wrote on 2019-03-13:
> julianfoad@apache.org wrote on Mon, 11 Mar 2019 11:35 +00:00:
> > Author: julianfoad
> > Date: Mon Mar 11 11:35:43 2019
> > New Revision: 1855211
> >
> > URL: http://svn.apache.org/viewvc?rev=1855211&view=rev
> > Log:
> > * publish/docs/community-guide/releasing.part.html:
> > Don't use reporter.apache.org for pre-releases.
>
> For what it's worth:
>
> reporter.a.o is AFAIK only used for drafting Board reports; I would
> expect the Board to care equally much about any release regardless of
> its alpha/beta/RC/GA status; therefore, I would consider release
> of an RC to be as worthy of mention in the quarterly report as any
> GA release.
Hmm, yes. I think I made the wrong decision there, carelessly assuming it was similar to our "doap" file[1] which doesn't need to mention pre-releases.
I'll revert this. r1855435. Thanks.
--
- Julian
Re: svn commit: r1855211 - /subversion/site/publish/docs/community-guide/releasing.part.html
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
julianfoad@apache.org wrote on Mon, 11 Mar 2019 11:35 +00:00:
> Author: julianfoad
> Date: Mon Mar 11 11:35:43 2019
> New Revision: 1855211
>
> URL: http://svn.apache.org/viewvc?rev=1855211&view=rev
> Log:
> * publish/docs/community-guide/releasing.part.html:
> Don't use reporter.apache.org for pre-releases.
For what it's worth:
reporter.a.o is AFAIK only used for drafting Board reports; I would
expect the Board to care equally much about any release regardless of
its alpha/beta/RC/GA status; therefore, I would consider release
of an RC to be as worthy of mention in the quarterly report as any
GA release.
Cheers,
Daniel
Re: svn commit: r1855211 - /subversion/site/publish/docs/community-guide/releasing.part.html
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
julianfoad@apache.org wrote on Mon, 11 Mar 2019 11:35 +00:00:
> Author: julianfoad
> Date: Mon Mar 11 11:35:43 2019
> New Revision: 1855211
>
> URL: http://svn.apache.org/viewvc?rev=1855211&view=rev
> Log:
> * publish/docs/community-guide/releasing.part.html:
> Don't use reporter.apache.org for pre-releases.
For what it's worth:
reporter.a.o is AFAIK only used for drafting Board reports; I would
expect the Board to care equally much about any release regardless of
its alpha/beta/RC/GA status; therefore, I would consider release
of an RC to be as worthy of mention in the quarterly report as any
GA release.
Cheers,
Daniel