On Tue, Feb 23, 2016 at 10:14:11PM +0800, Qiming Teng wrote: :My take of this is that we are saving the cost by isolating developers :(contributors) from users/customers.
I'm a little concerned about this as well. Though presumably at least the PTLs would still attend the User/Ops conference even if their project didn't co-schedule a midcycle and while there could be more focused on that user feed back rather than splitting their attention with implementation detais and other design summit type issues. I'm not entierly settled in my opinion yet, but right now the proposed changes seem like a good direction to me. Moving the design summit seems popular with the dev community here. Moving the User/Ops session further after release also seems like a good plan as there will be some people there with real production experiance with the new release. In Tokyo we had an Operators session on upgrade issues with Liberty that was very well attended but exactly zero attendees had actually run the upgrade in production. So later in the cycle is definitely better for getting feed back on the last realeas, but is there a good plan for how that feed back will feed into the next release (or maybe at that point it will be next+1)? -Jon __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
