rel-eng February 2016

rel-eng@lists.fedoraproject.org

9 participants
66 discussions

#6350: integrate atomic (host and other) CI/CD into Fedora
by Fedora Release Engineering 02 Oct '16

02 Oct '16

#6350: integrate atomic (host and other) CI/CD into Fedora -----------------------------+------------------------ Reporter: walters | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Breaking out from: https://fedorahosted.org/rel-eng/ticket/6313 Let's define a system and process for CD (Continuous Delivery) that bypasses manual integration via Koji/Bodhi and ships as quickly as possible to a small audience on dl.fedoraproject.org. Specifically, use rpmdistro-gitoverlay to mirror upstream sources that we know have been peer reviewed already, and build/ship them automatically. Also generate a devel/ ostree ref based on this content, and potentially images. Integrate pull request testing into this too. Resources required: - OpenStack tenant resources - Ability to write to dl.fedoraproject.org somewhere -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6350> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 9

#6304: ability to test spin-kickstars by doing throw away image builds in koji
by Fedora Release Engineering 12 Sep '16

12 Sep '16

#6304: ability to test spin-kickstars by doing throw away image builds in koji -----------------------------+------------------------ Reporter: dustymabe | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ It would be nice to be able to create image builds in koji that are throw away builds that are purely used for testing of changes to kickstart files etc.. The idea is that we would use these as a way to test our changes before officially commiting them to the spin-kickstarts repo. Having this ability would mean it is much easier for contributors to test changes and thus more likely to submit fixes and or suggestions back. We can currently do an image build on our own machines but it does take some setup and it is not the same environment as the one in koji. So, while we can test on our own machines, is it a valid test? Not really. I would love this functionality. I know it might not technically be possible right now to do, but we shouldn't ignore its value and should perhaps take steps to get there. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6304> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 12

#6200: Cannot mirror Fedora drpms using OpenAFS
by Fedora Release Engineering 27 Jun '16

27 Jun '16

#6200: Cannot mirror Fedora drpms using OpenAFS -----------------------------+------------------------ Reporter: tc01 | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 22 Final | Component: other Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ I had (mistakenly) filed this against infrastructure: https://fedorahosted.org/fedora-infrastructure/ticket/4798 To summarize: we'd like to run a Fedora mirror in an OpenAFS cell, but the drpms/ directory is far larger than the 64K slot limit in OpenAFS and, as a result, cannot mirror them. We are currently just excluding the drpms, which works, but I'd like to be able to mirror them if possible. A couple of possible fixes are mentioned in the discussion on that ticket; keeping fewer drpms, or organizing the drpms into alphabetical subdirectories instead of one giant drpms/ directory. How does rel-eng feel about this? Is this something that could be fixed in some way or should we merely continue to exclude the drpms? Thanks in advance. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6200> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 6

#6333: delete errant rhos-8.0-rhel-7 from erlang dist-git
by Fedora Release Engineering 27 Jun '16

27 Jun '16

#6333: delete errant rhos-8.0-rhel-7 from erlang dist-git ----------------------+------------------------ Reporter: jeckersb | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: git Keywords: | Blocked By: Blocking: | ----------------------+------------------------ I accidentally pushed a rhos-8.0-rhel-7 branch to the fedora remote on the erlang repo, and the commit hook won't let me delete it by pushing an empty ref overtop. Please delete this branch manually (or better, tell me how to delete it if I can do it myself! http://pkgs.fedoraproject.org/cgit/rpms/erlang.git/log/?h=rhos-8.0-rhel-7 Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6333> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6261: Create secondary release staging SOP
by Fedora Release Engineering 27 Jun '16

27 Jun '16

#6261: Create secondary release staging SOP -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Should be similar to the one for primary I guess: https://fedoraproject.org/wiki/Stage_final_release_for_mirrors It came up when I noticed that the CHECKSUM files for secondary test releases are not signed: https://dl.fedoraproject.org/pub/fedora- secondary/releases/test/23_Alpha/Server/ppc64le/iso/Fedora-Server-23 -ppc64le-CHECKSUM -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6261> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#6289: Add license information to new sphinx docs
by Fedora Release Engineering 10 Apr '16

10 Apr '16

#6289: Add license information to new sphinx docs -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 22 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ With the conversion from the wiki to sphinx, the license information of the content got lost. The wiki contains the statement {{{Content is available under Attribution-Share Alike 3.0 Unported unless otherwise noted.}}}. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6289> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#6334: script needed for openh264
by Fedora Release Engineering 22 Mar '16

22 Mar '16

#6334: script needed for openh264 -----------------------------+------------------------ Reporter: ausil | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ a basic outline of the steps needed koji move-pkg <source tag> <dest-tag> list the latest rpms in the tag sign the rpms something like "NSS_HASH_ALG_SUPPORT=+MD5 sigul sign-rpms --v3-signature --store-in-koji fedora-24 /mnt/koji/packages/openh264/1.5.2/0.3.git21e44bd.fc24/*/*rpm -o tmp/signed/" import the signatures into koji "koji import-sig tmp/signed/*" write out the signed rpms mash the repo sign the repo metadata tar up the repo create email attching the tarball and send it to the folks over at cisco. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6334> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6286: Please sign all RC and TC images
by Fedora Release Engineering 19 Mar '16

19 Mar '16

#6286: Please sign all RC and TC images -------------------------+------------------------ Reporter: genodeftest | Owner: rel-eng@… Type: enhancement | Status: new Milestone: | Component: koji Keywords: | Blocked By: Blocking: | -------------------------+------------------------ Current situation: TC and RC images are provided on an server that does not force encryption ( http://dl.fedoraproject.org/pub/alt/stage/ ) and does not provide any signatures (see e.g. http://dl.fedoraproject.org/pub/alt/stage/23_RC10/Workstation/x86_64/iso/ ). Attacker model: * many government intelligence agencies including (but not limited to) NSA and GCHQ * some companies * criminals have an interest to intrude PCs of most people in the world. Especially testers (often software developers themselves) are at risk for being attacked since they are a high-value target for redistributing malware. Having unsigned software to download is one way to make this possible. Please provide Signatures for all RC and TC images in the future. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6286> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 10

#6339: Please drop epel-rpm-macros from buildsys group
by Fedora Release Engineering 18 Mar '16

18 Mar '16

#6339: Please drop epel-rpm-macros from buildsys group -----------------------------+------------------------ Reporter: remi | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ This package brings a very low benefit and create very bad issues. Broken SCL build: https://bugzilla.redhat.com/1301358 Even if SCL are not allowed in Fedora, this is a huge blocker for some of us (working on RHSCL or CentOS-SCL) More, the spec file in EPEL can now be incompatible with RHEL / CentOS build system (where these macros don't exists). If really you want such things, please open a RH bug to have them include upstream. Having such workaround only in EPEL seems a terrible bad idea. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6339> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#6262: drop rawhide-stable tag and consider master branch to be always stable
by Fedora Release Engineering 10 Mar '16

10 Mar '16

#6262: drop rawhide-stable tag and consider master branch to be always stable -------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: enhancement | Status: new Milestone: | Component: other Keywords: meeting | Blocked By: Blocking: | -------------------------+------------------------ Since we require patch reviews for the rel-eng pagure repo and use it for running buildbranched/buildrawhide, we can IMHO drop using the rawhide- stable tag and just consider the master branch to be always stable enough to run the scripts from it directly. AFAICS only ansible needs to be adjusted to change the crontab to not checkout rawhide-stable but master for primary and secondaries systems. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6262> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng February 2016