How Should Releases Be Announced?
It is important that people are informed about the availability of new releases. At the very least, emails should be sent out announcing this to all appropriate mailing lists. Many top level projects have announcement lists for this purpose. There is also an ASF-wide announcement list which is suitable. Please note that you can not post the ASF-wide announcement list without the usage of “apache.org” mail address. Also, please make sure that you have put 3-5 lines blurb for the project. (because most of the subscribers to announce.AT.apache.DOT.org list would not know what is XX-Project, generally speaking) It is recommended that an SHA-1 OpenPGP compatible signature is added to the announcement mail. Please ensure that your public key has been already uploaded to famous pgp sites (e.g. http://pgp.mit.edu/). This key should either be the one used to sign the release or one that is cross-signed by that key.
Related Questions
- If I’ve been installing and using the JAWS public beta releases, should I remove the public beta before installing the official JAWS 9.0 release?
- If a ship approaching the dock suffers a mechanical malfunction and releases fuel to the environment, what is the contingency plan?
- Has the support for older releases of Java on the Solaris platform changed since Java for Business was announced?
