Cudos to Nathan for authoring, I just did the easy job reviewing and
merging to publish...
/Daniel
Den ons 16 aug. 2023 kl 08:07 skrev :
> Author: dsahlberg
> Date: Wed Aug 16 06:07:27 2023
> New Revision: 1911713
>
> URL: http://svn.apache.org/viewvc?rev=1911713&view=rev
> Log:
> In site/publish:
>
> Merge 1911705-1911709 from site/staging
>
> * docs/community-guide/releasing.part.html
> (#releasing, #release-compat, #release-stabilization-how-to-edit): Fix
> typos
>
> Modified:
> subversion/site/publish/ (props changed)
> subversion/site/publish/docs/community-guide/releasing.part.html
>
> Propchange: subversion/site/publish/
>
> --
> Merged /subversion/site/staging:r1911705-1911709
>
> 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=1911713&r1=1911712&r2=1911713&view=diff
>
> ==
> --- subversion/site/publish/docs/community-guide/releasing.part.html
> (original)
> +++ subversion/site/publish/docs/community-guide/releasing.part.html Wed
> Aug 16 06:07:27 2023
> @@ -14,7 +14,7 @@ order of specificity:
> created?" and "What should be the content of a tarball?"
> What steps to take when it is time to create a release. This section
> addresses the question of "How do I manage a release?"
> -How to constructing a set of release tarballs. This section discusses
> +How to construct a set of release tarballs. This section discusses
> the steps required to go from source code in the repository to a set
> of
> distributable .tar.gz or .zip files with the
> desired content.
> @@ -228,7 +228,7 @@ client/server interoperability, and make
> path between MAJOR.MINOR Subversion releases.
>
> Compatibility can span a number of axes: everything from APIs and ABIs
> to
> -command line output formats. We try to balance to need to modify the
> existing
> +command line output formats. We try to balance the need to modify the
> existing
> architecture to support new features, while still supporting current users
> to the greatest extent possible. The general idea is:
>
> @@ -251,7 +251,7 @@ to the greatest extent possible. The ge
>
> (Occasionally, bugs are found which require the behavior of old
> APIs
> to be modified slightly. This typically only manifests itself in
> - various corner cases and other uncommon area. These changes are
> + various corner cases and other uncommon areas. These changes are
> documented as https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/";>API
> errata for each MAJOR.MINOR release.)
>
>
> @@ -756,8 +756,8 @@ voting, are always kept on the main rele
> title="Link to this section">¶
>
>
> -When adding revisions to a nominations that others have already voted
> on,
> -annotated their entries with "(rX only)" to clarify what parts they have
> and
> +When adding revisions to a nomination that others have already voted
> on,
> +annotate their entries with "(rX only)" to clarify what parts they have
> and
> haven't voted on, like this:
>
>
>
>
>
