Although it's the best for the community as a whole that a defect doesn't last long unresolved, but the committers may not always have the chance to fix them.
A trivial defect in tapestry-jquery hasn't been even replied too although reported 2 days ago <https://github.com/got5/tapestry5-jquery/issues/230> and on the google group, the post disclosing the matter<https://groups.google.com/forum/?hl=en#!topic/tapestry5-jquery/owgJzegUI4g>was viewed 3 times only at the time of writing this ! Some other times defects are just too noisy to be fixed<https://issues.apache.org/jira/browse/TAP5-1948> and would have a MAJOR impact on backward compatibly so it'll have to be done on a major release such as Tapestry 6 :) And no one is getting paid to do it. May be in an indirect way such as using the framework but not directly so they *have to* to solve defects. May be when a committer faces a reported issue, that could be another story :D On Mon, Sep 3, 2012 at 11:52 PM, Sigbjørn Tvedt <sigbjo...@gmail.com> wrote: > Hi > > I guess the contributers are looking for issues that has a title the know > they are able to fix, or issues with attachments so that they will be able > to just apply it as a patch. (If the title was "Norwegian validation > message issue", would you open it unless it signaled that it was ready to > be resolved?) > > Maybe if you uploaded the solution as a patch and accepted that it can be > included in the source, it will go faster. > > ps: If you read the page "Community" (1), it says "Please note that a patch > is always preferred over an archive of properties files." The comment is > the jira thread is even more difficult to apply than a archive. > > > > Regards > Sigbjørn Tvedt > > 1: > > http://tapestry.apache.org/community.html#Community-ContributingtranslationsforTapestrybuiltinmessages > > > > On 3 September 2012 17:53, Rural Hunter <ruralhun...@gmail.com> wrote: > > > https://issues.apache.org/jira/browse/TAP5-1865 > > I raised the defect several months ago and there have been several > > Tapestry releases since then. I don't see any action in the ticket so I > > suppose it's not fixed. The solution is very simple and has already been > > put in the ticket. I'm wondering why it's still not fixed. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >
