Ted, While we are on the subject of patches....
Lets say a patch is submitted.. is it enough to rely on the bugzilla message that is sent when a bug is altered or should the patch be generally announced here. From reading the contributing guides it seems to say announce it on the dev list, but to me that is pointless traffic since bugzilla sends the email already. Al -----Original Message----- From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 12:40 PM To: Struts Developers List Subject: Re: RFC: Struts HTML Ajax-Aware Tags You can create a patch that represents the modifications, and then a committer can apply the patch. Appying patches is generally an automatic process and only takes a few minutes. The change logs sent to the commits@ lists are patches. It's not unusual for a mature project to ask that all changes be submitted as patches first, even by the committers. The list can then review the changes before they are made. Around here, we are still operating in lazy consensus mode. We can commit a change, and if nobody squawks, it stick. But, if a PMC member does veto a product change, we have to do undo it. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
