Doesn't this fall under the general "develop on the list" practice? I would assume that developing on the list includes mentioning when you are going to do something like swap out a library for a newer version.
Can someone articulate what problem this new policy proposal is addressing and how it addesses it? It is very difficult for me to see what the goal here is and if that goal is being achieved. James Margaris -----Original Message----- From: Upayavira [mailto:[EMAIL PROTECTED] Sent: Friday, February 02, 2007 2:35 PM To: general@incubator.apache.org Subject: Re: [Vote] Incubating Project Policy William A. Rowe, Jr. wrote: > Upayavira wrote: >> I'd add clarification about 'committing third party code' with >> reference to libraries. I should be able to commit the latest log4j >> jar without having to do any jira nuisance. This is about committing >> the code itself as a contribution, not as a dependency. > > I deliberately included libraries as third party code. Including (for > example) log4j in your project, and deciding how 'fresh' (bleeding edge? > advertised stable? last known stable?) of a version the project should > bump it to. You might even discover that there is an issue with the > version you want to adopt that's known to another project contributor. > > There's nothing unreasonable about posting "I'm bumping our log4j to > trunk to resolve our interop bugs with ..." before you do so, right? Yep, true enough. Upayavira --------------------------------------------------------------------- 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]
