Next Release Schedule
Hi, all Keiron announced a code freeze. Pursuant to that, I will be building and posting a release candidate on Saturday. I figure we should allow 2-3 days for feedback. A final build of the next 0.20.x FOP would then happen Tuesday or Wednesday. Regards, Arved Sandstrom --- This mail was sent through the Nova Scotia Provincial Server, with technical resources provided by Chebucto Community Net. http://nsaccess.ns.ca/mail/ http://www.chebucto.ns.ca/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Release Schedule
Please don't forget "fop.sh" file also. Thanks in Advance Thanks, Mike -Original Message- From: Charlie Wu [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 7:24 PM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: RE: Release Schedule Please include javadoc and the batch files in both the src release and binary release.. it took me hours to figure out hwo to get fop to work because i only downloaded the binary release (0.19).. thanks Charlie -Original Message- From: Arved Sandstrom [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 4:14 PM To: [EMAIL PROTECTED] Subject: Release Schedule Hi, all I have the 0.18 to 0.19 changes put into the CHANGES file. Please review carefully. I am committing the 0.19 to 0.20 changes to that file tomorrow evening. You'll have until Sunday to review the CHANGES file. I'll make final mods to that file Sunday, immediately prior to building the release. If you've got an issue with credits, please pipe up. :-) We had quality control problems (my fault) with existence, location and condition of DOS batch files in the last release. I promise to be more careful with these this time. Can anyone think of anything else that relates to the suitability and serviceability of the distributions? I am still (and have been for quite a while) very undecided about whether to include Javadoc (size considerations). Perhaps in the source distro only? Comments? Regards, Arved Sandstrom -- Fairly Senior Software Type e-plicity (http://www.e-plicity.com) Halifax, Nova Scotia Wireless * B2B * J2EE * XML - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Release Schedule
Arved Sandstrom wrote: > > At 09:46 PM 8/9/01 -0500, Weiqi Gao wrote: > > > > This makes sense. People who are getting the source > > release can build the Javadocs from the release. > > People who are getting the binary release can't > > build the Java docs, so they need the Javadocs bundled > > in. > > Weiqi, > > I assume you meant that what makes sense is neither what > I suggested nor what Charlie suggested, but rather, > prepared Javadoc with the binary distro, and none with > the source. I pretty much assume that the complete set > of batch files will be identical acrosss different > distros. Of course this is assuming that the Javadoc is going to be useful for the customers of the binary distribution. > I want to make it clear that the Javadoc is not going > to help someone all that much in figuring out how to > make FOP run. We are talking about the API docs when I > say Javadoc, _not_ the regular HTML documentation. I have to admit that during the past few months of trying to use FOP I have never looked at the Javadoc. The HTML documentation has been adequate. However I'm just one user. There might be other users whose experience says otherwise. When I said "Javadoc in binary distribution", what I had in mind are things that I can download from Sun's website, like JAXP 1.1, JSSE, JNDI, etc. They've always included the Javadocs. But they distribute only the public API Javadocs (the javax.naming.*, etc., part, not the com.sun.naming.*, etc., part). I don't know how FOP can fit into that model. Maybe when the public API is separated from the implementation details, FOP can provide Javadocs only for the public API and not the implemenation details, thus cutting down the size of the distribution. Until then, go with your instinct. > Incidentally, none of this is an issue for me. I have a > fast machine and I have a cable connection. If all > potential users also have cable or ADSL connections then > it's a moot point. But they don't, so distro size (I > would think) is a consideration. Speaking as one with a 28.8k modem behind an unlimited hours ISP, I don't really care about the size either. (I downloaded my GNOME 1.4 as well as the .NET SDK over the phone line. It took only a couple of DAYS.) -- Weiqi Gao [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Release Schedule
At 09:46 PM 8/9/01 -0500, Weiqi Gao wrote: >Charlie Wu wrote: >> >> Please include javadoc and the batch files in both the >> src release and binary release.. it took me hours to >> figure out hwo to get fop to work because i only >> downloaded the binary release (0.19).. > >This makes sense. People who are getting the source release can build the >Javadocs from the release. People who are getting the binary release can't >build the Java docs, so they need the Javadocs bundled in. Weiqi, I assume you meant that what makes sense is neither what I suggested nor what Charlie suggested, but rather, prepared Javadoc with the binary distro, and none with the source. I pretty much assume that the complete set of batch files will be identical acrosss different distros. I want to make it clear that the Javadoc is not going to help someone all that much in figuring out how to make FOP run. We are talking about the API docs when I say Javadoc, _not_ the regular HTML documentation. Incidentally, none of this is an issue for me. I have a fast machine and I have a cable connection. If all potential users also have cable or ADSL connections then it's a moot point. But they don't, so distro size (I would think) is a consideration. Regards, Arved Fairly Senior Software Type e-plicity (http://www.e-plicity.com) Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Release Schedule
Charlie Wu wrote: > > Please include javadoc and the batch files in both the > src release and binary release.. it took me hours to > figure out hwo to get fop to work because i only > downloaded the binary release (0.19).. This makes sense. People who are getting the source release can build the Javadocs from the release. People who are getting the binary release can't build the Java docs, so they need the Javadocs bundled in. -- Weiqi Gao [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Release Schedule
Please include javadoc and the batch files in both the src release and binary release.. it took me hours to figure out hwo to get fop to work because i only downloaded the binary release (0.19).. thanks Charlie -Original Message- From: Arved Sandstrom [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 4:14 PM To: [EMAIL PROTECTED] Subject: Release Schedule Hi, all I have the 0.18 to 0.19 changes put into the CHANGES file. Please review carefully. I am committing the 0.19 to 0.20 changes to that file tomorrow evening. You'll have until Sunday to review the CHANGES file. I'll make final mods to that file Sunday, immediately prior to building the release. If you've got an issue with credits, please pipe up. :-) We had quality control problems (my fault) with existence, location and condition of DOS batch files in the last release. I promise to be more careful with these this time. Can anyone think of anything else that relates to the suitability and serviceability of the distributions? I am still (and have been for quite a while) very undecided about whether to include Javadoc (size considerations). Perhaps in the source distro only? Comments? Regards, Arved Sandstrom -- Fairly Senior Software Type e-plicity (http://www.e-plicity.com) Halifax, Nova Scotia Wireless * B2B * J2EE * XML - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Release Schedule
Hi, all I have the 0.18 to 0.19 changes put into the CHANGES file. Please review carefully. I am committing the 0.19 to 0.20 changes to that file tomorrow evening. You'll have until Sunday to review the CHANGES file. I'll make final mods to that file Sunday, immediately prior to building the release. If you've got an issue with credits, please pipe up. :-) We had quality control problems (my fault) with existence, location and condition of DOS batch files in the last release. I promise to be more careful with these this time. Can anyone think of anything else that relates to the suitability and serviceability of the distributions? I am still (and have been for quite a while) very undecided about whether to include Javadoc (size considerations). Perhaps in the source distro only? Comments? Regards, Arved Sandstrom -- Fairly Senior Software Type e-plicity (http://www.e-plicity.com) Halifax, Nova Scotia Wireless * B2B * J2EE * XML - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
