All I'm saying is I'm going to be upset if HAMMER2 as the defaults is in 4.x instead of being a new major release.
On Fri, Nov 7, 2014 at 1:47 PM, John Marino <dragonfly...@marino.st> wrote: > On 11/7/2014 22:34, Matthew Dillon wrote: > > The ABI for package purposes can be a little confusing during release > > time. The release is 4.0 but the current 'master' (now 'after' the > > release) is 4.1. For ABI purposes we round up to the nearest even > > number so the current 4.1 master will look for '4.2' packages. 6 months > > from now the current master will, in fact, become 4.2. It's easier to > > manage the binary repo and the mirrors and allows us to do continuous > > package builds without having to juggle too many different names. Each > > binary package set is ~60GB or so. > > > > Maybe I over-engineered it :-) > > This is a blue moon issue. > We were expecting the release to be 3.10, not 4.0. The 3.10 packages > had been in places for 5 months. The transition from 3.9 to 3.10 would > have been seamless. Even when we switched to 4.0, the 3.10 packages > were only a couple of days old. But with the change to 4.0, we didn't > have any packages, and the RC was released before we had an opportunity > to build them. > > So it's only a problem at 4.0, 5.0. 6.0, and it's an avoidable problem > on our side. > > John > > > -- Sincerely, Zachary Crownover