Adrian, I think your OFBIZ-495 is a perfect example of an issue that would benefit from something like this. It's a fairly large task, and while there has certainly been a lot of discussion on the mailing list, you've essentially been left with the burden to complete the task. However, if your patches were applied to a sandbox, I think others would be more apt (theoretically speaking) to take a look at it, and instead of pointing out where there may be a flaw, point out the flaw and provide a quick solution.
How many comments in JIRA are: "there's xyz problem with this patch, please resubmit". This is the exact response the reviewers should be giving because of the amount of time it would take on their part to fix the problem and create a more correct patch. However, it puts the burden back on the original submitter even though he may be 30 days or more beyond that problem in his own deployment. In any event, I highly doubt there will be any arm twisting for anyone to utilize a sandbox when available. But for those who want to collaborate a little more closely with others, the option will hopefully be beneficial for them. --- Adrian Crum <[EMAIL PROTECTED]> wrote: > I don't agree that each patch needs to be a nearly > complete solution. I have two > features I've been working on for a while now and > I've broken them up into > smaller pieces - each one is its own Jira issue. > Some of those patches have made > their way into the project, some have not. > > Having it broken up that way allows others to work > on bits of the project. > Committers have the option to commit the portions > they feel are useful. The > remainder can be downloaded and applied to local > copies. > >
