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

expand the developer tutorials with best practices #3027

Closed
sssd-bot opened this issue May 2, 2020 · 1 comment
Closed

expand the developer tutorials with best practices #3027

sssd-bot opened this issue May 2, 2020 · 1 comment

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

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

  • Created at 2013-06-14 22:01:11 by jhrozek
  • Assigned to nobody

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.

Comments


Comment from dpal at 2013-06-20 15:54:07

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11
rhbz: => 0


Comment from jhrozek at 2013-06-28 21:26:14

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.


Comment from jhrozek at 2013-09-26 11:00:24

Fields changed

milestone: SSSD 1.11.1 => SSSD 1.11.2


Comment from dpal at 2013-10-03 15:04:17

Fields changed

milestone: SSSD 1.11.2 => SSSD 1.12 beta


Comment from jhrozek at 2014-05-30 15:54:50

Fields changed

milestone: SSSD 1.12 beta => SSSD 1.12.1


Comment from jhrozek at 2014-09-08 20:09:20

Mass-moving all tickets that didn't make 1.12.1 into 1.12.2

milestone: SSSD 1.12.1 => SSSD 1.12.2


Comment from jhrozek at 2014-09-30 19:06:36

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


Comment from jhrozek at 2014-11-19 18:17:48

Fields changed

mark: => 0
milestone: SSSD 1.12.3 => SSSD 1.12.4


Comment from jhrozek at 2015-02-18 19:29:19

Moving tickets that didn't make the 1.12.4 release to 1.12.5

milestone: SSSD 1.12.4 => SSSD 1.12.5


Comment from jhrozek at 2017-02-24 15:04:40

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD 1.12.5
@andreboscatto
Copy link
Contributor

Please visit https://sssd.io/contrib/introduction.html

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

No branches or pull requests

2 participants