Re: svn commit: r1886494 - /subversion/site/staging/docs/community-guide/releasing.part.html

[Daniel Sahlberg]

Den tis 16 feb. 2021 kl 16:20 skrev Daniel Sahlberg <
daniel.l.sahlb...@gmail.com>:

> Den tis 16 feb. 2021 kl 12:44 skrev Daniel Sahlberg
> :
> >> P.S.  While reviewing this I noticed that
> >> https://subversion-staging.apache.org/favicon.ico is different to
> >> https://svn.apache.org/repos/asf/subversion/site/staging/favicon.ico:
> an Apache
> >> feather v. a Subversion logo.
> >
> >
> > Hmm. That is very strange. I've pinged infra on Slack.
>
> Infra says:
> > looks like it's an overall override for "generic sites" that they all
> have the ASF favicon due to the dash in subversion-staging it gets
> overridden
>
> Ie, it is not a fault in our repository but an httpd.conf thing for the
> site.
>
> I asked to have this removed and was requested to add it to Jira:
> https://issues.apache.org/jira/browse/INFRA-21429


It took just short of two months but Infra has changed the override and the
staging site is showing the correct favicon, ie the one in the repository.

Kind regards
Daniel

Re: svn commit: r1886494 - /subversion/site/staging/docs/community-guide/releasing.part.html

[Daniel Sahlberg]

Den tis 16 feb. 2021 kl 12:44 skrev Daniel Sahlberg
:
>> P.S.  While reviewing this I noticed that
>> https://subversion-staging.apache.org/favicon.ico is different to
>> https://svn.apache.org/repos/asf/subversion/site/staging/favicon.ico: an 
>> Apache
>> feather v. a Subversion logo.
>
>
> Hmm. That is very strange. I've pinged infra on Slack.

Infra says:
> looks like it's an overall override for "generic sites" that they all have 
> the ASF favicon due to the dash in subversion-staging it gets overridden

Ie, it is not a fault in our repository but an httpd.conf thing for the site.

I asked to have this removed and was requested to add it to Jira:
https://issues.apache.org/jira/browse/INFRA-21429

Kind regards,
Daniel Sahlberg

Re: svn commit: r1886494 - /subversion/site/staging/docs/community-guide/releasing.part.html

[Daniel Sahlberg]

Thanks for your review!

Den mån 15 feb. 2021 kl 21:07 skrev Daniel Shahaf :

> dsahlb...@apache.org wrote on Sat, Feb 13, 2021 at 21:41:10 -:
> > +++ subversion/site/staging/docs/community-guide/releasing.part.html Sat
> Feb 13 21:41:10 2021
> > @@ -1255,80 +1255,24 @@ href="https://reporter.apache.org/addrel
> >
> >   
> >
> > -
>
> Here, you moved some 70 lines and also made a change between the pre-move
> and
> post-move form.  First, here's the delta for ease of review:
>

Sorry, should have done it in two commits.


> [[[
> -NOTE: We announce the release before updating the website since the
> website
> -update links to the release announcement sent to the announce@ mailing
> list.
> +NOTE: We update the website before announce the release to make sure
> any
> +links in the release announcement are valid. After announcing the release,
> +links to the release announcement e-mail are added to the website.
> ]]]
>
> On the first added line, "before announce the release" is ungrammatical.
>

Fixed (I hope..), r1886586.

(Also, with some archives it's possible to generate the links in advance;
> for
> example, this message's permalink is
> <
> https://mail-archives.apache.org/mod_mbox/subversion-dev/202102.mbox/%3C9761a2ec-aab5-409d-ba23-4f519c76a03c@tarpaulin.shahaf.local2%3E
> >.)
>
> >  
> >  Update the website
> > -->#releasing-update-website"
> >  title="Link to this section">¶
> >  
> >
> > +Even though the steps below indicate to update the published website
> > +directly, you may prepare the changes on
> ^/subversion/site/staging.
> > +In that case:
> > +
> > +  Do a catch-up merge from
> ^/subversion/site/publish.
> > +  Commit any changes to ^/subversion/site/staging and
> > +check the results on https://subversion-staging.apache.org
> "
> > +>https://subversion-staging.apache.org.
> > +  When ready to publish, merge the changes back to
> > +^/subversion/site/publish.
>
> Suggest to remind here to review the merge results in case there are other
> changes on staging at the time «svn merge» is run.
>

Added, r1886586.


