On Fri, Sep 9, 2011 at 2:40 PM, Rick Shaw <wfs...@gmail.com> wrote: > I worry that if the issue management is moved from the main JIRA for C* > sponsored drivers there will be synergy and awareness lost between client > and server. Did the Hector and Pelops folks see it as a good thing to have > their own?
It's a valid point, but I think I think it's easier to solve that if it becomes a problem, than it is to try and map the workflows of many projects onto a tool meant for one. If it does become an issue then we can make it something to work on, which could include technical solutions like linking bug trackers. For example, think of the way that Hudson/Jenkins uses JIRA's SOAP API (I assume) to update issues on success/failure. > As a small convenience to the Maven inclined among us, perhaps it would be > useful and non threatening to maintain the directory structure for the JDBC > driver in default Maven directory structure format? This would be > exceedingly helpful for simple source control checkout of the code base for > those that would like to add their own POM to build and test, and not effect > a default ANT build in any way. Yes I know it is possible to remap all the > various directory resources but if it start out using the Maven defaults > both camps can easily interoperate without a lot of special casing as it > should not really matter to an ANT build design. I have no personal objections, but I would ask that we put off things like this until the move is complete. -- Eric Evans Acunu | http://www.acunu.com | @acunu
