Deliverables and release engineering changes for Fedora.Next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!
As it seems, Fedora.Next and product planning leads also to changes
how Fedora is produced and how it's going to be distributed to our
users.

For this, we need to collect product deliverables, so needed changes
for release engineering can be planned (and implemented) and as I was
talking to Dennis, we're are currently blocked on it. 

I created rel-eng ticket - WGs, please, try to sum up required changes 
there (in consumable way), so we have it in one place (for possible
overlaps in requirements etc).

https://fedorahosted.org/rel-eng/ticket/5891

Currently, Alpha Change Deadline is planned for no earlier than
2014-07-22, it's not as far as it sounds, especially if changes
in releng are needed. So let's try to work this out as soon as
possible. 

I suppose, in the end, FESCo should approve requested changes in 
product deliverables. So once requirements are collected, I'll
create (yet another) ticket for FESCo. Or even better - as Cloud
did - Change proposal would be the best solution, even after the
submission deadline.

(Sorry for cross-posting;-).

Thanks
Jaroslav 
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Big List of Linux Books]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux