Perpetual Jira Issues for Javadoc, Spelling, etc.?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Perpetual Jira Issues for Javadoc, Spelling, etc.?

Keith R. Bennett
Hello, all.

In order to minimize the effort required to fix less critical things like Javadoc errors and spelling, would you want to have a special JIRA issue that would always be open for this?

That way, someone seeing such an error can immediately (without the slower patch review process) commit the fix and refer to that JIRA issue.  Of course, we could mandate that any commits bypassing review consist *only* of this kind of fix.

I've seen some Javadoc errors (e.g. incorrect parameter names) and misspellings.  Without a way to bypass review, these fixes would take longer to fix, or possibly not be fixed at all.

- Keith
Reply | Threaded
Open this post in threaded view
|

Re: Perpetual Jira Issues for Javadoc, Spelling, etc.?

Bertrand Delacretaz-2
Hi Keith,

On 10/15/07, Keith R. Bennett <[hidden email]> wrote:
> ...That way, someone seeing such an error can immediately (without the slower
> patch review process) commit the fix and refer to that JIRA issue....

AFAIU we currently work mostly in "commit-then-review" mode, with some
"review-then-commit" patches when someone is unsure about the impact
or wants to have a review.

I'm not sure if we made a formal decision on this, but if I'm right
everybody's free to commit "obvious" bugfixes at any time, without
prior review. I think we trust each other enough on this, and
subversion is here to fix the occasional slip.

Do others agree on this?

-Bertrand
Reply | Threaded
Open this post in threaded view
|

Re: Perpetual Jira Issues for Javadoc, Spelling, etc.?

Keith R. Bennett
So fixing Javadoc, spelling errors, etc. would be an exception to the 'all commits must refer to a JIRA issue' rule?

- Keith