You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by Felipe Leme <ja...@felipeal.net> on 2004/06/06 20:02:43 UTC
[PROPOSAL] Changes on bugzilla
Hello,
I'd like to propose some changes on bugzilla:
1.Add support to sandbox taglibs
[ ] +1 Add sandbox taglibs in the Components field
[ ] -1 Do not add sandbox taglibs in the Components field, explain why
2.Update versions available. We could remove the 1.0B1 and EA1 and add
1.0.3, 1.0.4, 1.0.5, 1.1.0, 1.2.0 and nightly
[ ] +1 Update Version field
[ ] -1 Do not update Version field, explain why
Regards,
Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: [PROPOSAL] Changes on bugzilla
Posted by Glenn Nielsen <gl...@mail.more.net>.
On Sun, Jun 06, 2004 at 03:02:43PM -0300, Felipe Leme wrote:
> Hello,
>
> I'd like to propose some changes on bugzilla:
>
> 1.Add support to sandbox taglibs
>
> [ ] +1 Add sandbox taglibs in the Components field
> [X] -1 Do not add sandbox taglibs in the Components field, explain why
The sandbox is just that, a place for exploring taglib ideas.
A sandbox taglib can be added to Bugzilla when it has been voted
out of the sandbox.
> 2.Update versions available. We could remove the 1.0B1 and EA1 and add
> 1.0.3, 1.0.4, 1.0.5, 1.1.0, 1.2.0 and nightly
>
> [X] +1 Update Version field
> [ ] -1 Do not update Version field, explain why
I think my bugzilla account has permission to do these things.
Regards,
Glenn
----------------------------------------------------------------------
Glenn Nielsen glenn@more.net | /* Spelin donut madder |
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
----------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: [PROPOSAL] Changes on bugzilla (UPDATED)
Posted by Kris Schneider <kr...@dotech.com>.
Felipe Leme wrote:
> On Tue, 2004-06-08 at 11:31, Kris Schneider wrote:
>
>>Just for clarification, are we talking about a single entry that covers all the
>>sandbox projects or an entry for each project in the sandbox?
>
>
> Originally I proposed one entry for each project. But it could be only
> one for all of them too. So, here is the new proposal:
>
> 1.Add bugzilla support to sandbox taglibs
>
> [ ] +1 Add one entry for each sandbox taglib in the Components field
> [X] +1 Add only one entry for all sandbox taglibs in the Components field
> [ ] -1 Do not add bugzilla support for sandbox taglibs, explain why
>
> (my vote is for the first options; I'd like that Glenn and Justyna voted again)
>
> 2.Update versions available. We could remove the 1.0B1 and EA1 and add
> [X] +1 Update Version field
> [ ] -1 Do not update Version field, explain why
>
> (my vote is for the first option again)
>
> Felipe
--
Kris Schneider <ma...@dotech.com>
D.O.Tech <http://www.dotech.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: [PROPOSAL] Changes on bugzilla (UPDATED)
Posted by Glenn Nielsen <gl...@mail.more.net>.
On Tue, Jun 08, 2004 at 07:40:19PM -0300, Felipe Leme wrote:
> On Tue, 2004-06-08 at 11:31, Kris Schneider wrote:
> > Just for clarification, are we talking about a single entry that covers all the
> > sandbox projects or an entry for each project in the sandbox?
>
> Originally I proposed one entry for each project. But it could be only
> one for all of them too. So, here is the new proposal:
>
> 1.Add bugzilla support to sandbox taglibs
>
> [ ] +1 Add one entry for each sandbox taglib in the Components field
> [X] +1 Add only one entry for all sandbox taglibs in the Components field
> [ ] -1 Do not add bugzilla support for sandbox taglibs, explain why
>
> (my vote is for the first options; I'd like that Glenn and Justyna voted again)
>
> 2.Update versions available. We could remove the 1.0B1 and EA1 and add
> [X] +1 Update Version field
> [ ] -1 Do not update Version field, explain why
>
> (my vote is for the first option again)
Glenn
----------------------------------------------------------------------
Glenn Nielsen glenn@more.net | /* Spelin donut madder |
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
----------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: [PROPOSAL] Changes on bugzilla (UPDATED)
Posted by Justyna Horwat <Ju...@Sun.COM>.
Felipe Leme wrote:
> On Tue, 2004-06-08 at 11:31, Kris Schneider wrote:
> 1.Add bugzilla support to sandbox taglibs
>
> [ ] +1 Add one entry for each sandbox taglib in the Components field
> [X] +1 Add only one entry for all sandbox taglibs in the Components field
> [ ] -1 Do not add bugzilla support for sandbox taglibs, explain why
I believe that until Sandbox projects are voted out of the sandbox and
fully supported they should not have their own entry in the components
field.
It should be clear to users that Sandbox projects are not yet officially
supported. If it gets to the point that a Sandbox project needs its own
entry in the components field I believe that it should also be
considered as a fully supported taglibs project.
> 2.Update versions available. We could remove the 1.0B1 and EA1 and add
> [X] +1 Update Version field
> [ ] -1 Do not update Version field, explain why
Thanks,
Justyna
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
[PROPOSAL] Changes on bugzilla (UPDATED)
Posted by Felipe Leme <ja...@felipeal.net>.
On Tue, 2004-06-08 at 11:31, Kris Schneider wrote:
> Just for clarification, are we talking about a single entry that covers all the
> sandbox projects or an entry for each project in the sandbox?
Originally I proposed one entry for each project. But it could be only
one for all of them too. So, here is the new proposal:
1.Add bugzilla support to sandbox taglibs
[ ] +1 Add one entry for each sandbox taglib in the Components field
[ ] +1 Add only one entry for all sandbox taglibs in the Components field
[ ] -1 Do not add bugzilla support for sandbox taglibs, explain why
(my vote is for the first options; I'd like that Glenn and Justyna voted again)
2.Update versions available. We could remove the 1.0B1 and EA1 and add
[ ] +1 Update Version field
[ ] -1 Do not update Version field, explain why
(my vote is for the first option again)
Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: [PROPOSAL] Changes on bugzilla
Posted by Kris Schneider <kr...@dotech.com>.
Just for clarification, are we talking about a single entry that covers all the
sandbox projects or an entry for each project in the sandbox?
Quoting Felipe Leme <ja...@felipeal.net>:
> I agree with Justyna - just because a taglib is on the sandbox doesn't
> means it doesn't 'deserve' an entry on bugzilla. In fact, a bug account
> would be a good indicator of a taglib popularity and its maturity to
> leave the sandbox (take for instance Image: it received a lot of
> comments in the list that resulted in code changes - these activities
> would be better suited at bugzilla).
>
> On Mon, 2004-06-07 at 13:42, Justyna Horwat wrote:
>
> > I think a "Sandbox" component field would be helpful for a component
> > that is still under the evaluation phase and not ready to be voted out
> > of the sandbox.
--
Kris Schneider <ma...@dotech.com>
D.O.Tech <http://www.dotech.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: [PROPOSAL] Changes on bugzilla
Posted by Felipe Leme <ja...@felipeal.net>.
I agree with Justyna - just because a taglib is on the sandbox doesn't
means it doesn't 'deserve' an entry on bugzilla. In fact, a bug account
would be a good indicator of a taglib popularity and its maturity to
leave the sandbox (take for instance Image: it received a lot of
comments in the list that resulted in code changes - these activities
would be better suited at bugzilla).
On Mon, 2004-06-07 at 13:42, Justyna Horwat wrote:
> I think a "Sandbox" component field would be helpful for a component
> that is still under the evaluation phase and not ready to be voted out
> of the sandbox.
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: [PROPOSAL] Changes on bugzilla
Posted by Justyna Horwat <Ju...@sun.com>.
Felipe Leme wrote:
> Hello,
>
> I'd like to propose some changes on bugzilla:
>
> 1.Add support to sandbox taglibs
>
> [X] +1 Add sandbox taglibs in the Components field
> [ ] -1 Do not add sandbox taglibs in the Components field, explain why
I looked at how the Jakarta Commons is set up with the Sandbox projects.
They do have a general "Sandbox" component field as well as an
"unspecified" version field.
Looking at our SandBox projects, yes they are not officially supported
however they still can be tested and evaluated. If someone comes across
a problem with a Sandbox component, they currently have no way of
tracking it.
I think a "Sandbox" component field would be helpful for a component
that is still under the evaluation phase and not ready to be voted out
of the sandbox.
> 2.Update versions available. We could remove the 1.0B1 and EA1 and add
> 1.0.3, 1.0.4, 1.0.5, 1.1.0, 1.2.0 and nightly
>
> [X] +1 Update Version field
> [ ] -1 Do not update Version field, explain why
Thanks,
Justyna
> Regards,
>
> Felipe
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org