This isn't desktop software, though. Databases are kind of special, like
filesystems: a huge variety of bugs in them can be data-loss bugs, and
when you lose data you can lose a *lot* at once.
As such, the priority must *always* be quality, specifically
lack-of-data-loss quality. It's no good if a DB is released sooner if it
eats your data once you install it. Prioritizing time-based schedules over
quality helps only the vendor, not the users.
(PostgreSQL gets this right: note their massive backports of any data loss
bug, often to five-year-obsolete releases, simply because users upgrade to
new major versions of databases extremely rarely, but still consider data
loss bugs crucial to fix.)