>
> > +
>
> > @@ -1344,9 +1288,9 @@ the oldest supported LTS branch's ST
> >  ^/subversion/site/publish/index.html, also removing the
> >  oldest News item from that page.  Use release.py
> write-news to
> >  generate a template news item, which should then be customized.
> > -At least fill in the URL to the archived announcement email, and
> check
> > -that the date is correct if you generated the template in advance
> of the
> > -release date.
> > +For now, comment out the link to the release announcement e-mail.
> > +Check that the date is correct if you generated the template in
> advance of
> > +the release date.
>
> Sounds like we should make write-news generate the HTML comment marker in
> advance, and only ask the RM to remove them.  (The RM has a fair amount of
> work
> as it is; every little bit helps.)
>

Very reasonable, patch below. I'm adding the comment unless there is an
announcement url in command line arguments. I'm not happy about the
[if-any][else] construct but I couldn't find a way to check "if not any",
from a quick glance at the documentation in gsteins gihub repo. I took the
liberty of updating releasing.part.html as if the change below (or similar)
will go through.

[[[
Index: tools/dist/templates/rc-news.ezt
===
--- tools/dist/templates/rc-news.ezt(revision 1886582)
+++ tools/dist/templates/rc-news.ezt(working copy)
@@ -8,8 +8,18 @@
release is not intended for production use, but is provided as a
milestone
to encourage wider testing and feedback from intrepid users and
maintainers.
Please see the
+[if-any announcement_url]
+[else]
+
+[end]
release notes and
https://svn.apache.org/repos/asf/subversion/tags/[version]/CHANGES";>
change log for information about what will eventually be
Index: tools/dist/templates/stable-news.ezt
===
--- tools/dist/templates/stable-news.ezt(revision 1886582)
+++ tools/dist/templates/stable-news.ezt(working copy)
@@ -10,8 +10,18 @@
 [else]   This is the most complete release of the [major-minor].x line to
date,
and we encourage all users to upgrade as soon as reasonable.
 [end]   Please see the
+[if-any announcement_url]
+[else]
+
+[end]
release notes for more information about this release.
]]]


> Cheers,
>
> Daniel
>
> P.S.  While reviewing this I noticed that
> https://subversion-staging.apache.org/favicon.ico is different to
> https://svn.apache.org/repos/asf/subversion/site/staging/favicon.ico: an
> Apache
> feather v. a Subversion logo.
>

Hmm. That is very strange. I've pinged infra on Slack.

Kind regards,
Daniel Sahlberg

Re: svn commit: r1886494 - /subversion/site/staging/docs/community-guide/releasing.part.html

[Daniel Shahaf]

dsahlb...@apache.org wrote on Sat, Feb 13, 2021 at 21:41:10 -:
> +++ subversion/site/staging/docs/community-guide/releasing.part.html Sat Feb 
> 13 21:41:10 2021
> @@ -1255,80 +1255,24 @@ href="https://reporter.apache.org/addrel
>  
>   
>  
> -

Here, you moved some 70 lines and also made a change between the pre-move and
post-move form.  First, here's the delta for ease of review:

[[[
-NOTE: We announce the release before updating the website since the website
-update links to the release announcement sent to the announce@ mailing 
list.
+NOTE: We update the website before announce the release to make sure any
+links in the release announcement are valid. After announcing the release,
+links to the release announcement e-mail are added to the website.
]]]

On the first added line, "before announce the release" is ungrammatical.

(Also, with some archives it's possible to generate the links in advance; for
example, this message's permalink is
.)

>  
>  Update the website
> -->#releasing-update-website"
>  title="Link to this section">¶
>  
>  
> +Even though the steps below indicate to update the published website 
> +directly, you may prepare the changes on ^/subversion/site/staging.
> +In that case:
> +
> +  Do a catch-up merge from 
> ^/subversion/site/publish.
> +  Commit any changes to ^/subversion/site/staging and
> +check the results on https://subversion-staging.apache.org";
> +>https://subversion-staging.apache.org.
> +  When ready to publish, merge the changes back to 
> +^/subversion/site/publish.

Suggest to remind here to review the merge results in case there are other
changes on staging at the time «svn merge» is run.

> +

> @@ -1344,9 +1288,9 @@ the oldest supported LTS branch's ST
>  ^/subversion/site/publish/index.html, also removing the
>  oldest News item from that page.  Use release.py write-news to
>  generate a template news item, which should then be customized.
> -At least fill in the URL to the archived announcement email, and check
> -that the date is correct if you generated the template in advance of the
> -release date.
> +For now, comment out the link to the release announcement e-mail.
> +Check that the date is correct if you generated the template in advance 
> of 
> +the release date.

Sounds like we should make write-news generate the HTML comment marker in
advance, and only ask the RM to remove them.  (The RM has a fair amount of work
as it is; every little bit helps.)

