Most if not all of the committers are in the same boat as you are. They have already risked their own time and energy to patch issues themselves so many times that the previous committers thought it's simply easier to give commit access to this person than to keep applying his patches.
All software has bugs but Tapestry's codebase is in general very mature, well tested and well thought out. Tapestry committers have, for various reasons, decided that the benefits of using Tapestry outweigh the drawbacks, even when patching issues themselves. Everybody needs to do their own benefit analysis. In terms of user base, Tapestry has one of the largest among Java web frameworks. The most certain way of getting your issue fixed is supplying a patch with test. It doesn't always get applied or it doesn't get applied without changes. If you think it's difficult to get a patch applied to Tapestry, you should try kernel development first. Kalle On Sat, Oct 26, 2013 at 6:31 PM, Lenny Primak <[email protected]>wrote: > Hi guys, > > I am struggling with a problem - how to get bugs (that I care about) fixed? > I am building web apps for clients that run on Tapestry. > I am finding that I am spending more and more time working around Tapestry > bugs. > The time that I spend fixing / working around bugs in Tapestry is the time > I don't spend building > and fixing my own applications. This isn't a good situation. > > I originally built the FlowLogix library to bridge Tapestry with JEE, and > Shiro (via Tapestry-Security) > Most of the functionality in there now is actually workarounds for various > bugs and missing features in Tapestry. > I always file a JIRA for every one of them. Minority gets fixed (after > much begging) but majority isn't getting fixed. > > I know there are a lot of JIRA issues and few committers. I also know I > can submit patches, but this can be dicey as well, > as that takes committers' time and energy. Risk for me is that I can't > spend time creating patches that don't get applied, or > get rejected because I don't have a separate test (even though it's mostly > enough that it doesn't cause a regression, > which is covered by other tests) > > I also know Tapestry community is small, and volunteer, so this problem > doesn't really surprise me. > Right now, I am at a point that is getting unsustainable in this manner, > especially since so many changes are > happening in T5.4, which brings much more work and more bugs to fix. > > I'd like to know if any committers want to help solve this problem? I > know it can be solved. > What can be the motivating factor in getting these bugs fixed? > > I will even go as far as paying for the fixes. My clients won't pay for > me to fix Tapestry, > so I would have to pay out of my own pocket, just so I don't have to lose > time fixing Tapestry myself. > Any other suggestions? > > Same applies to Tynamo project as well. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
