Hi all, I'll soon start the release process for XML Graphics Commons. There's not much to do there, apart from updating the website content. Meanwhile I'd like to enter some kind of freezing phase in the FOP area. That is, mainly, avoid to perform too big changes which might introduce instabilities in the code. I propose the following plan: - make a list of patches/bugs that we would like to apply/fix before releasing. Here everyone can help, even non-committers ;-) Once the list is done we will see how many of them we can handle. - refactor the website according to Chris' recent suggestions. That requires some writing skills and a minimal knowledge of Cocoon/Forrest and I'd be /very/ grateful for any help in this area... - once Commons is released we can start the process for FOP
I'll create the branch very soon, as it's probably best to perform the website refactoring in it. Once it's done we will have to be careful when committing changes. I suggest to perform code changes on Trunk only and merge in the 0.94 branch if applicable; and make website changes in the branch only, that I'll merge back into Trunk once the release is out. Speaking of branches, I noticed that there are many (very) old branches on Subversion. What about removing them? Some cleanup wouldn't hurt, they won't be completely lost anyway as it will still be possible to retrieve them from earlier revisions, and the corresponding tags would remain. The candidates for removal are: - FOP_0-20-0_Alt-Design/ - FOP_0-20-4Pre_BuildExp_pbw/ - Temp_API_Finalization/ - Temp_KnuthStylePageBreaking/ - Temp_SpaceResolution/ - dirkx/ <---- what is this one?? - fop-0_14_0/ - fop-0_14_0_regions/ - fop-0_17_0_batikSVG/ - fop-0_20_2-maintain/ - fop-0_90/ - fop-0_91/ - fop-0_92/ - fop-0_93/ - foray-font/ - release-0-13-0/ Some time ago we discussed about abandoning support for Java 1.3. Since then I forgot to launch the poll on fop-user. I guess this will have to be postponed and 1.3 archives will be provided for 0.94. I think that's all for now. Thanks, Vincent
