On Tue, 2015-06-02 at 09:55 +0700, Truong Anh Tuan wrote: > ----- Original Message ----- > > From: "Stephen Gallagher" <sgallagh@xxxxxxxxxx> > > To: "Server SIG" <server@xxxxxxxxxxxxxxxxxxxxxxx>, > > desktop@xxxxxxxxxxxxxxxxxxxxxxx, > > devel-announce@xxxxxxxxxxxxxxxxxxxxxxx, > > cloud@xxxxxxxxxxxxxxxxxxxxxxx > > Sent: Tuesday, June 2, 2015 2:03:44 AM > > Subject: Fedora.next PRD refresh > > <snipped> > > > == Future PRD Refreshes == > > Starting at Flock 2016 (yes, *next* calendar year), each working > > group > > will have a workshop scheduled at Flock to go over its PRD and plan > > for > > the following year. Note: because Flock generally falls between > > Alpha > > and Beta of a Fedora release, all PRD planning is presumed to be a > > directive for Fedora N+1 and N+2 at that time, not retroactively > > applied to the current release. > > > > The workshops are expected to cover the majority of the update, and > > then they will be brought back to the respective mailing lists for > > further review before being due to the Council one month after > > Flock > > concludes. > > +1. This is a good idea and it is important to push products toward > on > the right way. > I am just curious why it would not be held from this year? because of > time constrains? > We had already communicated to several groups that we wanted to refresh it before Alpha this cycle (Cloud in particular had moved far from its original PRD). We decided to keep that plan and adjust the future.
Attachment:
signature.asc
Description: This is a digitally signed message part
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
