https://issues.apache.org/bugzilla/show_bug.cgi?id=46202
--- Comment #5 from Helder Magalhães <[email protected]> 2009-03-13 10:44:35 PST --- (In reply to comment #4) > 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. I was generally thinking that the documentation was meant to reflected the last release, but now that you pointed out the status page, I remember so it seems that this is unclear (you have my memory refreshed )... :-| > 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? My 2 cents go for having the documentation always reflect the trunk status. One could use something like the @since javadoc keyword for stating newly introduced features, but I'm not sure if this can become confusing for users. I also like the idea of only stating the relevant differences of trunk vs. last release, but this means that changes need to be tracked down whenever a new version is released... I'm comfortable with any of these, please post your opinion(s) and I'll try to review the patch whenever possible. > If you could create a separate patch and attach it to that bug, that would be > better I think. OK, I'll take a look at that whenever possible. ;-) -- 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]
