You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henri Yandell <fl...@gmail.com> on 2006/04/17 07:20:53 UTC
[latka][all] Dormant Latka questions
In making Latka dormant, should we be doing anything about the 15
issues open for Latka in Bugzilla; and should we be doing anything
about the jakarta.apache.org/commons/latka/ website?
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [latka][all] Dormant Latka questions
Posted by Dion Gillard <di...@gmail.com>.
For a dormant component to have open bugs seems pretty reasonable to me.
On 4/18/06, Stephen Colebourne <sc...@btopenworld.com> wrote:
>
> The problem with this is that it counts against our open bug statistics.
> Or is that not a measure we care about?
>
> Stephen
>
>
> Dion Gillard wrote:
> > I'd prefer we didn't NOFIX any issues. Leaving them as NEW keeps their
> real
> > status and shows noone is yet working on things.
> >
> > On 4/18/06, Rahul Akolkar <ra...@gmail.com> wrote:
> >
> >>On 4/17/06, Henri Yandell <fl...@gmail.com> wrote:
> >>
> >>>In making Latka dormant, should we be doing anything about the 15
> >>>issues open for Latka in Bugzilla;
> >>
> >><snip/>
> >>
> >>Over in Taglibs, when it became clear that some weren't going to see
> >>any further development (soon), we WONTFIX'ed existing tickets -- a
> >>quick search got me these examples:
> >>
> >>http://issues.apache.org/bugzilla/show_bug.cgi?id=22587
> >>http://issues.apache.org/bugzilla/show_bug.cgi?id=22895
> >>
> >>Commons dormancy isn't quite the same, but maybe for the specific case
> >>of [latka] a similar approach is justified.
> >>
> >>
> >>
> >>>and should we be doing anything
> >>>about the jakarta.apache.org/commons/latka/ website?
> >>>
> >>
> >><snap/>
> >>
> >>I republished at the /sandbox/ URL, and meant to bring this up then.
> >>Maybe we should let it 404, unless someone -1s. In any case, the
> >>Commons website now points to the /sandbox/ URL.
> >>
> >>-Rahul
> >>
> >>
> >>
> >>>Hen
> >>>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >>
> >>
> >
> >
> >
> > --
> > http://www.multitask.com.au/people/dion/
> > Chuck Norris sleeps with a night light. Not because Chuck Norris is
> afraid
> > of the dark, but because the dark is afraid of Chuck Norris
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
--
http://www.multitask.com.au/people/dion/
Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid
of the dark, but because the dark is afraid of Chuck Norris
Re: [latka][all] Dormant Latka questions
Posted by Stephen Colebourne <sc...@btopenworld.com>.
The problem with this is that it counts against our open bug statistics.
Or is that not a measure we care about?
Stephen
Dion Gillard wrote:
> I'd prefer we didn't NOFIX any issues. Leaving them as NEW keeps their real
> status and shows noone is yet working on things.
>
> On 4/18/06, Rahul Akolkar <ra...@gmail.com> wrote:
>
>>On 4/17/06, Henri Yandell <fl...@gmail.com> wrote:
>>
>>>In making Latka dormant, should we be doing anything about the 15
>>>issues open for Latka in Bugzilla;
>>
>><snip/>
>>
>>Over in Taglibs, when it became clear that some weren't going to see
>>any further development (soon), we WONTFIX'ed existing tickets -- a
>>quick search got me these examples:
>>
>>http://issues.apache.org/bugzilla/show_bug.cgi?id=22587
>>http://issues.apache.org/bugzilla/show_bug.cgi?id=22895
>>
>>Commons dormancy isn't quite the same, but maybe for the specific case
>>of [latka] a similar approach is justified.
>>
>>
>>
>>>and should we be doing anything
>>>about the jakarta.apache.org/commons/latka/ website?
>>>
>>
>><snap/>
>>
>>I republished at the /sandbox/ URL, and meant to bring this up then.
>>Maybe we should let it 404, unless someone -1s. In any case, the
>>Commons website now points to the /sandbox/ URL.
>>
>>-Rahul
>>
>>
>>
>>>Hen
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>
>
>
> --
> http://www.multitask.com.au/people/dion/
> Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid
> of the dark, but because the dark is afraid of Chuck Norris
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [latka][all] Dormant Latka questions
Posted by Dion Gillard <di...@gmail.com>.
I'd prefer we didn't NOFIX any issues. Leaving them as NEW keeps their real
status and shows noone is yet working on things.
On 4/18/06, Rahul Akolkar <ra...@gmail.com> wrote:
>
> On 4/17/06, Henri Yandell <fl...@gmail.com> wrote:
> > In making Latka dormant, should we be doing anything about the 15
> > issues open for Latka in Bugzilla;
> <snip/>
>
> Over in Taglibs, when it became clear that some weren't going to see
> any further development (soon), we WONTFIX'ed existing tickets -- a
> quick search got me these examples:
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=22587
> http://issues.apache.org/bugzilla/show_bug.cgi?id=22895
>
> Commons dormancy isn't quite the same, but maybe for the specific case
> of [latka] a similar approach is justified.
>
>
> > and should we be doing anything
> > about the jakarta.apache.org/commons/latka/ website?
> >
> <snap/>
>
> I republished at the /sandbox/ URL, and meant to bring this up then.
> Maybe we should let it 404, unless someone -1s. In any case, the
> Commons website now points to the /sandbox/ URL.
>
> -Rahul
>
>
> > Hen
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
--
http://www.multitask.com.au/people/dion/
Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid
of the dark, but because the dark is afraid of Chuck Norris
Re: [latka][all] Dormant Latka questions
Posted by Henri Yandell <fl...@gmail.com>.
On 4/17/06, Rahul Akolkar <ra...@gmail.com> wrote:
> On 4/17/06, Henri Yandell <fl...@gmail.com> wrote:
> > and should we be doing anything
> > about the jakarta.apache.org/commons/latka/ website?
> >
> <snap/>
>
> I republished at the /sandbox/ URL, and meant to bring this up then.
> Maybe we should let it 404, unless someone -1s. In any case, the
> Commons website now points to the /sandbox/ URL.
Should go ahead and setup a redirect in the jakarta/site .htaccess.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [latka][all] Dormant Latka questions
Posted by Rahul Akolkar <ra...@gmail.com>.
On 4/17/06, Henri Yandell <fl...@gmail.com> wrote:
> In making Latka dormant, should we be doing anything about the 15
> issues open for Latka in Bugzilla;
<snip/>
Over in Taglibs, when it became clear that some weren't going to see
any further development (soon), we WONTFIX'ed existing tickets -- a
quick search got me these examples:
http://issues.apache.org/bugzilla/show_bug.cgi?id=22587
http://issues.apache.org/bugzilla/show_bug.cgi?id=22895
Commons dormancy isn't quite the same, but maybe for the specific case
of [latka] a similar approach is justified.
> and should we be doing anything
> about the jakarta.apache.org/commons/latka/ website?
>
<snap/>
I republished at the /sandbox/ URL, and meant to bring this up then.
Maybe we should let it 404, unless someone -1s. In any case, the
Commons website now points to the /sandbox/ URL.
-Rahul
> Hen
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org