----- Original Message ----- > On Tue, Feb 25, 2014 at 3:02 PM, Jaroslav Reznik <jreznik@xxxxxxxxxx> wrote: > > >> We do not have a formal process in place for organizing such planning > >> efforts, but as a provisional one, we'd like to take the following steps: > > > > We do have a formal process in place - Change process. I'm going to > > announce it right now and as Fedora.next planning is a bit different to > > previous one, I'd like to ask even non engineering teams to be involved > > in Change process to help us scope the upcoming release and effort > > needed to accomplish planned Changes. > > > > There is a chicken-egg problem here. Without knowing the schedule one > cannot tell you which change might end up being done or not as > upstream schedules do not match ours. > We should put out a schedule to get things going. Staying in this > "hand weavy" state forever isn't helpful. It's not going to be forever and that's the reason we are trying to get these questions answered asap. And we have guidance in that no earlier than August and you WGs can propose other days to match theirs deadlines. And yes, it's chicken egg. Let's start with eggs :). Jaroslav > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
