Gerald Boersma wrote:
Y'all:
Just some quick questions on the process for reporting and fixing open
bugs for JRuby. For example, I am looking at the current RSpec bugs
(http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=11295&resolution=-1&component=13420&sorter/field=priority&sorter/order=DESC):
1. Many of these defects already have a patch submitted for them, but
are still Open and Unresolved. Is there a way to distinguish ones with
candidate fixes from ones that are unaddressed?
Weeeeell. Not really. You can do a search and exclude things with
attachments, but that's pretty fuzzy. Right now it's only the committers
or the original bug reporter who can change the status on a bug. We
generally use Resolved to mean the fix is in trunk, and Closed for bugs
that have fixes in a released version.
2. Looks like a patch is "published" by attaching the patch to the
defect report and adding a comment. However, does not seem that comments
are published to the JRuby dev mailing list. Is this correct? How are
comments in JIRA monitored and acted on (i.e. new patch available,
clarification questions)?
Oh, you can subscribe to the JIRA mailing list to get announcements on
new reports and changes in them. All core developers are on these lists.
Further, if you submit a bug yourself, you will get all followup emails
related to that bug. I think you can also watch a bug as a third-party,
which means you will get notifications on that too. So all in all this
is very usable. We decided a long time ago to not have JIRA issues
mailed to the dev or user lists, since it's pretty noisy.
3. Who commits the patch? I assume that a limited number of team members
have commit privileges. is this true? If so, I assume they review
patches and check them in at their leisure. Right?
The core developers are the people with commit rights. Currently there
is at least Charles, Tom, me, Nick, Vladimir, Marcin, Mentalguy, Bill
and Wayne. (sorry if I forgot anyone).
We all have different amounts of time to work on issues. Charles and Tom
work full time on these things - but not exclusively bug fixing. There
is also lots of surrounding work going on, plus the new computer and so on.
Nick will have full time once he gets back from vacation. Myself I do
whatever I can but it's more 20-30% work time. The others are mostly
doing this on their spare time, which means people do what they can.
If there are specific issues, they can always be raised and discussed
here or on IRC. That is an easy way to get more rapid action, if it is
judged the bug is fixable and high priority.
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
"Yields falsehood when quined" yields falsehood when quined.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
