You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Brian K. Wallace" <br...@transmorphix.com> on 2006/03/04 21:23:06 UTC
Jira
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Would it be possible for someone with proper permissions to go through
Jira and close issues that are no longer applicable? I find it either a)
impossible to believe or b) extremely problematic if all the issues
dating back to mid 2004 are still relevant.
Having so many issues open, very few actually assigned to a release, and
some with patches attached but still "open" makes following the "pick an
issue and submit a patch" methodology somewhat... difficult.
Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFECfcqaCoPKRow/gARAnqIAJ9TN/6z1ZupCJrNCxcvwJ423u4CZQCgmP0U
tkzqGYhQz6RycdSeN17Oq3U=
=PSxH
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Jira
Posted by Leonardo Quijano Vincenzi <le...@dtqsoftware.com>.
Of course, the real solution would be to actually use the version
timestamps that JIRA provide... I mean... if I were a committer I would
grab each and every one of these 269 "Unscheduled" issues and actually
put them on the right version. Then somebody can mark them as "LATER" or
move them to another project or whatever, or just leave them open
without them cluttering the rest of Tapestry versions.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Jesse Kuhnert wrote:
> Can't we just close anything <= 3.0 ;) I know I know..of course I'm only
> kidding. It's such an impossible task.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Jira
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ahh for things to be that easy... ;-)
I can definitely agree that it's not going to be a piece of cake - even
if they all said "no longer applicable" in the description it'd take
some doing to get them all handled. One at a time and before you know it
- - there's one more done. :-) ["done" being relative: closed, dupe, patch
applied, etc...]
(at the very least... there are 8 still assigned to the 4.0 release.
hmmm...)
Jesse Kuhnert wrote:
> Can't we just close anything <= 3.0 ;) I know I know..of course I'm only
> kidding. It's such an impossible task.
>
> On 3/4/06, Brian K. Wallace <br...@transmorphix.com> wrote:
> Would it be possible for someone with proper permissions to go through
> Jira and close issues that are no longer applicable? I find it either a)
> impossible to believe or b) extremely problematic if all the issues
> dating back to mid 2004 are still relevant.
>
> Having so many issues open, very few actually assigned to a release, and
> some with patches attached but still "open" makes following the "pick an
> issue and submit a patch" methodology somewhat... difficult.
>
> Brian
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEC80qaCoPKRow/gARApqlAJ0cV7iApNFHGS9IlYw9UPayjxBdQwCfYnHa
B55Ap87pEnZOt2Ulw7FLV2M=
=99zw
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Jira
Posted by Jesse Kuhnert <jk...@gmail.com>.
Can't we just close anything <= 3.0 ;) I know I know..of course I'm only
kidding. It's such an impossible task.
On 3/4/06, Brian K. Wallace <br...@transmorphix.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Would it be possible for someone with proper permissions to go through
> Jira and close issues that are no longer applicable? I find it either a)
> impossible to believe or b) extremely problematic if all the issues
> dating back to mid 2004 are still relevant.
>
> Having so many issues open, very few actually assigned to a release, and
> some with patches attached but still "open" makes following the "pick an
> issue and submit a patch" methodology somewhat... difficult.
>
> Brian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
>
> iD8DBQFECfcqaCoPKRow/gARAnqIAJ9TN/6z1ZupCJrNCxcvwJ423u4CZQCgmP0U
> tkzqGYhQz6RycdSeN17Oq3U=
> =PSxH
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>