On 21/01/2014, Curtis Hovey-Canonical <[email protected]> wrote: > > I believe milestone 1.17.1 has about 4 weeks of issues targeted to it. > https://launchpad.net/juju-core/+milestone/1.17.1
I have retargetted all bugs that are not actually landed or about to land on trunk against the new 1.18.0 milestone. This should mean we can get a 1.17.1 release done, as desired. In general, I think we should target bugs against the next stable release milestone for planning, and only move them to the upcoming development release milestone when there's actually a prospect of something landing. Others may have a different opinion on this. For now, if you land something in time for 1.17.1 please bump the related bug back to that milestone. > I doubt we can release a 1.18.0 this month without cutting scope. That > may not be possible as API-everywhere really must be complete to > release 1.18.0. Playing with milestones hasn't changed the fact we have a lot of work targeted at 1.18, unfortunately not much jumped out at me as deferrable. Martin -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
