#2417 refactor sdap_nested_group_hash_group
Closed: wontfix 4 years ago by pbrezina. Opened 9 years ago by preichl.

Refactor sdap_nested_group_hash_group as incremental changes made this function hard to understand and potentially bug prone.

Unit test would be be nice too.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.1
owner: somebody => preichl
rhbz: => 0

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

Fields changed

mark: => 0
patch: 0 => 1

Refactoring should go to master.

milestone: SSSD 1.12.3 => SSSD 1.13 alpha

Should not block Alpha

milestone: SSSD 1.13 alpha => SSSD 1.13 beta
sensitive: => 0

Should not block Beta either.

milestone: SSSD 1.13 beta => SSSD 1.13

Patch was submitted, should be included in 1.13.1

milestone: SSSD 1.13.2 => SSSD 1.13.1

oops, sorry, wrong ticket. It's too late for refactoring of 1.13

milestone: SSSD 1.13.1 => SSSD 1.14 beta

I'm afraid there won't be enough time in 1.14

milestone: SSSD 1.14 beta => SSSD 1.15 beta

Metadata Update from @preichl:
- Issue assigned to preichl
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch adjusted to on (was: 1)
- 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: Canditate to close

4 years ago

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)

4 years ago

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/3459

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata