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

Drop ca mgm #21

Closed
wants to merge 4 commits into from
Closed

Drop ca mgm #21

wants to merge 4 commits into from

Conversation

mcalmer
Copy link

@mcalmer mcalmer commented Jun 29, 2015

yast2 ca-mangement module is broken and will not be fixed. It should get dropped.
This commit removes it from yast2-auth-server

@kobliha
Copy link
Member

kobliha commented Jun 29, 2015

Where is a FATE Nr for this request?

@mcalmer
Copy link
Author

mcalmer commented Jun 29, 2015

It's not a feature, it is a fact.

@jsrain
Copy link
Member

jsrain commented Jun 29, 2015

What is the fact?
Every functionality removal needs a Fate entry in order to be covered by release notes and for support to be aware.

@mcalmer
Copy link
Author

mcalmer commented Jun 29, 2015

Fate#319119: drop not functional yast2-ca-management

@jsrain
Copy link
Member

jsrain commented Jun 29, 2015

Master is for both next openSUSE and SLE12-SP1 - in this case, I suggest you should branch the repository first. This feature is not filed or evaluated against SP1.

@mcalmer
Copy link
Author

mcalmer commented Jun 29, 2015

I will leave the git handing for the maintainer of yast2-auth-server. I created only a branch with the start of the work.

@mvidner
Copy link
Member

mvidner commented Oct 22, 2015

SLE-12-SP1 does contain yast2-ca-management, so we must not merge this until the SLE-12-SP1 branch is created.
Anyway, if that module should be dropped, there should be a corresponding PR in that module, and I see none: https://github.com/yast/yast-ca-management/pulls

@mvidner
Copy link
Member

mvidner commented Oct 22, 2015

Ah, master will become SLE-12-SP2 anyway. So the relevant question is: will CA management be in SLE 13? That needs to be agreed on with its product management.

@mcalmer
Copy link
Author

mcalmer commented Oct 22, 2015

If they want, they need to find a new maintainer.

@mcalmer
Copy link
Author

mcalmer commented Oct 22, 2015

And what you mean with a pull request to drop a module.
A pull request with removing all files?

@lslezak
Copy link
Member

lslezak commented Jan 20, 2016

What's the status here? The SP1 is already out...

@mcalmer: The dropped modules have just a short README in the master branch (like in https://github.com/yast/yast-bluetooth) so it's obvious that they are not maintained anymore.

@kobliha
Copy link
Member

kobliha commented Jan 20, 2016

@lslezak Dropping CA Mgmt has to go through FATE, I'm afraid.

@mcalmer
Copy link
Author

mcalmer commented Jan 20, 2016

The fate exists as Fate#319119. But I think it should nobody hold back from removing the usage of it in the auth module :-)

@lslezak
Copy link
Member

lslezak commented Apr 3, 2017

I'm not familiar with ca-mgmt nor auth-server modules, @HouzuoGuo or @varkoly, could you check this and merge it if possible? This PR is open for more than 1 year...

@HouzuoGuo
Copy link
Contributor

CA management is no longer integrated with setting up ID management servers since SLES 15.

@HouzuoGuo HouzuoGuo closed this Feb 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants