You're over thinking it. :-)
Opening an issue is probably the best way, since it enables a single
work pattern for making sure things don't get lost. Don't worry about
conserving bits.
Besides, we feel really productive when we can resolve open issues... ;-)
-> richard
On 3/9/12 11:25 , Reuben Garrett wrote:
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.
Sorry if I'm over-thinking this - I'm still a fledgling.
~ RNPG
[1] :
http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.ipojo.annotations-1.8.0/src/main/java/org/apache/felix/ipojo/handler/temporal/Temporal.java
