who should use bugzilla ?

[phil.race]

Hello Brad and Mark,

As you can see from the email below, there's something of
an apparent hole in the description of who should use bugzilla.

Can we clarify what's supposed to be the process

Specifically if you are external to Sun. but  have an openjdk user id
either because you are a member of an openjdk group (eg 2d, awt), OR
because you have an openjdk project, then should you in fact use
bugzilla, since you can't use the Sun internal bugster tool ?


-phil.

-------- Original Message --------


Roman Kennke wrote:

>>
>> For the cases where where you have a proposed fix, then use bugzilla, for
>> the ones you don't submitting each of those tests as a bug report into bugs.sun.com
>> is the right thing to do at the moment.
>
> Ok. The announcement also says 'contributions from those developers
> without push permissions'. This is interesting, as it excludes people
> like me, who have push access, but I cannot really make use of
> bugs.sun.com either. So I will continue to send emails instead.

I think the intent is that patches should NOT be sent in email,
as bugzilla is now available to track those patches so that they
don't get lost in the email and its easier to see where we are WRT
to integrating contributions.

So you should use bugzilla for submitting patches, even if you
ultimately push them. Patches already in process likely don't
need to be retrospectively added to bugzilla unless you want to
do that.

-phil.

[martinrb]

On Tue, Mar 3, 2009 at 13:43, Phil Race <Phil.Race@...> wrote:
> Hello Brad and Mark,

> Specifically if you are external to Sun. but  have an openjdk user id
> either because you are a member of an openjdk group (eg 2d, awt), OR
> because you have an openjdk project, then should you in fact use
> bugzilla, since you can't use the Sun internal bugster tool ?

I am waiting for an announcement that would allow me to do my first
commit entirely without Sun engineer help.

Martin

[Mark Reinhold]

> Date: Tue, 03 Mar 2009 13:43:15 -0800
> From: phil.race@...

> As you can see from the email below, there's something of
> an apparent hole in the description of who should use bugzilla.
>
> Can we clarify what's supposed to be the process
>
> Specifically if you are external to Sun. but  have an openjdk user id
> either because you are a member of an openjdk group (eg 2d, awt), OR
> because you have an openjdk project, then should you in fact use
> bugzilla, since you can't use the Sun internal bugster tool ?

In the long run, people such as Roman who have push rights into the JDK 6
and 7 forests -- and in his case have in fact already pushed changes to
at least one of those forests, after appropriate review -- should not
need to use a special process set up primarily for people who haven't yet
earned such rights.

Having said that, Roman is completely right to point out that he can't
make effective use of bugs.sun.com on his own.  There are, moreover,
other internal tools, e.g., the code-review robot, that aren't (yet)
available to external developers.

Until such time as more of our internal tools are externalized, and we
use our Bugzilla for all bugs rather than just for contributions from
non-Sun developers, I see no harm in using Bugzilla to track changes
being proposed by such developers even if they do have push rights into
the appropriate forests.

If there's general agreement on this then I'll arrange for the warning
header on bugs.openjdk.java.net to be modified accordingly.

- Mark

[Ulf Zibis-2]

Hi all,

I also think, that existing tools for externals are very poor, compared
e.g. with NetBeans project.

