[
https://issues.apache.org/jira/browse/GORA-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967167#comment-13967167
]
Lewis John McGibbney commented on GORA-321:
-------------------------------------------
I can't work on this until Sunday but I am +1 for the patch being brough in to
trunk.
Arguments for are that
* In addition to sql, we are opting *not* to release dynamodb module this time
around.
* if tests pass in Jenkins and locally in the terminal then it would be
foolish to delay rolling a release candidate just because the tests don't pass
in Eclipse. What if they pass in Netbeans on something else? We should have an
IDE agnostic approach IMHO.
If a project committer would like to commit this patch then I am +1 for
committing it to trunk and seeing how the Jenkins builds go... we can always
roll back the commit if needs be.
> Merge GORA_94 into Gora trunk
> -----------------------------
>
> Key: GORA-321
> URL: https://issues.apache.org/jira/browse/GORA-321
> Project: Apache Gora
> Issue Type: Improvement
> Components: avro
> Affects Versions: 0.4
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Blocker
> Fix For: 0.4
>
> Attachments: GORA-321-final.patch, GORA-321.patch
>
>
> This is a final issue to merge in GORA_94 into trunk.
> I'll get a patch attached here which provides a diff people can apply against
> Gora trunk code base.
> Within the scope of this patch, I am proposing to NOT release gora-dynamodb
> for 0.4 as there is additional thought required to get it working.
> [~renato2099] and myself have been discussing this at ApacheCon and will
> address it in due course.
> I would like to personally thank ALL contributors to GORA_94 branch over
> recent months. It became a bit of a monster and it a major contribution to
> Apache Gora.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
