db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinav Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6791) Google Summer of Code 2015: Derby bug fixing
Date Sat, 14 Feb 2015 17:56:12 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321599#comment-14321599

Abhinav Gupta commented on DERBY-6791:

Hi Bryan,

I went through all the links and then I looked at at the bugs that you
And I went through Derby-6773, looked at the description and links on the
page, it seems to be a bug that I can solve but what I am not sure is how
to start working on it. Could you please give me a quick idea on how the
bug/ improvement (Derby- 6773) can be reproduced, and how to know what part
of the Derby code needs to be fixed.

Thank you very much :)


On Thu, Feb 12, 2015 at 4:15 AM, Bryan Pendleton (JIRA) <jira@apache.org>

> Google Summer of Code 2015: Derby bug fixing
> --------------------------------------------
>                 Key: DERBY-6791
>                 URL: https://issues.apache.org/jira/browse/DERBY-6791
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, SQL, Store
>            Reporter: Bryan Pendleton
>              Labels: Java, database, gsoc2015, jdbc
> For the 2015 Google Summer of Code, I am offering to mentor a
> student for general bug fixing of the Derby database.
> The Derby JIRA has collected the community's knowledge about
> known bugs in Derby, and there are plenty of bugs for us to work on.
> If you take on this project, with assistance from me, you'll:
> - select Derby issues from the Derby issue to fix
> - reproduce those problems by writing and running tests
> - develop patches to address the problems
> - work with the community to get the patches reviewed
> - have your reviewed and accepted contributions committed to the next Derby release.

This message was sent by Atlassian JIRA

View raw message