https://issues.apache.org/bugzilla/show_bug.cgi?id=46202
--- Comment #4 from Cameron McCormack <[email protected]> 2009-03-12 15:41:40 PST --- (In reply to comment #3) > I believe there might be interest in breaking this down, in order to allow a > commit whenever possible and a later commit (potentially creating a separate > bug report) for dealing with things which only make sense after the next > release (such as java 1.3 drop and the new window.location interfaces). Does > this make sense? It brings up a good point. What version of Batik the site documentation reflect? In the Status page at least, I have just had it describe whatever the current SVN trunk can do. FOP has separate pages for trunk vs releases. Duplicating all of the documentation for trunk vs release doesn't seem like a nice way to present it, IMO. There aren't that many changes in trunk vs the 1.7 release anyway, so perhaps the documentation can reflect trunk functionality, but with notes stating if certain aspects are since the release? WDYT? > Apart from this, I recently stumbled at bug 43950, which could also be > addressed within this patch. Should it (by creating a bug dependency), or was > it better to create two separate patches? If you could create a separate patch and attach it to that bug, that would be better I think. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
