Jonathan Edwards wrote: > > On Jun 19, 2009, at 10:22 AM, MC wrote: > >>> Nah. Just the team that's actually doing the work. >> >> I don't understand the politics enough to understand that. All I >> means was: I thought I read that the plan had important updates going >> to the stable repository! >
Only critical security or stability fixes have a hope of ending up in the release repository, so far there are none scheduled as far as I know. Support subscriptions will get you access to other important fixes, or you can self-support and run off of /dev. > good point .. on top of that - why has the dev repository (last update > [minor] - 05/30) been lagging behind the release repository (last update > 06/03) for close to a month? .. and why is the contrib repository (last > update 05/09) even further behind the dev repository? > > methinks something's broken in the updating scheme of things .. i would > have at least anticipated the dev repository to track with the nv > releases - it's getting a little painful maintaining my own repos to > just try and take in the dev changes from the more recent nv releases, > and then having to go back and figure out what got consolidated where in > the released dev repo .. > The dev repo will be updated soon. We have only so many resources to apply, and stabilizing the release takes all of them. This will be improving in future releases as we distribute the work back upstream further. Changing over the factory on the fly is harder than you think. Dave
