You must tag releases in the format of "1.x-a.b.c" for the Backdrop packaging script to work. You will see right away if there was an error during the packaging process, as a notice will appear on the release page.
Creating Security Releases
You will need to work with the Backdrop Security Team in order to make a security release for your project. Please contact firstname.lastname@example.org to begin this process.
You and the security team will choose a Wednesday to coordinate the release, and on that day, when you publish the release on GitHub, someone from the Backdrop Security Team will need to update the project release node on backdropcms.org to indicate that this particular release is a security release.
The Backdrop Security Team
The Backdrop Security Team is authorized to make limited commits to all projects.
The team consists only of trusted members of the backdrop-contrib group who have security experience.
This team will work together with Backdrop maintainers to resolve potential security issues. In the event that a maintainer can't be reached, or if an issue is deemed sufficiently critical, the security team is authorized to commit directly to any project, and issue a new security release.
The Backdrop Bug Squad
The Backdrop Bug Squad is authorized to make limited commits to all projects. The team consists only of trusted members of the backdrop-contrib group.
This team is intended to help contributors stay on top of minor bug fixes and User Interface improvements by merging issues that have been "Reviewed and tested by the community" for a period of at least two weeks.
Archiving your project
In the rare case that your project needs to be archived, please update the README.md file to explain why it is no longer useful.
A great example of this is the AYAH project, which was archived because the AYAH service was discontinued.