How do you plan to handle the upcoming XGC1.5 and FOP1.1 release doc changes? They will need to get deployed, then merged with trunks, then redeployed. After that, they can be reintegrated into your CMS sources I guess. Is that what you expect?
On Fri, Oct 12, 2012 at 11:03 PM, The Web Maestro <[email protected]>wrote: > Hi folks, > > Could we get some eyeballs on the new ASF CMS system? We're all going > to need to update pages there, and we haven't migrated yet... > > I don't know if folks've been adding recent Documentation/Content > changes there as well, but we'll need to start soon! ;-) > > I've attached a coupe of lists of files that need to be merged into > the ASF-CMS documentation for FOP & Batik. I guess I need to do it for > XML Graphics as well, but that should be pretty simple! > > We're getting closer to the wire, and I thought I'd ping the team > about the migration. We have some lingering issues (see below) I'm > still working to resolve, but for the most part they're relatively > minor. > > The worst issue is an IE9 scrollbar issue that *many* sites around the > 'Net are experiencing. I intend to have a fix for that soon! There are > also issues with the Batik Demo, and some expanded nav blocks. > > I was able to fix the FOP Compliance page, but I haven't gotten many > lurkers from folks outside of Chris & Helder... > > Kind regards, > > Web Maestro Clay > -- > <[email protected]> - <http://ourlil.com/> > My religion is simple. My religion is kindness. > - HH The 14th Dalai Lama of Tibet > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
