2011/11/24 Michal Hasko <mha...@redhat.com>: > On 11/23/2011 06:38 PM, Konstantin Kolinko wrote: >> The preferred way is to create a report in Bugzilla and attach the patch >> there. > > As I think about what the page http://tomcat.apache.org/svn.html says > about trunk branch: > > "The primary development branch. Patches are committed here using > Commit-then-Review and then voted on for porting to the release > branches using Review-then-Commit." > > Does that mean that I, puny mortal human can commit directly to trunk? >
No. It just means that all new changes are committed to trunk first, and then proposed, reviewed and voted before applying them to stable branches. (Well, tc7.0.x is still C-T-R now, but that is a minor detail). If you want to learn more about how commit rights etc. work at ASF, you may want to look at the following ASF pages. Though it is not related to the problem you are solving now, but you may want to look at it later. http://www.apache.org/foundation/how-it-works.html http://www.apache.org/dev/contributors.html > >> You can file it for "Tomcat 7" and select "trunk" in the version field >> there (or latest released version if the problem affects released >> versions of Tomcat 7). Just mention against what version& branch of >> the source code the patch was generated. > > What bugzilla component would you suggest for reporting such change > (possibility to override default plaintext junit log format) in > build.xml? The 'Packaging' seems to be closest to build.xml changes, > although I admit it is probably not the best. > It does not matter much and can be changed later. All Bugzilla mail goes to dev@ anyway. Most reports go to 'Catalina', but it can be 'Packaging' as well. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
