rel-eng January 2014

rel-eng@lists.fedoraproject.org

7 participants
138 discussions

#5665: Providing a master CHECKSUMS file for boot.fpo
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#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

1 3

#1107: auto-cleanup rawhide trees
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#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

1 8

#5805: add index.asc files for cloud images for virt-builder
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#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

1 16

#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

#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

#5678: koji package for cloud images so they can be non-scratch, and garbage collection policies for those packages
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5678: koji package for cloud images so they can be non-scratch, and garbage collection policies for those packages -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Replying to [ticket:3897 mattdm]: > We want to generate non-scratch cloud images. Because of a bug, these currently need to have the name of the architecture in the package. That will be fixed in the Real Soon Future, but in the meantime I'd like to get going with what we have. Could we please create koji packages named > > {{{ > Fedora-19-cloud-x86_64 > Fedora-19-cloud-i386 > Fedora-20-cloud-x86_64 > Fedora-20-cloud-i386 > Fedora-rawhide-cloud-x86_64 > Fedora-rawhide-cloud-i386 > }}} > > And, we would also like to have a custom garbage collection policy for these; even though they are not scratch builds, they don't need to stay around forever. If we can do a nightly builds (ideal), then I think a week is fine; if they are weekly, keeping a month around seems good. Of course, longer is always better. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5678> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 6

#5622: [RFE] Allow user to (create/)delete private branches
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5622: [RFE] Allow user to (create/)delete private branches -----------------------------+------------------------ Reporter: vondruch | Owner: rel-eng@… Type: enhancement | Status: new Milestone: Fedora 19 Alpha | Component: git Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ I'd like to be able to manage my private branches. For example, in preparation for Ruby 2.0 release, I was pushing my changes to .spec file into Ruby's repository in dist git, into ruby-2.0 branch. This branch is already merged into master for some while and I'd like to delete it, but it is forbidden: {{{ $ git push -f origin :ruby-2.0 remote: + refs/heads/ruby-2.0 ruby vondruch DENIED by fallthru remote: error: hook declined to update refs/heads/ruby-2.0 To ssh://vondruch@pkgs.fedoraproject.org/ruby ! [remote rejected] ruby-2.0 (hook declined) error: failed to push some refs to 'ssh://vondruch@pkgs.fedoraproject.org/ruby' }}} Would it be possible to allow some development branches, which can be created and deleted as well, without need of opening rel-eng tickets etc? Thanks -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5622> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#5329: RFE: Send branched report only when there is any change committed
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5329: RFE: Send branched report only when there is any change committed -----------------------------+------------------------ Reporter: pnemade | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: mash Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, While we are in freeze, can branched report be only sent to the devel/test list when there is any change added for any package? Parag. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5329> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 4

#5218: block httpd-devel.i686, php-devel.i686 from x86_64 compose
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5218: block httpd-devel.i686, php-devel.i686 from x86_64 compose -----------------------------+------------------------ Reporter: jorton | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Could the .i686 packages for both httpd-devel and php-devel be blocked from inclusion in the x86_64 compose, we don't (can't/won't) support them biarch. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5218> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#5215: Stage comps and spin-kickstarts during freezes
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5215: Stage comps and spin-kickstarts during freezes -----------------------------+------------------------ Reporter: adamwill | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: git Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ As noted on the F17 QA retrospective by me and Bruno Wolff: https://fedoraproject.org/wiki/Fedora_17_QA_Retrospective it's a problem that we use git master of both comps and spin-kickstarts for composes - not the latest packaged version - and both these git repos are not frozen during freezes. During the 17 cycle, we had a concrete example of a comps change during a freeze causing considerable trouble: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=807879 - pulling Boxes into comps during the Beta freeze made that issue a serious problem. For spin-kickstarts, the same kind of thing is possible, and we also have a release criterion requiring a spin-kickstarts package which matches the .ks files used for the compose to be present in the release repository; obviously, the lack of a git freeze makes this tricky to ensure. So we would strongly recommend, at minimum, a mechanism for freezing spin- kickstarts and comps at Alpha, Beta and Final freeze. Post-freeze changes could be made following the same blocker/NTH process used for other post- freeze changes. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5215> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng January 2014