On Tue, Jun 24, 2014 at 7:07 AM, Russell Bryant <rbry...@redhat.com> wrote:
> On 06/24/2014 07:35 AM, Michael Still wrote: > > Phil -- I really want people to focus their efforts on fixing bugs in > > that period was the main thing. The theory was if we encouraged people > > to work on specs for the next release, then they'd be distracted from > > fixing the bugs we need fixed in J. > > > > Cheers, > > Michael > > > > On Tue, Jun 24, 2014 at 9:08 PM, Day, Phil <philip....@hp.com> wrote: > >> Hi Michael, > >> > >> Not sure I understand the need for a gap between "Juno Spec approval > freeze" (Jul 10th) and "K opens for spec proposals" (Sep 4th). I can > understand that K specs won't get approved in that period, and may not get > much feedback from the cores - but I don't see the harm in letting specs be > submitted to the K directory for early review / feedback during that period > ? > > I agree with both of you. Priorities need to be finishing up J, but I > don't see any reason not to let people post K specs whenever. > Expectations just need to be set appropriately that it may be a while > before they get reviewed/approved. > No, we need more discipline around bug fixing and also to reserve time for docs. Anne > > -- > Russell Bryant > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
