[
https://issues.apache.org/jira/browse/GORA-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069577#comment-13069577
]
Chris A. Mattmann commented on GORA-22:
---------------------------------------
bq. Alexis, it is a commonly accepted practice at Apache that patches are peer
reviewed before being committed
That's not strictly true. It depends on what policy the project is using.
Apache supports both Commit-then-Review (CTR) as well as Review-then-Commit
(RTC) models. Each has their own advantages and outcomes:
http://www.apache.org/foundation/glossary.html#CommitThenReview
http://www.apache.org/foundation/glossary.html#ReviewThenCommit
My personal rule of thumb is that if I'm doing some quick, easy bug fux, or
some new feature, etc., then simply committing it, then asking for feedback is
fine. As devs/committers, we have been granted the commit bit, and we're using
SVN, so things can change as needed. On the other hand, if I'm doing something
larger, and I want feedback from folks *before* I put it in SVN (maybe I
anticipate not having time to modify it much after that point, or I just feel
that getting it right *first* really matters), then I'll enter into RTC mode
and ask for feedback via patches.
Either way is fine, really.
> Upgrade cassandra backend to cassandra 0.7
> ------------------------------------------
>
> Key: GORA-22
> URL: https://issues.apache.org/jira/browse/GORA-22
> Project: Gora
> Issue Type: Improvement
> Components: storage
> Affects Versions: 0.2-incubating
> Reporter: Julien Nioche
> Fix For: 0.2-incubating
>
> Attachments: gora-cassandra-mapping.xml, gora-cassandra-mapping.xml,
> gora.patch, goraCassandra.patch
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
