18 ms·

We've talked about this a lot internally. They make a big deal about releasing on the 22nd of every month, but they usually have to turn around and release a pa

We've talked about this a lot internally. They make a big deal about releasing on the 22nd of every month, but they usually have to turn around and release a patch shortly thereafter. 14.8 is a bit of an extreme: 14.8.0 on the 22nd, 14.8.1 (bug fix) on the 23rd, then 14.8.2 (security) on the 25th. We'd personally prefer to see a better release when it's done, vs. them keeping this farce of a 'release streak' going and then asking customers to install another upgrade within days.

0xbadcafebee 5y ago
Seems like you could just wait a few weeks until upgrading to a new release?
- kokey 5y ago
  When I used to maintain a GitLab server I used to do exactly this by upgrading almost a month behind their schedule.
  - passerby1 5y ago
    The problem with this approach is being vilnerable to major zero-days (like 30k servers hack in Nov 2021) every month.
lbotos 5y ago
I've proposed to other customers who want less releases to track one minor version behind for the experience you are looking for. Still within security fix range, up-to-date and you will jump the the latest patch release (and none should follow unless it's a security release).
blyry 5y ago
I always ran 1 ( sometimes 2) point releases behind, never ever had an issue upgrading. Omnibus on Ubuntu.