On 8/7/19, David Magda <dmagda(a)ee.ryerson.ca> wrote:
That is an argument for timed releases. The OpenBSD project is a good
example: they release twice a year. If a feature cannot be made stable in
time for one release, they either back it out or do not commit in the first
place, and simply try to make it work for the following one. There is
actually less pressure to force a feature (that may or may not be ready) in
a particular release, because the next one will be along shortly. When
releases are ad hoc, there is actually more pressure because people start
thinking “if we don’t get it in this release, who knows when the next
opportunity will be”.
It is also an argument for external funding, because the team involved
needs to be sponsored when release time comes. Who will then ensure
the type of sponsorship that does not dry up at a bad moment?