Anthony Towns wrote: > For those who're interested: we'll see about handling 2.2r2 in a more > transparent manner. I'll try to keep auric:~ajt/which-updates as an up > to date list of which will get accepted and why others will get rejected, > and have it posted automatically to -release once a week. Comments etc > should go to -release.
It might be nice if, once we get package pools, we can break off a pre-r2 branch that just gets the updates put in it as you clear them. Then it could even be tested a bit and it would be quite obvious what was going in. -- see shy jo
