On Feb 12, 2008 1:34 PM, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > Sorry, I did not mean this. I meant that customer (or better, users) > may "ask" for features/bug fixing, but it will be fixed only if there > is a developer willing to do the work.
Another way of looking at it is that *WE* are the customer. An Apache project builds the product that we ourselves *want* to use (and then we actually use it). Other people who use Apache projects are not the customer, but prospective customers, who might someday want to contribute back to the project (by helping out on the mailing list and issue tracker, suggesting patches, testing builds, and so forth). People who use our products for years and years, but never contribute back, are simply freeloaders. (God bless them every one!) Since it's an all-volunteer effort, talking about doing something that someone else might like us to do (a prospective contributor or freeloader), tends not to work in the long term, since there is no incentive to actually do the work -- unless the feature also helps us in our own work. It's easy to talk about such things, it's harder to find the volunteer hours to actually do them. :) A key problem with continuing to patch a branch is just that it's more work, and we have very few people who are ready, willing, and able to do any of the patch work right now. If someone has an itch to release 2.0.12, and wants to backport some of the patches, then great, have at it. But, please, only if you fully intend to follow through and create a new 2.0.12 build for the rest of us to test. We have a large backlog of patches. Insisting that everyone apply and test all of these patches against the branch, and making sure it builds (Is Bamboo building the branch?), is twice as much work. Right now we can even get anyone to do 1x the work!. AFAIK, if a security issue came up with 2.0.11, we could make a surgical fix and release that as 2.0.12. It's as GA now as it was when released it. But, if we start applying miscellaneous patches, then 2.0.12 would not be GA ready anymore, and if we had to do an immediate, surgical release, we'd have to roll a 2.0.11.1 instead. HTH, Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
