+1 I wouldn't be able to take a 1.0.1 release anyway with my release cycle.
I will try to look for more text extraction performance tweaks to provide for 1.1.0 if I can. -----Original Message----- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Thursday, February 25, 2010 4:17 AM To: dev@pdfbox.apache.org Subject: Next release & merging of trunks Hi, As discussed, we have a few open issues for which it would be nice to push out a new release as soon as they're fixed. I'd like to start preparing for a 1.1.0 release for this. I'd not go for 1.0.1 as we already have some API changes in trunk and cherry-picking bug fixes to a maintenance branch doesn't seem worth the effort for now. These issues span all three of our components, so it would probably be easiest to do a simultaneous release of all the components. Since also 1.0.0 was made as a simultaneous release of two components, I think it might be worthwhile to consider merging the release cycles of the components. Instead of separate trunks (jempbox/trunk, fontbox/trunk, pdfbox/trunk) we'd only have a single trunk with the three components inside it (trunk/jempbox, trunk/fontbox, trunk/pdfbox), all sharing the same version number and release cycle. Thus a PDFBox 1.1.0 release would consist of 1.1.0 versions of all the components. WDYT? BR, Jukka Zitting
smime.p7s
Description: S/MIME cryptographic signature
