On Thursday, November 13, 2003, at 01:45 AM, Andreas L. Delmelle wrote:
Yeah, hidden all the way down on the page ( could cause problems with *very*
lazy users viewing the site at lo-res? :) )
Perhaps it was laziness (ouch! ;-p), but I'd like to think not. I spent 10-15 minutes looking on the site to determine where I could download the the 1.0Dev version to test with--actually, I've gone searching a *bunch* of times, only to get frustrated and "come back later" to find it. Truth is, I didn't know *what* to look for and the term "snapshot" didn't come to mind...
Anyway, I will be submitting a [PATCH] to change the download page to highlight "FOP 1.0DR1 Snapshot" shortly. However, I might also modify the page to indicate the following links/headings:
* Binary or Source? * Current Release Binary Download * Current and Development Release Source Downloads
I'll then change the content of the "Current and Development Release Source Downloads" section accordingly:
<snip/>
MODIFIED:
* [b]FOP-1.0DR1 Snapshot[/b] - Download a CVS snapshot of FOP-1_0DR1
from the cvs files [a href=..]here[/a]. These snapshots are built
approximately every six hours, and have the GMT of their creation
time embedded in their names. Please note that these CVS snapshots are
made only for the "HEAD" branch.
* [b]FOP-1.0DR1 Snapshot[/b] - Download a CVS snapshot of FOP-1_0DR1
from the cvs files [a href=..]here[/a]. These snapshots are built
approximately every six hours, and have the GMT of their creation
time embedded in their names. Please note that these CVS snapshots are
made only for the "HEAD" branch.
* [b]FOP-1.0DR1 Snapshot[/b] - Download a CVS snapshot of FOP-1_0DR1
from the cvs files [a href=..]here[/a]. These snapshots are built
approximately every six hours, and have the GMT of their creation
time embedded in their names. Please note that these CVS snapshots are
made only for the "HEAD" branch of [a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/ ?only_with_tag=HEAD"]CVS[/a].
I'd also like to standardize on what we'll be calling this on the site. Here are the contestants I'm aware of:
Redesign TRUNK HEAD FOP 1.0Dev FOP-1.0Dev FOP1.0Dev FOP 1.0DR1 FOP-1.0DR1 FOP1.0DR1
(Personally, I like "FOP-1.0DR1" so that's what I'll use in my [PATCH]. I'm not calling for a vote--a) I don't think I can call a VOTE yet; b) does this need a VOTE?--but it would be good to know that everyone's on the same page... ;-p)
+1, although I never really experienced problems with it, I can imagine that
the average FOP-noob gets a bit confused by all this name-juggling...
Having used FOP for over a year, I don't consider myself an average FOP-noob, in spite of the fact that I have trouble keeping the names straight. ;-p
The term "Redesign" will become obsolete as soon as 1.0 gets released.
(FYI: "FOP-1.0Dev" turns up on the command line as version indicator )
Obsolescence. Too true! Hehehe! Anyway, I thought I'd seen FOP-1.0Dev somewhere!
I guess that's not really worth it, although to be honest I don't know
if there've been any updates to the "fop-0_20_2-maintain" branch (i.e.,
0.20.5). Have there been (the Release Notes don't indicate any
changes)? If so, it might be good to identify what they are somewhere.
If there are not, then never mind.
Release notes only indicate changes compared to the previous version (
0.20.4 ). If I'm not mistaken, Glen has applied a few (although I believe it
to be very few) patches to 0.20.5 since its release in July. ( amongst
others the printJobName displaying as 'FOP Document' ).
Is CVS the only place where the new and improved 0.20.5 can be downloaded? Does it make sense to generate a "snapshot" each time updates are made to the 0_20_2-maintain branch, since "everyone" is using it? If updates are made, they are significant. I have to assume that the 0.20.5 binary is unchanged else the name would change to indicate updates (0.20.5a or something).
Obviously would also be quite an effort to update the Release Notes with
every little bugfix/patch being applied, but if you're volunteering, who are
we to stand in your way ;)
I wouldn't mind making these types of changes. It's not like we make changes to 0.20.5 very often... ;-p
