Basically, we need the "second deliverable" from https://fedoraproject.org/wiki/Fedora.next/boardproposal#Product_Working_Gro...
... a list of necessary changes from existing Fedora procedures needed to release the product. This should be ordered to show what things depend on other changes and at which point the changes will mean that we can no longer produce the current type of Fedora. This will allow us to identify the resources needed by what teams in order to implement the plan and at what point we may need to have a longer than normal release cycle to do tooling work.
Here's the item on the big cloud todo list: https://fedoraproject.org/wiki/Cloud/Cloud_ToDo#Fedora.next_changes_list
Follow that to the (not yet created) Cloud Changelist page. Sam (or anyone), if you want to throw up an etherpad for hacking on it, that'd be good.
On Thu, Feb 13, 2014 at 3:21 AM, Matthew Miller mattdm@fedoraproject.org wrote:
Basically, we need the "second deliverable" from https://fedoraproject.org/wiki/Fedora.next/boardproposal#Product_Working_Gro...
... a list of necessary changes from existing Fedora procedures needed to release the product. This should be ordered to show what things depend on other changes and at which point the changes will mean that we can no longer produce the current type of Fedora. This will allow us to identify the resources needed by what teams in order to implement the plan and at what point we may need to have a longer than normal release cycle to do tooling work.
Here's the item on the big cloud todo list: https://fedoraproject.org/wiki/Cloud/Cloud_ToDo#Fedora.next_changes_list
Follow that to the (not yet created) Cloud Changelist page. Sam (or anyone), if you want to throw up an etherpad for hacking on it, that'd be good.
I went ahead and put up some ideas, brainstorming with looking heavily at the Cloud ToDo and Cloud PRD pages: https://fedoraproject.org/wiki/Cloud_Changelist
Hope that helps getting started here, and hopefully in the right direction, too.
-- Sandro
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 14 Feb 2014 16:31:19 +0900 "Sandro "red" Mathys" red@fedoraproject.org wrote:
On Thu, Feb 13, 2014 at 3:21 AM, Matthew Miller mattdm@fedoraproject.org wrote:
Basically, we need the "second deliverable" from https://fedoraproject.org/wiki/Fedora.next/boardproposal#Product_Working_Gro...
... a list of necessary changes from existing Fedora procedures needed to release the product. This should be ordered to show what things depend on other changes and at which point the changes will mean that we can no longer produce the current type of Fedora. This will allow us to identify the resources needed by what teams in order to implement the plan and at what point we may need to have a longer than normal release cycle to do tooling work.
Here's the item on the big cloud todo list: https://fedoraproject.org/wiki/Cloud/Cloud_ToDo#Fedora.next_changes_list
Follow that to the (not yet created) Cloud Changelist page. Sam (or anyone), if you want to throw up an etherpad for hacking on it, that'd be good.
I went ahead and put up some ideas, brainstorming with looking heavily at the Cloud ToDo and Cloud PRD pages: https://fedoraproject.org/wiki/Cloud_Changelist
Automate rel-eng
produce scratch builds on change (or at least nightly builds?)
we have had nightly images as part of the night rawhide and branched compose for months, you need to grab them from koji and upload them somewhere but its already done
Dennis
On Fri, Feb 14, 2014 at 5:48 PM, Dennis Gilmore dennis@ausil.us wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 14 Feb 2014 16:31:19 +0900 "Sandro "red" Mathys" red@fedoraproject.org wrote:
On Thu, Feb 13, 2014 at 3:21 AM, Matthew Miller mattdm@fedoraproject.org wrote:
Basically, we need the "second deliverable" from https://fedoraproject.org/wiki/Fedora.next/boardproposal#Product_Working_Gro...
... a list of necessary changes from existing Fedora procedures needed to release the product. This should be ordered to show what things depend on other changes and at which point the changes will mean that we can no longer produce the current type of Fedora. This will allow us to identify the resources needed by what teams in order to implement the plan and at what point we may need to have a longer than normal release cycle to do tooling work.
Here's the item on the big cloud todo list: https://fedoraproject.org/wiki/Cloud/Cloud_ToDo#Fedora.next_changes_list
Follow that to the (not yet created) Cloud Changelist page. Sam (or anyone), if you want to throw up an etherpad for hacking on it, that'd be good.
I went ahead and put up some ideas, brainstorming with looking heavily at the Cloud ToDo and Cloud PRD pages: https://fedoraproject.org/wiki/Cloud_Changelist
Automate rel-eng
produce scratch builds on change (or at least nightly builds?)we have had nightly images as part of the night rawhide and branched compose for months, you need to grab them from koji and upload them somewhere but its already done
Right, I remember. Now. :) Thanks for the clarification, updated the wiki page accordingly. The original (or main) point was 'builds on changes', so that's still valid. -- Sandro
Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJS/dhyAAoJEH7ltONmPFDRfsoP/AiL3octIe1+uGEEBZmj1Dnv fHqf5gdyIy+CvLsA9FXVXhL1+S7pt3CaxLkwSCnE/YwTERTtNjXI5ZdsjMJJB6c+ iJJw761d/yFqzsj2QjIL3jszIam8p9VaqxLWYOFu5X5pBqkmwssgOSbicKfoIO+n pkccqtV1VH4Dh6omLStWppF4hotX/4hKY52+cAS2RctK7aPF/brue+7zXkOzi6Kv FtnSLMnrTbOF33TfVCrRlp+12oUwHpQZOOSuciy0yJbKoIF0P/+kyG3KlFmSzg+3 nCloIGNQwueFE5X2QD05uJCD6FoO/TVuV4jgUqN0Zae+ZQzhd7r/vIv88L8mDrme sgbKS5MaHQ4C569v1X4txXGFu8g9W3ptIm5mUk0CBDRTR2DEBkhAZsTRRAO2T1d2 PWlAdlYFq38zhMIZP4/GFC+QBVHMhv/nyvp8wsOhVyXincvfh823FoHAWwAEWm16 DIvIaaN5DJFxw53E8hNF9jv5XvsKYVA6ksliJAUE7blszPOqkAw4ThkXNnYWcWs/ cv2CGxmQZd8XhYmCKxnsUZQnYpLCfEBoZVeSIaRTug3UbNf8TZLuAAfoSMN8oOjx BX8TNT4FNgXpURQqlGbKac/IstEP9rrCvc+SPGYCQYEddAtZVoSGgnl/kP5SOloQ klwetSRA2weBPUyWQYEE =Rt/H -----END PGP SIGNATURE----- _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
cloud@lists.stg.fedoraproject.org
-
Dennis Gilmore -
Matthew Miller -
Sandro "red" Mathys