======================================
#fedora-meeting-2: RELENG (2018-10-04)
======================================
Meeting started by mboddu at 17:00:04 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2018-10-04/releng.2018…
.
Meeting summary
---------------
* init process (mboddu, 17:00:04)
* LINK: https://pagure.io/releng/pull-requests (nirik, 17:28:09)
* mboddu will go over the PR's in different repo's and clean them up
and will also run a new fedora-release build for f28. (mboddu,
17:43:55)
Meeting ended at 17:51:17 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (42)
* nirik (30)
* zodbot (8)
* bowlofeggs (5)
* sgallagh (2)
* relrod (2)
* tyll (0)
* puiterwijk (0)
* masta (0)
* Kellin (0)
* pbrobinson (0)
* dustymabe (0)
* pingou (0)
* maxamillion (0)
* sharkcz (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2018-10-04 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-2(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org/calendar/meeting/9274/
cverna opened a new pull-request against the project: `releng` that you are following:
``
Use manifest list for stg container base image
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/7851
mclasen reported a new issue against the project: `releng` that you are following:
``
Please add gnome-clocks to the f29-flatpak tag.
$ koji add-pkg --owner=releng f29-flatpak gnome-clocks
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7850
The status of the issue: `Please unretire rust-slab0.3` of project: `releng` has been updated to: Closed as Fixed by mohanboddu.
https://pagure.io/releng/issue/7847
mohanboddu added a new comment to an issue you are following:
``
@eclipseo Okay, thanks for the info and will close the ticket now.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7847
ignatenkobrain added a new comment to an issue you are following:
``
Isn't it possible to switch to newer version of slab? Also what is the use-case for mio-more?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7847
mizdebsk reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Please set EOL dates in to "2018-12-01" for the following branch SLAs in PDC:
1. branch SLA ID 739258,
SLA name "rawhide",
branch ID 370671,
branch name "1.10",
global component "ant",
branch type "module",
new EOL date "2018-12-01"
2. branch SLA ID 739214,
SLA name "rawhide",
branch ID 370645,
branch name "3.5",
global component "maven",
branch type "module",
new EOL date "2018-12-01"
3. branch SLA ID 739215,
SLA name "rawhide",
branch ID 370646,
branch name "201801",
global component "javapackages-tools",
branch type "module",
new EOL date "2018-12-01"
4. branch SLA ID 741257,
SLA name "rawhide",
branch ID 371899,
branch name "2.10",
global component "scala",
branch type "module",
new EOL date "2018-12-01"
* When do you need this? (YYYY/MM/DD)
Earliest convenience.
* When is this no longer needed or useful? (YYYY/MM/DD)
N/A
* If we cannot complete your request, what is the impact?
Branches will still be marked as inactive in PDC. As a consequence packagers may be unable to push to these branches. Additionally, after EOL enforcement is re-enabled, module builds from these branches may no longer be working.
Please let me know if you prefer branch SLAs listed in a different form, as I will be opening a new ticket with more (~200) SLAs to be updated soon.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7843
mohanboddu added a new comment to an issue you are following:
``
@eclipseo Are you willing to maintain it and what are the branches you want it to be unretired for?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7847