You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2013/07/25 23:06:22 UTC
Closing out lots of bugs
I've been taking some time the last couple of days to work through the huge
issue backlog for Tapestry.
I've been fixing some low-hanging fruit. I've been assigning many issues to
myself for later.
I've also been closing out a lot of issues. Some of them are things that
are fixed (or at least, very probably fixed) in 5.4. Many are duplicates,
which can be tedious to sort out.
Some issues are concerned with client-side JavaScript in 5.3 that no longer
make sense in 5.4. At this time I'm closing those issues with a note to
that effect. The assumption there is that we are not going to be doing
another 5.3 release, or at least, that we would only fix critical bugs in a
potential 5.3 release; this is not the result of a developer discussion,
merely my assessment of the issues and that status of the other committers.
If you *really* want something fixed, a patch with tests is the best way to
make that happen.
In any case, a closed issue is not the end of the line; issues can always
be re-opened if there is a valid case to be made. Again, a case is more
valid if it includes a test case to demonstrate the problem and, better
yet, a patch with tests.
However, with a backlog of 450+ issues to be addressed, getting the list
down to a manageable state is a precursor to getting 5.4 to a beta release.
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: Closing out lots of bugs
Posted by Muhammad Gelbana <m....@gmail.com>.
I saw the blogpost:
http://tapestryjava.blogspot.com/2013/07/tapestry-54-avalanche-of-fixed-issues.html
VERY exciting !
So how will the documentation will adapt to such a big and fundamental
change between 5.3 and 5.4 ?
On Thu, Jul 25, 2013 at 11:12 PM, Kalle Korhonen <kalle.o.korhonen@gmail.com
> wrote:
> +1, I fully support this assessment and way or working.
>
> Kalle
>
>
> On Thu, Jul 25, 2013 at 2:06 PM, Howard Lewis Ship <hl...@gmail.com>
> wrote:
>
> > I've been taking some time the last couple of days to work through the
> huge
> > issue backlog for Tapestry.
> >
> > I've been fixing some low-hanging fruit. I've been assigning many issues
> to
> > myself for later.
> >
> > I've also been closing out a lot of issues. Some of them are things that
> > are fixed (or at least, very probably fixed) in 5.4. Many are
> duplicates,
> > which can be tedious to sort out.
> >
> > Some issues are concerned with client-side JavaScript in 5.3 that no
> longer
> > make sense in 5.4. At this time I'm closing those issues with a note to
> > that effect. The assumption there is that we are not going to be doing
> > another 5.3 release, or at least, that we would only fix critical bugs
> in a
> > potential 5.3 release; this is not the result of a developer discussion,
> > merely my assessment of the issues and that status of the other
> committers.
> >
> > If you *really* want something fixed, a patch with tests is the best way
> to
> > make that happen.
> >
> > In any case, a closed issue is not the end of the line; issues can always
> > be re-opened if there is a valid case to be made. Again, a case is more
> > valid if it includes a test case to demonstrate the problem and, better
> > yet, a patch with tests.
> >
> > However, with a backlog of 450+ issues to be addressed, getting the list
> > down to a manageable state is a precursor to getting 5.4 to a beta
> release.
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator of Apache Tapestry
> >
> > The source for Tapestry training, mentoring and support. Contact me to
> > learn how I can get you up and productive in Tapestry fast!
> >
> > (971) 678-5210
> > http://howardlewisship.com
> >
>
Re: Closing out lots of bugs
Posted by Muhammad Gelbana <m....@gmail.com>.
I saw the blogpost:
http://tapestryjava.blogspot.com/2013/07/tapestry-54-avalanche-of-fixed-issues.html
VERY exciting !
So how will the documentation will adapt to such a big and fundamental
change between 5.3 and 5.4 ?
On Thu, Jul 25, 2013 at 11:12 PM, Kalle Korhonen <kalle.o.korhonen@gmail.com
> wrote:
> +1, I fully support this assessment and way or working.
>
> Kalle
>
>
> On Thu, Jul 25, 2013 at 2:06 PM, Howard Lewis Ship <hl...@gmail.com>
> wrote:
>
> > I've been taking some time the last couple of days to work through the
> huge
> > issue backlog for Tapestry.
> >
> > I've been fixing some low-hanging fruit. I've been assigning many issues
> to
> > myself for later.
> >
> > I've also been closing out a lot of issues. Some of them are things that
> > are fixed (or at least, very probably fixed) in 5.4. Many are
> duplicates,
> > which can be tedious to sort out.
> >
> > Some issues are concerned with client-side JavaScript in 5.3 that no
> longer
> > make sense in 5.4. At this time I'm closing those issues with a note to
> > that effect. The assumption there is that we are not going to be doing
> > another 5.3 release, or at least, that we would only fix critical bugs
> in a
> > potential 5.3 release; this is not the result of a developer discussion,
> > merely my assessment of the issues and that status of the other
> committers.
> >
> > If you *really* want something fixed, a patch with tests is the best way
> to
> > make that happen.
> >
> > In any case, a closed issue is not the end of the line; issues can always
> > be re-opened if there is a valid case to be made. Again, a case is more
> > valid if it includes a test case to demonstrate the problem and, better
> > yet, a patch with tests.
> >
> > However, with a backlog of 450+ issues to be addressed, getting the list
> > down to a manageable state is a precursor to getting 5.4 to a beta
> release.
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator of Apache Tapestry
> >
> > The source for Tapestry training, mentoring and support. Contact me to
> > learn how I can get you up and productive in Tapestry fast!
> >
> > (971) 678-5210
> > http://howardlewisship.com
> >
>
Re: Closing out lots of bugs
Posted by Kalle Korhonen <ka...@gmail.com>.
+1, I fully support this assessment and way or working.
Kalle
On Thu, Jul 25, 2013 at 2:06 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> I've been taking some time the last couple of days to work through the huge
> issue backlog for Tapestry.
>
> I've been fixing some low-hanging fruit. I've been assigning many issues to
> myself for later.
>
> I've also been closing out a lot of issues. Some of them are things that
> are fixed (or at least, very probably fixed) in 5.4. Many are duplicates,
> which can be tedious to sort out.
>
> Some issues are concerned with client-side JavaScript in 5.3 that no longer
> make sense in 5.4. At this time I'm closing those issues with a note to
> that effect. The assumption there is that we are not going to be doing
> another 5.3 release, or at least, that we would only fix critical bugs in a
> potential 5.3 release; this is not the result of a developer discussion,
> merely my assessment of the issues and that status of the other committers.
>
> If you *really* want something fixed, a patch with tests is the best way to
> make that happen.
>
> In any case, a closed issue is not the end of the line; issues can always
> be re-opened if there is a valid case to be made. Again, a case is more
> valid if it includes a test case to demonstrate the problem and, better
> yet, a patch with tests.
>
> However, with a backlog of 450+ issues to be addressed, getting the list
> down to a manageable state is a precursor to getting 5.4 to a beta release.
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
Re: Closing out lots of bugs
Posted by Kalle Korhonen <ka...@gmail.com>.
+1, I fully support this assessment and way or working.
Kalle
On Thu, Jul 25, 2013 at 2:06 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> I've been taking some time the last couple of days to work through the huge
> issue backlog for Tapestry.
>
> I've been fixing some low-hanging fruit. I've been assigning many issues to
> myself for later.
>
> I've also been closing out a lot of issues. Some of them are things that
> are fixed (or at least, very probably fixed) in 5.4. Many are duplicates,
> which can be tedious to sort out.
>
> Some issues are concerned with client-side JavaScript in 5.3 that no longer
> make sense in 5.4. At this time I'm closing those issues with a note to
> that effect. The assumption there is that we are not going to be doing
> another 5.3 release, or at least, that we would only fix critical bugs in a
> potential 5.3 release; this is not the result of a developer discussion,
> merely my assessment of the issues and that status of the other committers.
>
> If you *really* want something fixed, a patch with tests is the best way to
> make that happen.
>
> In any case, a closed issue is not the end of the line; issues can always
> be re-opened if there is a valid case to be made. Again, a case is more
> valid if it includes a test case to demonstrate the problem and, better
> yet, a patch with tests.
>
> However, with a backlog of 450+ issues to be addressed, getting the list
> down to a manageable state is a precursor to getting 5.4 to a beta release.
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
Re: Closing out lots of bugs
Posted by Ulrich Stärk <ul...@spielviel.de>.
Some time ago I marked a lot of issues as bulk-close-candidate. Filtering for those could help as
they are likely candidates for closing (old, not recently updated, affecting outdated versions, etc.).
Uli
On 25.07.2013 23:06, Howard Lewis Ship wrote:
> I've been taking some time the last couple of days to work through the huge
> issue backlog for Tapestry.
>
> I've been fixing some low-hanging fruit. I've been assigning many issues to
> myself for later.
>
> I've also been closing out a lot of issues. Some of them are things that
> are fixed (or at least, very probably fixed) in 5.4. Many are duplicates,
> which can be tedious to sort out.
>
> Some issues are concerned with client-side JavaScript in 5.3 that no longer
> make sense in 5.4. At this time I'm closing those issues with a note to
> that effect. The assumption there is that we are not going to be doing
> another 5.3 release, or at least, that we would only fix critical bugs in a
> potential 5.3 release; this is not the result of a developer discussion,
> merely my assessment of the issues and that status of the other committers.
>
> If you *really* want something fixed, a patch with tests is the best way to
> make that happen.
>
> In any case, a closed issue is not the end of the line; issues can always
> be re-opened if there is a valid case to be made. Again, a case is more
> valid if it includes a test case to demonstrate the problem and, better
> yet, a patch with tests.
>
> However, with a backlog of 450+ issues to be addressed, getting the list
> down to a manageable state is a precursor to getting 5.4 to a beta release.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org