Hey all,
I prepared a F24 Change proposal for PDC here:
https://fedoraproject.org/wiki/Changes/PDC
Anyone want to give it a review, make any edits, or add yourself to it
before I send it in?
-Ralph
For anyone who isn't already aware, I've partnered with the Fedora release tooling folks to help organize work and communication into and out of the team. The team is focused on tooling & process in support of the release engineering functions of Fedora. The core team consists of Adam Miller, Kushal Das, Dennis Gilmore, Luke Macken & Sayan Chowdhury with special guest appearances as needed. I've been working with the team for a couple of months now on a trial basis and we're making it more official post-F23. We're making a few changes in our process to make things more transparent and predictable...
* moving our project work into Taiga [1] & using its kanban board to track what we're doing
* publishing our commitments for Fedora releases and our priority pipeline [2] so that it's easier to see what's planned (this includes being more diligent about filing changes for bigger items)
* regular meetings with some stakeholders to make sure that we're getting the right input to the team (I am always open to hear from anyone so shout at me if you need to)
* regular backlog grooming meetings with the team to review our priorities on a weekly or biweekly basis
* monthly live demos of our completed work
This is still unfolding and we're working out kinks and getting into the swing of things, so please bear with us as we do. I wanted to get this note out to you all (and feel free to forward) to make sure that everyone was aware of the changes and can get engaged in the process. If you have questions, feedback or need to reach out at any time, please let me know.
Thanks in advance!
--
Amanda Carter
[1] http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-t…
[2] https://fedoraproject.org/wiki/ReleaseEngineering/PriorityPipeline
PS - adding tflink here b/c I assume I need to be a member of the qa list before my message will be sent and I'm waiting for approval there; let me know if I need to resend please?
#6287: 1 Package missing from mirrors
-----------------------------+-------------------
Reporter: limb | Owner: limb
Type: defect | Status: new
Milestone: Fedora 22 Final | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+-------------------
libreoffice-4.4.5.2-11.fc22
Pushed to stable at the same time as libreoffice-4.4.5.2-10.fc22
Re-tagged.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6287>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6149: Fedora secondary arches .composeinfos are missing and need to be made
---------------------+------------------------
Reporter: alemay | Owner: pbrobinson
Type: task | Status: new
Milestone: | Component: other
Resolution: | Keywords:
Blocked By: | Blocking: testing
---------------------+------------------------
Comment (by pbrobinson):
Replying to [comment:7 alemay]:
> Well then they need to be manually made. So they get imported
internally.
Or beaker could be updated to use .treeinfo like all other tools,
.composeinfo is EOL, it's only used by beaker. Everything else uses
.treeinfo, the later also has the advantage of being signed and
verifiable:
{{{
https://dl.fedoraproject.org/pub/fedora-
secondary/releases/23/Server/aarch64/os/.treeinfo.signed
https://dl.fedoraproject.org/pub/fedora-
secondary/releases/23/Server/ppc64/os/.treeinfo.signed
https://dl.fedoraproject.org/pub/fedora-
secondary/releases/23/Server/ppc64le/os/.treeinfo.signed
}}}
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6149#comment:8>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6149: Fedora secondary arches .composeinfos are missing and need to be made
---------------------+------------------------
Reporter: alemay | Owner: pbrobinson
Type: task | Status: new
Milestone: | Component: other
Resolution: | Keywords:
Blocked By: | Blocking: testing
---------------------+------------------------
Comment (by alemay):
Well then they need to be manually made. So they get imported internally.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6149#comment:7>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6149: Fedora secondary arches .composeinfos are missing and need to be made
---------------------+------------------------
Reporter: alemay | Owner: pbrobinson
Type: task | Status: new
Milestone: | Component: other
Resolution: | Keywords:
Blocked By: | Blocking: testing
---------------------+------------------------
Comment (by ausil):
secondary arches need to put .composeinfo files in their arch directories,
the way secondary arches work it is not possible to make one .composeinfo
file for all arches
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6149#comment:6>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6149: Fedora secondary arches .composeinfos are missing and need to be made
---------------------+------------------------
Reporter: alemay | Owner: pbrobinson
Type: task | Status: new
Milestone: | Component: other
Resolution: | Keywords:
Blocked By: | Blocking: testing
---------------------+------------------------
Comment (by pbrobinson):
They'll be there for f23 GA
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6149#comment:5>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project