#5665: Providing a master CHECKSUMS file for boot.fpo
-----------------------------+------------------------
Reporter: shaiton | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Alpha | Component: other
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Hi, as requested to webmasters[1], could we get a CHECKSUMS file (as
provided for other Fedora releases) including all checksums?
It also needs to be signed of course.
You might decide that it is not needed, just forwarded the query.
[1]
https://lists.fedoraproject.org/pipermail/websites/2013-July/011535.html
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5665>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#1107: auto-cleanup rawhide trees
-------------------------+--------------------------------------------------
Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: koji
Keywords: |
-------------------------+--------------------------------------------------
Rawhide tree expiry is manual at the moment, unless I missed something.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1107>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5894: git branches for SCL packages
-----------------------------+------------------------
Reporter: mmaslano | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Alpha | Component: git
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
I would prefer SCL packages in branches of the main package (eg ruby). We
used the same approach in some internal projects and it worked well with
koji, composes, everything...
I suggest name of branches:
scl-f21
scl-f22
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5894>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5805: add index.asc files for cloud images for virt-builder
----------------------------+------------------------
Reporter: mattdm | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: Fedora 20 Beta | Component: other
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
Please add a GPG-signed 'index.asc' file to the Fedora 20 Images/
directory describing cloud images for virt-builder and other tools.
The format is documented at http://libguestfs.org/virt-builder.1.html
#creating-your-own-templates, and there's actually a Fedora example there.
Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5805>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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
#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
#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
#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
#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
#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