Page History

...

Extends 72 to a bit more ? (OpenOffice is one week)

 [] I have tested the binary RC on platform [ ] taken from Openoffice to get some quality check on binaries.

---

Release policy web page not clear on how to manage the conveniences artefacts of a release.

...

Before casting +1 binding votes, individuals are REQUIRED to download all signed source code packages onto their own hardware, verify that they meet all requirements of ASF policy on releases as described below, validate all cryptographic signatures, compile as provided, and test the result on their own platform.

....

Artifacts

Compiled packages²

The Apache Software Foundation produces open source software. All releases are in the form of the source materials needed to make changes to the software being released.

...

The repository directory https://dist.apache.org/repos/dist/release/<TLP name>/ is for official releases only, i.e. archives¹ (+ sigs, hashes) that have been approved by the PMC. For this reason, by default only PMC members can update the dist/release directory tree.

-------------------

1: the word archives should be artefacts ( Source packages, Compiled packages) to match with what is before in the document

2: is compiled package an equivalent to conveniences binaries (would add it in the title)

Difficulty I encounter understanding the workflow on approval

the release vote call is not described enough to me. If RM is showing the dist/dev/<TLP name>/V1 as voting resources nothing prevent additionnal binaries sources to be put during the vote.

the release approval is not clear what to do with compiled package, PMC member may not have access to requiered platform. What to do if we want some quality