Page MenuHomeFreeBSD

Pr-Guidelines Article: make it clear that the article is Bugzilla-specific
Needs ReviewPublic

Authored by linimon on Sun, Nov 9, 3:22 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 9, 8:41 PM
Unknown Object (File)
Sun, Nov 9, 8:35 PM
Unknown Object (File)
Sun, Nov 9, 7:35 PM
Unknown Object (File)
Sun, Nov 9, 7:33 PM
Unknown Object (File)
Sun, Nov 9, 7:31 PM
Unknown Object (File)
Sun, Nov 9, 7:27 PM
Subscribers
None

Details

Summary

This article has not been updated in years. There is so much wrong, that it will need to be tackled in multiple patches.

This first patch simply states that the article is Bugzilla-specific, and that any use of "PR" means "Bugzilla Problem Report". In a few cases, this is now spelled out explicitly.

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

linimon created this revision.

I think expending "PR" to "problem report" is a good thing, as nowadays that "PR" might be known by more people as "pull request"
While I don't think we'll be moving away from Bugzilla anytime soon, I suggest that keeping the title of this article independent of the issue tracking software we're using so it might be easier to update in the future.
We can mention in the beginning of this articles that the current issue tracking software the FreeBSD project uses is Bugzilla and this article will mainly cover it.

We can mention in the beginning of this articles that the current issue tracking software the FreeBSD project uses is Bugzilla and this article will mainly cover it.

oh I didn't see D53644 while writing this. Then I think it's fine.

documentation/content/en/articles/pr-guidelines/_index.adoc
72

What is this 'Needs MFC' state? Usually the bug is marked as 'In Progress' still, with the MFC keywords set to act as a reminder to MFC.

documentation/content/en/articles/pr-guidelines/_index.adoc
72

This is just a hold-over from the existing text.