Learn more about these different git repos.
Other Git URLs
Currently our releaseProcess wiki page mentions how to build tarball, but not how to update the SSSD team COPR repo at https://copr.fedorainfracloud.org/groups/g/sssd/coprs/
It would be nice to amend the wiki page so that we don't forget and have the process documented.
Repositories in the sssd group COPR are closely tight to fedora releases. The related version in fedora is mention in a description of COPR together with link to koji build. It simplify a maintenance and bug reporting. The only difference is in spec file. Packages in COPR has upstream spec file which if not the same as fedora spec file.
The upstream release process[1] does not mention anything about releasing packages to fedora because it focused on releasing of upstream tarball. But we might create optional/recommended section which will mention releasing new version in fedora + copr. Or it can be a separate wiki page linked from release process.
[1] https://fedorahosted.org/sssd/wiki/ReleaseProcess
OK, I guess on the release process page I would just say "Don't forget to upload the packages to appropriate Fedora versions".
I like the idea about a separate page about copr and Fedora. And chances are we'll have one for Fedora Atomic in the future, too.
Fields changed
cc: => lslebodn
milestone: NEEDS_TRIAGE => SSSD 1.14 backlog
rhbz: => 0
Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.
milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @jhrozek: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: docs
Metadata Update from @thalman: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue tagged with: Canditate to close
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4024
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.