You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2016/09/01 00:23:20 UTC
[jira] [Resolved] (DERBY-6870) Google Summer of Code 2016: Derby
bug fixing
[ https://issues.apache.org/jira/browse/DERBY-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Pendleton resolved DERBY-6870.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.13.0.0
We've completed all the intended work on this issue. Thank you Danoja
for all your contributions to Derby!
> Google Summer of Code 2016: Derby bug fixing
> --------------------------------------------
>
> Key: DERBY-6870
> URL: https://issues.apache.org/jira/browse/DERBY-6870
> Project: Derby
> Issue Type: Improvement
> Reporter: Bryan Pendleton
> Assignee: Danoja Dias
> Labels: database, gsoc2016, java, jdbc
> Fix For: 10.13.0.0
>
>
> For the 2016 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 bug tracker 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
(v6.3.4#6332)