Hello, with RHEL-7.6 golang package has been dropped from the RHEL distribution(https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/7.6_release_notes/#chap-Red_Hat_Enterprise_Linux-7.6_Release_Notes-Deprecated_Functionality , grep for golang). We as Go-SIG would be interested in reintroducing it back to epel7. What is the process and policy to reintroduce golang package back in to epel7?(I guess commit to the branch and file rel-eng ticket to unblock it in koji/bodhi?)
Yes, releng ticket to unblock and commits to bring it back in git.
I don't see any reason you cannot do this if rhel has dropped support...
So there are 2 parts to the request:
Use the Go Toolset instead of golang The golang package, previously available in the Optional channel, will no longer receive updates in Red Hat Enterprise Linux 7. Developers are encouraged to use the Go Toolset instead, which is available through the Red Hat Developer program.
A Release Engineering Ticket needs to be opened that these packages are no longer retired/blocked.
Thank you for clarification. Should I wait until this get approved by epel committee, before I will open the rel-eng ticket? When it will be on your meeting agenda?
If we have quorum it will be on todays meeting. On Wed, 14 Nov 2018 at 04:54, Jakub =C4=8Cajka pagure@pagure.io wrote:
jcajka added a new comment to an issue you are following: `` A Release Engineering Ticket needs to be opened that these packages are= no longer retired/blocked. Thank you for clarification. Should I wait until this get approved by epe= l committee, before I will open the rel-eng ticket? When it will be on your= meeting agenda? `` To reply, visit the link below or just reply to this email https://pagure.io/epel/issue/49
jcajka added a new comment to an issue you are following: ``
A Release Engineering Ticket needs to be opened that these packages are= no longer retired/blocked. Thank you for clarification. Should I wait until this get approved by epe= l committee, before I will open the rel-eng ticket? When it will be on your= meeting agenda?
A Release Engineering Ticket needs to be opened that these packages are= no longer retired/blocked.
Thank you for clarification. Should I wait until this get approved by epe= l committee, before I will open the rel-eng ticket? When it will be on your= meeting agenda?
``
To reply, visit the link below or just reply to this email https://pagure.io/epel/issue/49
--=20 Stephen J Smoogen.
If we have quorum it will be on todays meeting.
Great, I will try to attend if there would be any questions, but I have already clash for that time slot, so no guarantee that I will be there.
Meeting is going to have to be rescheduled due to conflicts for other people. I will ask people to vote on this in the ticket in fesco style. On Wed, 14 Nov 2018 at 10:51, Jakub =C4=8Cajka pagure@pagure.io wrote:
jcajka added a new comment to an issue you are following: `` If we have quorum it will be on todays meeting. Great, I will try to attend if there would be any questions, but I have a= lready clash for that time slot, so no guarantee that I will be there. `` To reply, visit the link below or just reply to this email https://pagure.io/epel/issue/49
Great, I will try to attend if there would be any questions, but I have a= lready clash for that time slot, so no guarantee that I will be there. ``
There was a question in the meeting if this request was ok with the golang SIG. We do not want to make work for them if they are not wanting to support this package.
If the SIG is ok with this it has been approved by EPSCO to be retired and will be recorded as an allowed exception in the main site soon.
Sorry for not attending the meeting, but it have been really late for me and I have been already booked for that time slot.
As I will be the person maintaining it, I'm fine with that. For the start I will keep the el7 branch on same support intensity as I'm keeping el6 branch.
If we decide in SIG that we want to enable the whole stack with all the (S)RPM macros, that will be completely different and separate story to this "resurrection".
Put in a ticket to releng and you are good to go!
Metadata Update from @smooge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.