Am 29.10.2015 um 00:57 schrieb Konstantin Kolinko:
2015-10-29 1:42 GMT+03:00 Mark Thomas <ma...@apache.org>:
All,
Many years ago, we switched all release branches to RTC primarily to
address a community problem where we could not agree on the best way
forward for some parts of the code.
RTC served us well. The disagreements ceased pretty much instantly.
However, RTC also slowed us down.
The development of 7.0.x started as CTR with a possibility of switching
to RTC if necessary. It never was. We chose not to switch 7.0.x to RTC
because the community issues that made RTC necessary had been solved and
RTC added unnecessary overhead and delay. 8.0.x and now 9.0.x progressed
the same way. Today, only 6.0.x is RTC.
I believe the use of RTC for 6.0.x is causing more harm than good. There
are fixes I don't propose for backport to 6.0.x because of the extra
hassle RTC introduces. I suspect others take a similar approach judging
on the number of fixes that don't make it back to 6.0.x.
I would therefore like to propose that we switch the 6.0.x release
branch from RTC to CTR and am therefore calling a VOTE to make this change.
[ ] Continue to use RTC for 6.0.x
[x] Switch 6.0.x to CTR
2. RTC seriously gets in a way, as review rate is slow. After waiting
for several months it is easy to loose track of the original problem.
Historically, I think Mark's work on introduction of automated tests
in Tomcat 7 became a key of success of CTR model for Tomcat 7 and
later. We do not have automated test in Tomcat 6 yet, but I no longer
consider it a showstopper against CTR.
I agreed also with these comments of Konstantin.
I guess we should not push backports to TC 6 to hard and instead value
stability over new features there.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
