Tobias Nygren <tnn%NetBSD.org@localhost> writes: >> Another thought is whether it's better to jump 2 versions less often, or >> 1 every year. Updating of course is work for each user with the >> dump/restore. But probably the real work and unknown is fixing up sql >> for tightened error checking. > > I'd say less often is better. Bumping means recursive bumps, repo and > dependency churn. BUT if we're going to go for 9.5 at some point, I'd > prefer sooner rather than later. When we bump, we should go to the > version that has the most remaining life left. > > We are half way through the official 9.3 life cycle, so there's no > immediate rush to update. OTOH updating every other year seems more > than reasonable to me, and it's about that time now. All in all, it sounds like a good plan is moving to 9.5 just after the branch (so on stable it changes on July 1 when 2016Q2 is cut). In general I like to have any big changes, no matter how innocent they seem, early in a cycle, and we're only 7 days from expected freeze time now.
Attachment:
signature.asc
Description: PGP signature