rel-eng January 2015

rel-eng@lists.fedoraproject.org

11 participants
120 discussions

#5883: New Cloud Images Process
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5883: New Cloud Images Process -----------------------------+------------------------ Reporter: red | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: git Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ The cloud kickstart file has been moved to the spin-kickstarts Git by rel- eng. When this happened, it seems there was no discussion regarding the future process to create cloud images and the Spins Process doesn't seem appropriate. Therefore, the Cloud SIG would like to know what the intended process should look like to give new contributors access to the cloud image kickstart files and how to make sure new images (i.e. products) are created from new kickstart files if necessary. For now, mattdm (probably already has) and I need access from the Cloud SIG but more will follow soon as we get ready to work on new products. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5883> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 6

#5880: update to pv-grub aki used in EC2
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5880: update to pv-grub aki used in EC2 -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ * '''What:''' We are currently using old boot images with pv grub 1.02 -- newer versions at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/UserProvidedKernels.html * '''Where:''' https://git.fedorahosted.org/cgit/releng/tree/scripts/cloud/fedora_ec2.py * '''Why:''' new version allows GPT partitions, works with both unpartioned and partitioned, would allow us to use a separate /boot if we want to change the filesystem for / in the future; also new version has bugfixes * '''When:''' F21 alpha; prereq of using whole-disk images -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5880> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#5721: Need application icons and application descriptions
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5721: Need application icons and application descriptions ----------------------------+------------------------ Reporter: rhughes | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Beta | Component: koji Keywords: | Blocked By: Blocking: | ----------------------------+------------------------ Hi, For the application installer preview I need the application icons and localized description data. I had the fedora-app-data package NAKd, but something needs to provide this data. Spot seemed to think it would be okay to include as metadata. The idea is to: * Generate the appstream.xml and appstream.tar files on koji * xmlmerge the .xml files and cat the .tar files when mash'ing the compose together. I've got C code to do the former, although someone familiar with python probably wants to re-write the code before putting it into koji. For F20 we can probably just ship the 15 most popular application icons and descriptions in gnome-software, although this won't scale with all the apps in Fedora. Any questions, I'm hughsie on IRC. Thanks. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5721> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 19

#6047: handle packages that are retired only in Branched but not Rawhide
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#6047: handle packages that are retired only in Branched but not Rawhide -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ Currently we allow to retire packages in Branched even if they are not retired in Rawhide. Today I realized that if a package is retired in Branched (i.e. it will be blocked in f21), it will also not be shipped in Rawhide, even if it is not retired there, because currently if it is blocked in f21 it is also blocked in f22. It might make sense to only retire packages in Branched to not ship packages with broken deps, like it is currently proposed. However this does not mean that the package should be retired in Rawhide, to allow it being fixed for the next release. Therefore we should decide if we: 1) Allow retirement in Branched only for packages retired in Rawhide 2) Unblock packages in f22 if they are only retired in f21 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6047> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 4

#5886: need method for distributing urgent fixes... urgently
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5886: need method for distributing urgent fixes... urgently -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: enhancement | Status: new Milestone: Fedora 21 Alpha | Component: mash Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Right now, the time it takes to do a push of F19 and F20 updates is a critical bottleneck in our ability to put out zero-day security updates. We need a solution for this. I understand that Infrastructure is working on a Netapp fix which will give a 3x speedup. I think that's probably still too slow. We need to be able to put out urgent updates on the scale of minutes, not hours. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5886> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 31

#6027: secondary arch old mash trees cleanup
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#6027: secondary arch old mash trees cleanup -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ There are a lot more old branched/rawhide trees at * http://s390.koji.fedoraproject.org/mash/ * http://ppc.koji.fedoraproject.org/mash/ * http://arm.koji.fedoraproject.org/mash/ that there are at http://kojipkgs.fedoraproject.org/mash/ Adjusting the secondary kojis might allow to save some storage space. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6027> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#5985: Delete branch created by mistake in dist-git: openstack-glance/f21-patches
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5985: Delete branch created by mistake in dist-git: openstack-glance/f21-patches -----------------------------+------------------------ Reporter: hguemar | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: git Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, someone created a branch by mistake in dist-git: f21-patches in openstack-glance. Could someone delete it ? http://pkgs.fedoraproject.org/cgit/openstack-glance.git/log/?h=f21-patches Thanks -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5985> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#5856: tag git commit for successful builds in dist-git
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5856: tag git commit for successful builds in dist-git -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ After a build succeeded, the commit used to build from should be tagged in dist-git. The tag should probably be the build's name-version-release. The information about successful builds could be fetched from fedmsg. Action Items: - Check whether fedmsg contains messages for successful builds - Decide on the name for tags I can work on this, I just want to track this publicly here. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5856> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#5986: write script to get all git commits used to build a package
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5986: write script to get all git commits used to build a package -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: other Keywords: easyfix | Blocked By: Blocking: 5856 | -----------------------------+------------------------ Create a mapping from build NVR to commit ID and vice-versa. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5986> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#5843: Create koji plugin to allow building only from whitelisted git branches
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5843: Create koji plugin to allow building only from whitelisted git branches -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ To allow user git branches, koji needs to be able to allow building only from whitelisted git branches such as master or epel-7. This might need to be addressed in a koji plugin. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5843> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng January 2015