On Tue, Sep 6, 2011 at 12:20 PM, Eric Evans wrote:
> Here is what I propose to do (one driver at a time):
>
> 1. Setup new Git-based projects on Apache Extras (cassandra-jdbc and
> cassandra-dbapi2)
> 2. Import the most current code and fix-up the tests as needed
> 3. Submit issues w/ patches for
On Fri, Sep 9, 2011 at 3:32 PM, Nick Telford wrote:
> It may be prudent to have someone to accept responsibility for each of the
> official drivers in Extras. This way we could have a single ticket (perhaps
> with sub-tickets for each driver) to ensure drivers are brought up to date
> for each rel
It may be prudent to have someone to accept responsibility for each of the
official drivers in Extras. This way we could have a single ticket (perhaps
with sub-tickets for each driver) to ensure drivers are brought up to date
for each release.
This would be less about polluting the C* JIRA with im
On Fri, Sep 9, 2011 at 2:40 PM, Rick Shaw 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 v
On Fri, Sep 9, 2011 at 8:40 AM, Rick Shaw 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?
I can't
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?
As a small convenience to the Maven inclined among us, perhaps it
On 7 September 2011 10:12, Eric Evans wrote:
> On Wed, Sep 7, 2011 at 8:22 AM, Stephen Connolly
> wrote:
>> On 6 September 2011 18:34, Vivek Mishra wrote:
>>> Sounds good moving to github.
>>> 1 quick question, what about JIRAs already raised w.r.t drivers? Not sure
>>> but is it possible to in
On Wed, Sep 7, 2011 at 8:22 AM, Stephen Connolly
wrote:
> On 6 September 2011 18:34, Vivek Mishra wrote:
>> Sounds good moving to github.
>> 1 quick question, what about JIRAs already raised w.r.t drivers? Not sure
>> but is it possible to integrate these new projects with current JIRA flow?
>>
On Tue, Sep 6, 2011 at 6:34 PM, Vivek Mishra wrote:
> Sounds good moving to github.
It's Google Code/Apache Extras that we've been discussing actually
(http://code.google.com/a/apache-extras.org/hosting).
> 1 quick question, what about JIRAs already raised w.r.t drivers? Not sure but
> is it po
On 6 September 2011 18:34, Vivek Mishra wrote:
> Sounds good moving to github.
> 1 quick question, what about JIRAs already raised w.r.t drivers? Not sure but
> is it possible to integrate these new projects with current JIRA flow?
>
> Planning to make these new projects based on maven build proc
This looks like a good plan.
Once the drivers are moved to Google Code, would we be managing/tracking issues
via Google Code or still via JIRA? I would assume Google Code, but wanted to
clarify.
Since each driver will likely be in it's own repository I would also like to
see the ruby driver
Sounds good moving to github.
1 quick question, what about JIRAs already raised w.r.t drivers? Not sure but
is it possible to integrate these new projects with current JIRA flow?
Planning to make these new projects based on maven build process?(As that might
be helpful in case of any quick relea
12 matches
Mail list logo
