+1, I fully support this assessment and way or working. Kalle
On Thu, Jul 25, 2013 at 2:06 PM, Howard Lewis Ship <hls...@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 >
