felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Meschberger <fmesc...@adobe.com>
Subject Re: patching process for ultra-fine revisions
Date Fri, 09 Mar 2012 16:33:32 GMT

Am 09.03.2012 um 08:25 schrieb Reuben Garrett:

> What's our normal process for submitting patches against very small
> sections of the code base (e.g. one-word javadoc corrections)?  For
> example, I noticed that the default timeout value for iPOJO's @Temporal
> annotation [1] is javadoc'd as "true", but is actually a long with default
> 3000.
> It seems like overkill to open a JIRA ticket for that, although maybe it's
> not a big deal if we're not worried about exhausting the ticket number
> namespace.  One could also group together several such changes, although
> this raises the question of how many changes are sufficient, and delays
> corrections until that threshold is reached.

IMHO the cleanest thing is to go with JIRA issues. Don't care about running out of ticket
numbers ...

The only point is that it looks like somewhat heavy lifting. Yet, you will have issue backed
traces of the code changes...

View raw message