Checkout Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
* publish/docs/community-guide/releasing.part.html

(backport-merge-bot): Correct the link-to-self.

* publish/docs/community-guide/releasing.part.html

(creating-branch): Tewak creating the release notes template.

* publish/docs/community-guide/releasing.part.html

(creating-branch): Add writing the release notes.

* docs/community-guide/releasing.part.html

(#backport-merge-bot): Link to the relevant bug.

* docs/community-guide/releasing.part.html

(#backport-merge-bot): Fix invalid markup.

* publish/docs/community-guide/releasing.part.html

(creating-branch): Move info on managing the backport merge bot...

(backport-merge-bot): ... to this new section, and expand and clarify it.

* publish/docs/community-guide/releasing.part.html

Adjust backport buildbot instructions, following recent changes related to

migration from svn-qavm3 to svn-qavm

( https://issues.apache.org/jira/browse/INFRA-18508 ).

* publish/docs/community-guide/releasing.part.html

Adjust release.py usage, following r1867623, and minor tweaks.

* publish/docs/community-guide/releasing.part.html

Adjust release.py --target option, following r1867630.

Use consistent version numbers in examples.

* publish/docs/community-guide/releasing.part.html

(#release-stabilization-how-many-votes): Clarify ambiguity.

Merge from staging: new consensus that non-LTS backports need only two +1 votes.
  1. … 4 more files in changeset.
* publish/docs/community-guide/releasing.part.html

(rolling-release): Update 'release.py' command-lines, removing unnecessary

'base-dir' and 'branch' options, the latter for compatibility with r1866944.

In 'Stabilizing and maintaining releases': merge clarifications from 'staging'.
  1. … 4 more files in changeset.
Remove a step for updating the 'upcoming changes' branch for a new minor release.

Reverts r1864042, as it is now done a different way:

https://issues.apache.org/jira/browse/SVN-4823 "site: upcoming.py script

should automatically show changes for the latest stable branch".

Document a step for updating the 'upcoming changes' branch for a new minor release.
* publish/docs/community-guide/releasing.part.html (tarball-signing):

Add sub-headings and format the requirements as a list, for clarity.

* publish/docs/community-guide/releasing.part.html: Revert mistaken r1855211.^M^MThanks to danielsh for pointing it out.
* publish/docs/community-guide/releasing.part.html:

Don't use reporter.apache.org for pre-releases.

Merge an outstanding change from staging tree to publish.

  1. … 1 more file in changeset.
Clarify the 'create a new release branch' docs.
* publish/docs/community-guide/releasing.part.html

(the-changes-file): Briefly mention 'release.py write-changelog'.

* publish/docs/community-guide/releasing.part.html

(releasing-update-website): Add a recipe for publishing API docs.

* docs/community-guide/releasing.part.html: Clarify a reference.
* docs/community-guide/releasing.part.html: Document r1841085.
* publish/docs/community-guide/releasing.part.html,

publish/docs/community-guide/releasing.toc.html

(release-branches): Organize some existing content into subsections.

  1. … 1 more file in changeset.
* publish/docs/community-guide/releasing.part.html

(notify-translators): Document how to produce a translation status report.

Remove obsolete references to SHA1.

* publish/docs/community-guide/releasing.part.html

Don't refer to 'SHA1 checksums', just say 'checksums', as the kind we use

has changed and may change again and isn't important here.

* publish/download.html

(verifying): Don't mention SHA1. Only mention one commonly available program

'sha512sum'. (GNU sha*sum programs are now part of 'coreutils'. Readers

able to make use of that information don't need to be told it here.)

  1. … 1 more file in changeset.
* publish/docs/community-guide/releasing.part.html

(rolling-release): Add a cross-reference.

* docs/community-guide/releasing.part.html

(#tarball-signing): Update following r1835195. Improve phrasing and apply

minor corrections.

Suggested by: danielsh

* docs/community-guide/releasing.part.html

(#tarball-signing): Update following r1835191. Correct the number of

required signatures per platform.