Hi,
Some of this was discussed several years ago, and we had the board approve some
guidelines that can be found here:
https://incubator.apache.org/guides/distribution.html
Note that covers RC for PyPi and other platforms. Projects are not prohibited
from publishing RCs, they just need to take
@Jarek:
> but how PMCS turn that into practice - should be up to them.
Of course. As stated in the the first mail, I'd "establish a consensus
to explicitly allow making release candidates publicly accessible
during the voting period."
It's to "allow" or hint PMCs that they can do so, because, as
Is this an opt-in or opt-out policy? We wouldn't want to do that for CVE
fixed right?
Gaty
On Thu, Jan 9, 2025, 07:07 Jarek Potiuk wrote:
> Sorry " should be *not *to encourage the projects to make it easy for
> anyone to install and test the release" -> "should be to encourage the
> projects
Sorry " should be *not *to encourage the projects to make it easy for
anyone to install and test the release" -> "should be to encourage the
projects to make it easy for anyone to install and test the release"
On Thu, Jan 9, 2025 at 1:06 PM Jarek Potiuk wrote:
> Just a small thing to add - whil
Just a small thing to add - while we are releasing RCs, I think the right
approach should be not to encourage the projects to make it easy for anyone
to install and test the release - which does not automatically mean to
publish RC in the same way the final candidate is published.
The key here is t
On Thu, 9 Jan 2025 at 11:09, Piotr P. Karwasz wrote:
> First of all, I share your intention of having the largest number of
> users test our Release Candidates before the official release. If other
> projects were able to test our candidates **before** the end of the
> voting period:
In NetBeans
Hi tison,
On 9.01.2025 11:22, tison wrote:
I'd like to establish a consensus to explicitly allow making release
candidates publicly accessible during the voting period.
This should be an existing exercise that the source code of release
candidates is available on dist.apache.org, e.g., [1].
[1
Hi,
On Thu, Jan 9, 2025 at 11:25 AM tison wrote:
> ...I'd like to establish a consensus to explicitly allow making release
> candidates publicly accessible during the voting period...
Aren't most or all ASF release candidates publicly accessible already?
As in "you can get it if you know the UR
Hi,
I'd like to establish a consensus to explicitly allow making release
candidates publicly accessible during the voting period.
This should be an existing exercise that the source code of release
candidates is available on dist.apache.org, e.g., [1].
[1] https://dist.apache.org/repos/dist/dev/
