From Fedora Project Wiki
(Created page with "Ongoing pad to track prioritization for Atomic product upstream. Monthly meetings held with stakeholders. Fedora priorities: https://fedoraproject.org/wiki/ReleaseEngineering...")
 
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 4: Line 4:


Invitees: Colin Walters, Mike McGrath, Jack Rieden
Invitees: Colin Walters, Mike McGrath, Jack Rieden
'''02DEC15'''
* Need to talk to MTrmc about involving Fedora in Notary conversations
* Should we move to 2 week ostree updates in the future (for atomic redesign) and possibly sooner?
** Colin will initiate a thread about this
* Need to make sure that Atomic and Docker workflows going forward reflect QA automation (including tools selection) for the release process and ideally for the development process
'''11NOV15'''
* QE coverage for Atomic - how do we get to a good state for release automation
** Make it as easy as possible for autocloud to accept tests
** Taskotron or Jenkins would allow us to do cluster testing
** Talk to Dan or Lokesh about testing docker in Atomic
* New priority: Cluster testing (Amanda will discuss with Tim for Taskotron)
** internal teams have lots of tests for this written for Jenkins
* Colin will give feedback to Adam on the contributing upstream doc
* How do we make it easier to make changes to Anaconda for Atomic?




'''07OCT15'''
'''07OCT15'''


* First meeting
* First meeting
* Decide who the right stakeholders are going forward to meet 1x / month
* Decide who the right stakeholders are going forward to meet 1x / month
* My role in Fedora & engagement with you going forward
* My role in Fedora & engagement with you going forward
* Draft priority list in progress (will be published to the Fedora Wiki when it's been groomed a bit more by the team)
* Draft priority list in progress (will be published to the Fedora Wiki when it's been groomed a bit more by the team)
  * 3 buckets of Atomic related work now, many of which we discussed with Colin and Mike at the end of October - http://etherpad.corp.redhat.com/FedoraAtomicNext
** 3 buckets of Atomic related work now, many of which we discussed with Colin and Mike at the end of October - http://etherpad.corp.redhat.com/FedoraAtomicNext
  * F23 - 2 week atomic enabled - http://209.132.184.50/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic
** F23 - 2 week atomic enabled - http://209.132.184.50/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic
  * ASAP - Atomic process improvements - http://209.132.184.50/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic_improvements
** ASAP - Atomic process improvements - http://209.132.184.50/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic_improvements
  * F25 - Atomic redesign - http://209.132.184.50/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic_redesign
** F25 - Atomic redesign - http://209.132.184.50/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic_redesign
    * There are a lot of dependencies here, hence alignment to F25 rather than F24
*** There are a lot of dependencies here, hence alignment to F25 rather than F24
  * What additional priorities are we missing from the list?
** What additional priorities are we missing from the list?
* RHEL Atomic Host upstream (?)
* RHEL Atomic Host upstream (?)
* Other
* Other
  * Potential resources from Jack to target Atomic work upstream
** Potential resources from Jack to target Atomic work upstream
  * Colin's feedback
** Colin's feedback
    * Continuous release / integration
*** Continuous release / integration

Latest revision as of 21:55, 2 December 2015

Ongoing pad to track prioritization for Atomic product upstream. Monthly meetings held with stakeholders.

Fedora priorities: https://fedoraproject.org/wiki/ReleaseEngineering/PriorityPipeline

Invitees: Colin Walters, Mike McGrath, Jack Rieden


02DEC15

  • Need to talk to MTrmc about involving Fedora in Notary conversations
  • Should we move to 2 week ostree updates in the future (for atomic redesign) and possibly sooner?
    • Colin will initiate a thread about this
  • Need to make sure that Atomic and Docker workflows going forward reflect QA automation (including tools selection) for the release process and ideally for the development process


11NOV15

  • QE coverage for Atomic - how do we get to a good state for release automation
    • Make it as easy as possible for autocloud to accept tests
    • Taskotron or Jenkins would allow us to do cluster testing
    • Talk to Dan or Lokesh about testing docker in Atomic
  • New priority: Cluster testing (Amanda will discuss with Tim for Taskotron)
    • internal teams have lots of tests for this written for Jenkins
  • Colin will give feedback to Adam on the contributing upstream doc
  • How do we make it easier to make changes to Anaconda for Atomic?


07OCT15

Retrieved from "https://fedoraproject.org/w/index.php?title=ReleaseEngineering/FedoraAtomicPriorityNotes&oldid=429198"