Update on bug system for OpenJDK (web-discuss)
aph at redhat.com
Wed May 25 10:07:06 UTC 2011
On 05/25/2011 10:39 AM, Mohan Pakkurti wrote:
> On May 25, 2011, at 12:36 AM, Dr Andrew John Hughes wrote:
>> On 24 May 2011 21:20, Mohan Pakkurti <mohan.pakkurti at oracle.com> wrote:
>>> Hi all,
>>> I have posted an update on the effort to create a bug system for
>>> OpenJDK here:
>>> Please join that discussion if you have any comments.
>> The current discussion seems to be very much one-sided in favour of
>> JIRA. Here are a number of points that aren't covered and may balance
>> things up:
>> * The language of Bugzilla (Perl) is denoted as a negative, while the
>> language of JIRA (Java) is denoted as a positive. What is the basis
>> for this? Also, how is the language relevant for JIRA when the
>> application is proprietary and thus can't be modified anyway?
> In the context of choosing a system for OpenJDK, my assumption is
> that we as a group have more expertise in Java than in Perl. Even
> though the language should not matter, it would be definitely easier
> for us in OpenJDK to contribute extensions, plugins and
> modifications in Java for JIRA than in Perl for Bugzilla.
>> * Bugzilla is criticised for needing code modifications to achieve
>> some features, but was this necessary for JIRA, it would not be
>> possible. It's not ideal that required features aren't available as
>> is, but Bugzilla being FOSS means any required feature can be added.
>> This is not possible with JIRA and is a major pro in choosing Bugzilla
>> IMHO. What happens if JIRA is chosen and a feature is needed down the
>> line that is not available? What choices do we have to implement it,
>> given we can't modify the code?
> If we need new features down the line, we can try to persuade
> Atlassian to implement them. And, if we are not able to get them to
> do that, we can implement the features ourselves.
> Every licensee of JIRA gets access to the full source code. We can
> modify the code to develop bug fixes, customisations or additional
Who does "we" refer to here, though? Is the licensee of JIRA Oracle
More information about the discuss