Especially on the bug parade I'm missing:
- sophisticated search tools
- saving search profiles
- reopening bugs from external
- attaching resources
- customising the watch list, e.g. displaying the summary in the list
(today only id's are displayed, and you have to open all links, to see
what's inside)

-Ulf


Am 05.03.2009 05:42, Mark Reinhold schrieb:

>> Date: Tue, 03 Mar 2009 13:43:15 -0800
>> From: phil.race@...
>>    
>
>  
>> As you can see from the email below, there's something of
>> an apparent hole in the description of who should use bugzilla.
>>
>> Can we clarify what's supposed to be the process
>>
>> Specifically if you are external to Sun. but  have an openjdk user id
>> either because you are a member of an openjdk group (eg 2d, awt), OR
>> because you have an openjdk project, then should you in fact use
>> bugzilla, since you can't use the Sun internal bugster tool ?
>>    
>
> In the long run, people such as Roman who have push rights into the JDK 6
> and 7 forests -- and in his case have in fact already pushed changes to
> at least one of those forests, after appropriate review -- should not
> need to use a special process set up primarily for people who haven't yet
> earned such rights.
>
> Having said that, Roman is completely right to point out that he can't
> make effective use of bugs.sun.com on his own.  There are, moreover,
> other internal tools, e.g., the code-review robot, that aren't (yet)
> available to external developers.
>
> Until such time as more of our internal tools are externalized, and we
> use our Bugzilla for all bugs rather than just for contributions from
> non-Sun developers, I see no harm in using Bugzilla to track changes
> being proposed by such developers even if they do have push rights into
> the appropriate forests.
>
> If there's general agreement on this then I'll arrange for the warning
> header on bugs.openjdk.java.net to be modified accordingly.
>
> - Mark
>
>
>  

[Brad Wetmore]

 From a discussion in early March.

Mark Reinhold wrote:
 > Until such time as more of our internal tools are externalized, and we
 > use our Bugzilla for all bugs rather than just for contributions from
 > non-Sun developers, I see no harm in using Bugzilla to track changes
 > being proposed by such developers even if they do have push rights into
 > the appropriate forests.
 >
 > If there's general agreement on this then I'll arrange for the warning
 > header on bugs.openjdk.java.net to be modified accordingly.

I agree with the "no harm" sentiment.  The original intent was for
developers without push rights, but see no reason to restrict it to only
those without push rights.

Since there was no further discussion, I'll assume this is ok, and have
updated the text accordingly.

Brad

P.S.  Mark's full response follows:

Mark Reinhold wrote:

>> Date: Tue, 03 Mar 2009 13:43:15 -0800
>> From: phil.race@...
>
>> As you can see from the email below, there's something of
>> an apparent hole in the description of who should use bugzilla.
>>
>> Can we clarify what's supposed to be the process
>>
>> Specifically if you are external to Sun. but  have an openjdk user id
>> either because you are a member of an openjdk group (eg 2d, awt), OR
>> because you have an openjdk project, then should you in fact use
>> bugzilla, since you can't use the Sun internal bugster tool ?
>
> In the long run, people such as Roman who have push rights into the JDK 6
> and 7 forests -- and in his case have in fact already pushed changes to
> at least one of those forests, after appropriate review -- should not
> need to use a special process set up primarily for people who haven't yet
> earned such rights.
>
> Having said that, Roman is completely right to point out that he can't
> make effective use of bugs.sun.com on his own.  There are, moreover,
> other internal tools, e.g., the code-review robot, that aren't (yet)
> available to external developers.
>
> Until such time as more of our internal tools are externalized, and we
> use our Bugzilla for all bugs rather than just for contributions from
> non-Sun developers, I see no harm in using Bugzilla to track changes
> being proposed by such developers even if they do have push rights into
> the appropriate forests.
>
> If there's general agreement on this then I'll arrange for the warning
> header on bugs.openjdk.java.net to be modified accordingly.
>
> - Mark

[Ulf Zibis-2]

I'm talking about bugs.sun.com, as I remember right, it was even
officially named "bug parade" in former times. I often got messages like
this:

We have determined that this report is a new bug and entered the bug into our
internal bug tracking system under Bug Id: 4894530.

You can monitor this bug and look for related issues on The Java Developer
Connection Bug Parade at:
http://developer.java.sun.com/developer/bugParade/bugs/4894530.html


-Ulf


Am 01.05.2009 03:41, Brad Wetmore schrieb:

> For the "bug parade", were you talking about the bugs.sun.com "bug
> parade" or the openjdk.java.net Bugzilla instance?
>
> Brad
>
>
> Ulf Zibis wrote:
>> Hi all,
>>
>> I also think, that existing tools for externals are very poor,
>> compared e.g. with NetBeans project.
>>
>> Especially on the bug parade I'm missing:
>> - sophisticated search tools
>> - saving search profiles
>> - reopening bugs from external
>> - attaching resources
>> - customising the watch list, e.g. displaying the summary in the list
>> (today only id's are displayed, and you have to open all links, to
>> see what's inside)
>>
>> -Ulf
>>
>>
>> Am 05.03.2009 05:42, Mark Reinhold schrieb:
>>>> Date: Tue, 03 Mar 2009 13:43:15 -0800
>>>> From: phil.race@...
>>>>    
>>>
>>>  
>>>> As you can see from the email below, there's something of
>>>> an apparent hole in the description of who should use bugzilla.
>>>>
>>>> Can we clarify what's supposed to be the process
>>>>
>>>> Specifically if you are external to Sun. but  have an openjdk user id
>>>> either because you are a member of an openjdk group (eg 2d, awt), OR
>>>> because you have an openjdk project, then should you in fact use
>>>> bugzilla, since you can't use the Sun internal bugster tool ?
>>>>    
>>>
>>> In the long run, people such as Roman who have push rights into the
>>> JDK 6
>>> and 7 forests -- and in his case have in fact already pushed changes to
>>> at least one of those forests, after appropriate review -- should not
>>> need to use a special process set up primarily for people who
>>> haven't yet
>>> earned such rights.
>>>
>>> Having said that, Roman is completely right to point out that he can't
>>> make effective use of bugs.sun.com on his own.  There are, moreover,
>>> other internal tools, e.g., the code-review robot, that aren't (yet)
>>> available to external developers.
>>>
>>> Until such time as more of our internal tools are externalized, and we
>>> use our Bugzilla for all bugs rather than just for contributions from
>>> non-Sun developers, I see no harm in using Bugzilla to track changes
>>> being proposed by such developers even if they do have push rights into
>>> the appropriate forests.
>>>
>>> If there's general agreement on this then I'll arrange for the warning
>>> header on bugs.openjdk.java.net to be modified accordingly.
>>>
>>> - Mark
>>>
>>>
>>>  
>>
>
>

[Brad Wetmore]

 > it was even
 > officially named "bug parade" in former times.

I was just checking to make sure it wasn't getting confused with
Bugzilla.  I am working on the Bugzilla piece, but have no control over
bugs.sun.com.

 >>> Especially on the bug parade I'm missing:
 >>> - sophisticated search tools
 >>> - saving search profiles
 >>> - reopening bugs from external
 >>> - attaching resources
 >>> - customising the watch list, e.g. displaying the summary in the list
 >>> (today only id's are displayed, and you have to open all links, to
 >>> see what's inside)

I agree with you!

Brad


Ulf Zibis wrote:

> I'm talking about bugs.sun.com, as I remember right, it was even
> officially named "bug parade" in former times. I often got messages like
> this:
>
> We have determined that this report is a new bug and entered the bug
> into our
> internal bug tracking system under Bug Id: 4894530.
>
> You can monitor this bug and look for related issues on The Java Developer
> Connection Bug Parade at:
> http://developer.java.sun.com/developer/bugParade/bugs/4894530.html
>
>
> -Ulf
>
>
> Am 01.05.2009 03:41, Brad Wetmore schrieb:
>> For the "bug parade", were you talking about the bugs.sun.com "bug
>> parade" or the openjdk.java.net Bugzilla instance?
>>
>> Brad
>>
>>
>> Ulf Zibis wrote:
>>> Hi all,
>>>
>>> I also think, that existing tools for externals are very poor,
>>> compared e.g. with NetBeans project.
>>>
>>> Especially on the bug parade I'm missing:
>>> - sophisticated search tools
>>> - saving search profiles
>>> - reopening bugs from external
>>> - attaching resources
>>> - customising the watch list, e.g. displaying the summary in the list
>>> (today only id's are displayed, and you have to open all links, to
>>> see what's inside)
>>>
>>> -Ulf
>>>
>>>
>>> Am 05.03.2009 05:42, Mark Reinhold schrieb:
>>>>> Date: Tue, 03 Mar 2009 13:43:15 -0800
>>>>> From: phil.race@...
>>>>>    
>>>>
>>>>  
>>>>> As you can see from the email below, there's something of
>>>>> an apparent hole in the description of who should use bugzilla.
>>>>>
>>>>> Can we clarify what's supposed to be the process
>>>>>
>>>>> Specifically if you are external to Sun. but  have an openjdk user id
>>>>> either because you are a member of an openjdk group (eg 2d, awt), OR
>>>>> because you have an openjdk project, then should you in fact use
>>>>> bugzilla, since you can't use the Sun internal bugster tool ?
>>>>>    
>>>>
>>>> In the long run, people such as Roman who have push rights into the
>>>> JDK 6
>>>> and 7 forests -- and in his case have in fact already pushed changes to
>>>> at least one of those forests, after appropriate review -- should not
>>>> need to use a special process set up primarily for people who
>>>> haven't yet
>>>> earned such rights.
>>>>
>>>> Having said that, Roman is completely right to point out that he can't
>>>> make effective use of bugs.sun.com on his own.  There are, moreover,
>>>> other internal tools, e.g., the code-review robot, that aren't (yet)
>>>> available to external developers.
>>>>
>>>> Until such time as more of our internal tools are externalized, and we
>>>> use our Bugzilla for all bugs rather than just for contributions from
>>>> non-Sun developers, I see no harm in using Bugzilla to track changes
>>>> being proposed by such developers even if they do have push rights into
>>>> the appropriate forests.
>>>>
>>>> If there's general agreement on this then I'll arrange for the warning
>>>> header on bugs.openjdk.java.net to be modified accordingly.
>>>>
>>>> - Mark
>>>>
>>>>
>>>>  
>>>
>>
>>
>