Andreas Hartmann wrote:
But how would it happen on the stable branch then?
You suggested RTC - would that mean that committers should
attach patches to bugzilla and the PMC reviews them before
they're committed?
or on the mailing list. in java land, patches seem to be bigger in
general than say, in C, which is why the mailing list might not work so
well if you intend to check in half a dozen classes.
so i would leave that up to the discretion of the committer.
http://httpd.apache.org/dev/guidelines.html has a useful discussion on
RTC /CTR :
"Ideas must be review-then-commit; patches can be commit-then-review.
With a commit-then-review process, we trust that the developer doing the
commit has a high degree of confidence in the change. Doubtful changes,
new features, and large-scale overhauls need to be discussed before
being committed to a repository. Any change that affects the semantics
of arguments to configurable directives, significantly adds to the
runtime size of the program, or changes the semantics of an existing API
function must receive consensus approval on the mailing list before
being committed."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
