Try shorter release cycles

Posted May 26, 2015 1:20 UTC (Tue) by ringerc (subscriber, #3071)
In reply to: Try shorter release cycles by roguelazer
Parent article: PostgreSQL: the good, the bad, and the ugly

The problem is that adding "QA time" in the sense of longer freezes doesn't help if nobody pays attention.

What we need is more people putting more time into actually reviewing and testing the changes. Presently everyone's focused on their projects and getting their patches in, and not many people have much time at all dedicated to testing and QA.

If we can increase the time slice given to QA and testing then we won't _need_ longer freezes. If we can't, then they won't do any good.

Try shorter release cycles

Posted Aug 7, 2015 8:17 UTC (Fri) by jospoortvliet (guest, #33164) [Link]

That is actually where shorter release cycles with occasional LTS releases helps. For some users, the shorter cycle releases are great as they have need for the features and/or don't put such crucial data in the db (or are fine with rolling back a backup). They will report bugs and help ensure your LTS releases are stable. And no, they would not try beta and alpha releases - different thing, really.