Learn more about these different git repos.
Other Git URLs
We have develTips and develTutorial wiki pages, but we might amend them with more options on best practices on what should be done before sending a patch, such as how to run different code analysis tools etc.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.11 rhbz: => 0
In a patch review of AD lookup patches for IPA server mode, Sumit raised a good point -- in new code at least, parameters should not be read directly from confdb or opts but rather passed as parameters. This makes the code more reusable and avoids big refactoring/splitup patches. This guidance should be part of best practices.
milestone: SSSD 1.11.1 => SSSD 1.11.2
milestone: SSSD 1.11.2 => SSSD 1.12 beta
milestone: SSSD 1.12 beta => SSSD 1.12.1
Mass-moving all tickets that didn't make 1.12.1 into 1.12.2
milestone: SSSD 1.12.1 => SSSD 1.12.2
We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3
milestone: SSSD 1.12.2 => SSSD 1.12.3
mark: => 0 milestone: SSSD 1.12.3 => SSSD 1.12.4
Moving tickets that didn't make the 1.12.4 release to 1.12.5
milestone: SSSD 1.12.4 => SSSD 1.12.5
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.12.5
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/3027
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.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.