To be clear, this is purely for release and internal kitchen stuff. The point of this area was purely for management reasons which there should be no non-management input in.darkbasic wrote:Agree on the release videos, but I don't agree on changelogs and RC packages. This is a FOSS project, everyone has access to the git repo and everyone can pull rc tags. Testing should be encouraged: hiding discussions in private areas you are simply going to kill interest from outsiders. If they are not going to be interested they will never join the private areas and the project will slowly starve. Do it in public, raise interest, encourage testing, just strip the youtube links and avoid publishing packages on PPAs before you're ready. Also final version on git shouldn't be tagged until you're *really* ready to release. In the meantime branch it, tag RCs and test RCs: you can't blame a package maintainer for updating his package because he got an automatic notification that a new stable release has been tagged.
Conversation around the lead up to the release itself will always be public, so bug-fixes, testing and RC builds will be made available.
The point-in-time of release, the tag for example by Zini, can be set internally for a simultaneous release. That way the tag appears at the moment that there is a blog post with videos and downloads. We already have a branch from master for release strategy, so this is a non-issue.
You can't avoid publishing packages on a public PPA if you are trying to create packages and want them to work and be ready for the release. I'm waiting to hear back from Canonical about if a private PPA for staging is possible.