Cheers,

Daniel

P.S.  While reviewing this I noticed that
https://subversion-staging.apache.org/favicon.ico is different to
https://svn.apache.org/repos/asf/subversion/site/staging/favicon.ico: an Apache
feather v. a Subversion logo.

svn commit: r1886494 - /subversion/site/staging/docs/community-guide/releasing.part.html

[dsahlberg]

Author: dsahlberg
Date: Sat Feb 13 21:41:10 2021
New Revision: 1886494

URL: http://svn.apache.org/viewvc?rev=1886494&view=rev
Log:
Because of a recent rejection on a release announcement e-mail.
Discussion on dev@: 
http://mail-archives.apache.org/mod_mbox/subversion-dev/202102.mbox/%3cyct00ucl31qzt...@byrne.stsp.name%3e

* staging/docs/community-guide/releasing.part.html:
  (release-update-website): Split the website update in two:
- Main update before the release announcement to make sure any links in
  the announcement are valid (reducing the risk or rejection).
- Add the links to the release announcement after the e-mail land in the
  archive.
Suggestion to use https://subversion-staging.a.o 
  (^/subversion/site/staging) to prepare the updates.
  (releasing-announce): Update the NOTE on website updating to reflect these
changes.

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=1886494&r1=1886493&r2=1886494&view=diff
==
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Sat Feb 13 
21:41:10 2021
@@ -1255,80 +1255,24 @@ href="https://reporter.apache.org/addrel
 
  
 
-
-Press releases for 1.x.0 releases
-  #releasing-press"
-title="Link to this section">¶
-
-
-New minor releases (numbered 1.x.0) may be accompanied by press releases.
-All details of the prospective press release are handled on the
-private@ list, in coordination with
-https://www.apache.org/press/";>press@a.o.
-
-As a rule of thumb, start a thread on private@ / press@
-at the start of the soak; it is better
-to give press@ too long an advance warning than too short one.
-
- 
-
-
-Announcing the release
-  #releasing-announce"
-title="Link to this section">¶
-
-
-Write a release announcement, referring to previous ones for
-guidance.  Remember to include the URL and checksums in the
-announcement!  The release.py write-announcement subcommand
-creates a template announcement which can be customized for specific
-circumstances.  If the release fixes security issues, pass
-the --security flag, in order to generate the correct Subject,
-Cc, and description in the output.
-
-If the community support levels are changing with this
-release, be sure to update the recommended_release variable in 
release.py
-before using it to generate the announcement.
-
-Send the announcement from your @apache.org email address.
-(Mail to announce@ will bounce if sent from any other address.
-For best results, follow the instructions on the
-https://infra.apache.org/committer-email.html";>committer email
-page and send your message through the official mail relay.)
-Ensure that your mailer doesn't wrap the URLs over multiple lines.
-
-NOTE: We announce the release before updating the website since the website
-update links to the release announcement sent to the announce@ mailing 
list.
-
-There are two announce@ mailing lists where the release announcement gets
-posted: The Subversion project's annou...@subversion.apache.org list, and the 
ASF-wide annou...@apache.org
-list. It is possible that your message to the ASF-wide announce@ list will be
-rejected. This generates a moderation notification with a Subject line such as:
-Returned post for annou...@apache.org. The moderator who ordered the
-mailing list software to reject the message may neglect to sign their name to
-the rejection message, making the rejection anonymous, and the grounds for the
-rejection may be invalid. Be that as it may, keep calm and forward the
-rejection to the dev@ mailing list so the project can discuss whether anything
-needs to be done about it. (If necessary, announce@ mailing list moderators can
-be contacted via the announce-owner@ handle.)
-
-Update the topics in various Subversion-related IRC channels, such as
-#svn and #svn-dev on freenode.
-
-If this is an X.Y.0 release, update the community support level at the very
-top of the STATUS files of any branches that have changed support
-status.  This would usually be X.Y.x/STATUS,
-X.$((Y-1)).x/STATUS, and if the new release is an LTS release, then
-the oldest supported LTS branch's STATUS file as well.
-
- 
-
 
 Update the website
   #releasing-update-website"
 title="Link to this section">¶
 
 
+Even though the steps below indicate to update the published website 
+directly, you may prepare the changes on ^/subversion/site/staging.
+In that case:
+
+  Do a catch-up merge from ^/subversion/site/publish.
+  Commit any changes to ^/subversion/site/staging and
+check the results on https://subversion-staging.apache.org";
+>https://subversion-staging.apache.org.
+  When ready to publish, merge the chang