Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

write up nslcd-sssd comparison #4438

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

write up nslcd-sssd comparison #4438

sssd-bot opened this issue May 2, 2020 · 0 comments

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3411

  • Created at 2017-05-25 20:28:02 by jhrozek
  • Closed at 2020-03-24 14:03:45 as wontfix
  • Assigned to nobody

Since some distributions might want to completely deprecate nslcd in favor of sssd, we should have a document that compares the two and use it as a basis to close the gaps.

Comments


Comment from simo at 2017-05-30 13:37:32

Metadata Update from @Simo:

  • Issue tagged with: docs

Comment from jhrozek at 2017-06-01 17:08:11

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD 1.15.4

Comment from jhrozek at 2017-08-18 16:14:29

Metadata Update from @jhrozek:

  • Issue tagged with: cleanup-one-sixteen

Comment from jhrozek at 2017-08-23 17:19:08

Metadata Update from @jhrozek:

  • Issue untagged with: cleanup-one-sixteen
  • Issue priority set to: trivial
  • Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)

Comment from jhrozek at 2017-10-19 20:43:32

Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1


Comment from jhrozek at 2017-10-19 20:43:37

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)

Comment from jhrozek at 2017-12-18 20:34:37

Metadata Update from @jhrozek:

  • Issue tagged with: postpone-to-2-0

Comment from jhrozek at 2018-01-08 18:24:28

Metadata Update from @jhrozek:

  • Issue untagged with: postpone-to-2-0
  • Issue set to the milestone: SSSD 2.0 (was: SSSD 1.16.1)

Comment from jhrozek at 2018-08-13 11:11:57

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)

Comment from jhrozek at 2019-02-22 15:49:54

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

Comment from jhrozek at 2019-06-13 23:21:56

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

Comment from thalman at 2020-03-11 11:12:24

Metadata Update from @thalman:

  • Issue tagged with: Canditate to close

Comment from pbrezina at 2020-03-24 14:03:44

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.


Comment from pbrezina at 2020-03-24 14:03:45

Metadata Update from @pbrezina:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant