On 23.03.2007 13:09:59 thomas.deweese wrote: > Hi Cameron, > > Cameron McCormack <[EMAIL PROTECTED]> wrote on 03/22/2007 10:41:09 PM: > > > Cameron McCormack: > > > Cool. It does fix the batik70.svg rendering under OS X. Unfortunately > > > it didn?t seem to help the other rendering issues. > > > > All of the rendering issues under OS X also existed with Batik 1.6. > > Since they?re not regressions, I suggest we leave them for now and forge > > ahead with the 1.7 release. > > I tend to agree. > > > Still waiting on Rhino to have a new release (I believe Atilla is > > working on better security policy work in general, rather than applying > > the workaround I supplied). What does everyone think of making the > > release candidate with Rhino 1.6R5 + a patch to make the debugger work, > > and then making the final 1.7 release once Rhino?s next distribution is > > out? > > I wasn't sure we could do that. I thought when we used code outside > the project it had to be 'released' code. Am I wrong on this? > Maybe I'm making stuff up, Jeremias any comment?
This rule is mostly about ASF-controlled software. The board wants that a certain amount of oversight is in place. For software developed outside the ASF, other rules may apply but it is still better to rely on formally released software in order to avoid potential legal problems. Imagine someone changing something that later turns out that the code was stolen somewhere (or whatever), i.e. they find a legal problem only after you already released with this code. Depending on released software decreases the likelihood that you run into any possible problems. If a committee has to nod a release through there's a good chance most problems are caught. In the case of a release candidate plus a patch you have full control over, you should be fairly safe. I wouldn't veto such a release. What's not a good idea is to take a snapshot from a code repo and put that in a ASF-controlled release. HTH Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
