#1107: auto-cleanup rawhide trees
--------------------------+-----------------------
Reporter: notting | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: | Component: mash
Resolution: | Keywords: meeting
Blocked By: | Blocking:
--------------------------+-----------------------
Changes (by ausil):
* keywords: => meeting
Comment:
We need to decide on a policy
we need a script to implement the policy and have it ran as part of
rawhide.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1107#comment:10>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2016-03-21 from 10:30:00 to 11:30:00 US/Central
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org/calendar/meeting/2026/
#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
Hi,
yesterday, on the F24 Alpha readiness meeting [1] we were discussing
Fedora 24 Alpha release time. Even we do not know now the date, as
Go/No-Go decision was to slip, we would like to be ready and
synchronized across teams when bits are ready.
We mostly agreed on 14:00 UTC as the time to have everything released.
Unfortunately we were missing any feedback from Release Engineering
team on this topic. As the Release Engineering team plays the crucial
role during the release process, I would like to follow up this
discussion here, to make sure the Release Engineering tea is aware of
it and has no objections.
[1] https://meetbot.fedoraproject.org/fedora-meeting/2016-03-17/f24-alpha-readi…
Thanks in advance for any feedback.
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
#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
#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: closed
Milestone: Fedora 23 Alpha | Component: koji
Resolution: fixed | Keywords:
Blocked By: | Blocking:
------------------------------+-----------------------
Changes (by ausil):
* status: new => closed
* resolution: => fixed
Comment:
We are now doing real build for f24 up
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5678#comment:7>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6366: missing metadata about nightly rawhide/24 composes
-----------------------------+------------------------
Reporter: bpeck | Owner: rel-eng@…
Type: defect | Status: new
Milestone: Fedora 24 Alpha | Component: other
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Currently there is no metadata about a compose in the rsync share. This
makes it very difficult to know what is available to rsync/import.
rsync rsync://dl.fedoraproject.org/fedora-linux-development/rawhide/
----------------------------
Fedora Master Mirror Servers
----------------------------
Modules for Fedora Core and Extras have been removed, as this content is
no longer updated. See the instructions below for how to mirror current
content.
See http://fedoraproject.org/wiki/Infrastructure/Mirroring for
instructions.
----------------------------
drwxrwxr-x 4,096 2016/03/09 13:26:55 .
drwxrwxr-x 4,096 2016/03/08 11:08:04 Atomic
drwxrwxr-x 4,096 2016/03/08 07:33:16 CloudImages
drwxrwxr-x 4,096 2016/03/08 07:33:17 Docker
drwxrwxr-x 4,096 2016/03/08 07:33:20 Everything
drwxrwxr-x 4,096 2016/03/08 07:36:56 Server
drwxrwxr-x 4,096 2016/03/08 07:37:03 Spins
drwxrwxr-x 4,096 2016/03/08 07:37:04 Workstation
In the past we used to have a .composeinfo file which not only told us
which trees were available in a compose but whether the compose completed
successfully.
Both of these attributes are important to keep testing. We don't want to
overwrite a working release with a broken one.
It appears that the .composeinfo file format is going away and being
replaced with metadata/composeinfo.json which is fine. We can update our
code to work with this but according to dgilmore its not as easy as simply
copying this file over since the compose gets carved up.
It sounds like the process that does the carving should produce a new
composeinfo.json which describes the carved up version.
Until this ticket is resolved we will not be able to mirror Fedora inside
Red Hat for testing.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6366>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project