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

[dev.icinga.com #10553] Update SELinux documentation #3612

Closed
icinga-migration opened this issue Nov 6, 2015 · 8 comments

Comments

Projects
None yet
1 participant
@icinga-migration
Copy link
Member

commented Nov 6, 2015

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10553

Created by mfriedrich on 2015-11-06 12:31:49 +00:00

Assignee: dgoetz
Status: Resolved (closed on 2016-08-09 06:55:04 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-09 06:55:04 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

Right now this is an outdated text document, which I've moved to a feature branch and removed from the 2.4 branch. Please update it accordingly.

Changesets

2015-11-06 12:34:58 +00:00 by mfriedrich 4cfde2d

Remove outdated SELinux documentation for now

refs #10553

2016-04-11 13:01:36 +00:00 by dgoetz 5ffa35d

Adds some clarification to SELinux doc
Adds SELinux doc before reference docs

refs #10553

2016-04-18 11:28:24 +00:00 by dgoetz d17fbb3

Adds some clarification to SELinux doc
Adds SELinux doc before migration

refs #10553

2016-08-09 06:51:20 +00:00 by dgoetz b2a1541

Docs: Add SELinux chapter

fixes #10553

Relations:

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 6, 2015

Updated by dgoetz on 2015-11-06 12:38:41 +00:00

Can you merge the latest doc from the branch feature/rpm-selinux-8332 and give me than some details what is missing?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 9, 2015

Updated by mfriedrich on 2015-11-09 09:24:01 +00:00

  • the manual installation instructions should be logically separated from the package installation
  • manual installation references git and a feature branch - better got for packages and their provided content?
  • creating a user mentions "dirk" ... it is unclear to me why such a user should exist
  • find a proper target in the index, 99-selinux.md isn't good. Better go for one before the appendix, rename the files, run ./update-links.py *.md and then update mkdocs.yml
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Apr 11, 2016

Updated by dgoetz on 2016-04-11 13:09:19 +00:00

Pushed some clarifications and moved it in the docs after normal docs and before reference docs.

Are there any more changes required? If not please close this issue and 8332 and after merging also delete the feature branches. Thanks.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Apr 13, 2016

Updated by gbeutner on 2016-04-13 10:17:09 +00:00

Please rebase your branch against the current master. Your latest commit (5ffa35) is a merge commit.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Apr 18, 2016

Updated by dgoetz on 2016-04-18 11:36:50 +00:00

I reseted the branch, added the doc again and moved them to be right before the migration like discussed offline.
So I hope it is fine now.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 3, 2016

Updated by gbeutner on 2016-08-03 08:17:15 +00:00

  • Blocks set to 8332
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 9, 2016

Updated by mfriedrich on 2016-08-09 06:52:24 +00:00

  • Target Version set to 2.5.0

https://twitter.com/icinga/status/762851454805606400

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 9, 2016

Updated by dgoetz on 2016-08-09 06:55:04 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset b2a1541.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.