Hi GNOME maintainers,
Please remember that if your software is in GNOME core, GNOME SDK, or is a dependency of either: following the unstable release schedule for .alpha, .beta, .rc, and .0 releases is MANDATORY unless your project has no noteworthy changes. (For stable releases other than .0, please ignore the schedule and release whenever you feel a release is needed.)
If you are unable to release according to the unstable schedule, please contact the release team for help BEFORE the tarball deadline. Alternatively, if you no longer have time to handle unstable releases, then please consider removing yourself from the doap so we know that your project is not maintained and not to bother you about it.
Each unstable release, we spend several days dealing with build failures caused by missing releases. If you don’t release according to the schedule and your software fails to build or is responsible for other software failing to build, you will be contacted by release team asking you to IMMEDIATELY release, and we may release your module for you if you don’t respond IMMEDIATELY. This is zero fun for us or for you, and I have lost track of how many times it’s happened so far this week: three time so far just today, several more yesterday, several more the day before. We cannot wait even a short while for your module to release because we have hundreds of tarballs to build and will take ages to successfully release if we wait even a short while for late tarballs.
You can avoid almost all of these problems by simply releasing your tarball according to the schedule. Build failures are almost always already fixed in git and are just awaiting a release. See also: Emmanuele’s proposal to release everything automatically.