cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Querna <>
Subject [PROPOSAL] CTR for all non-code changes
Date Fri, 18 Sep 2009 20:12:20 GMT

I'm not a commiter (yet!) for Cassandra, but it seems that doing
simple changes like fixing up the README requiring RTC
(review-then-commit) is over burdensome, without providing any
advantage to stability.

For the Apache HTTP Server project, while we use RTC for all of our
stable branches, for documentation and other non-code changes, we use
CTR (commit-then-review).  This lets simple things like typos to
developing large chunks of documentation happen quickly and without
any process burdens, which has allowed the Apache HTTP Servers great
documentation project to thrive.

I am starting to believe it would be helpful if Cassandra adopted a
similar CTR policy for non-code changes on trunk and all branches.




View raw message