You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Jeremias Maerki <de...@jeremias-maerki.ch> on 2008/01/10 18:05:54 UTC
Next release - when?
I think we should start to plan the next release. How about targeting
the end of February or beginning of March?
Without much thinking, the following items are on the table:
- Stabilizing tables.
- Stabilizing the image package once I've merged the brach into trunk.
- Verifying the AFP output works correctly.
What else?
Jeremias Maerki
Re: Next release - when?
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Jan 10, 2008, at 18:05, Jeremias Maerki wrote:
Apologies for the rather late reply:
> I think we should start to plan the next release. How about targeting
> the end of February or beginning of March?
Good idea.
>
> Without much thinking, the following items are on the table:
> - Stabilizing tables.
> - Stabilizing the image package once I've merged the brach into trunk.
> - Verifying the AFP output works correctly.
>
> What else?
Can't really think of anything pressing, so I'm going to leave this
open for now.
I agree with the intention of calling it a 'Release Candidate' (as we
have already dropped the Beta-tag when 0.93 was released...), and a
period of +/- 1 month before making the final 0.95 release, as
Vincent suggested, also sounds pretty good to me.
Cheers
Andreas
Re: Refactoring the website [was: Next release - when?]
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Ferdinand Soethe of the Forrest team is working on exactly that. I'm
helping him with some details. It should be ready in a couple of weeks
or so.
On 23.01.2008 11:15:28 Vincent Hennebert wrote:
> Another thing that has just occurred to me: it’s a shame that the PDFs
> available from our website are generated by FOP 0.20.5, while OTOH we
> advertise that this is an ancient version that is no longer supported
> and should really not be used anymore. Do what I say, not what I do.
>
> Either we find a way to plug the latest release of FOP in Forrest
> (Cocoon), or we better disable PDF links until we have handled that.
> That’s a very bad signal I think.
>
> Vincent
>
>
> --
> Vincent Hennebert Anyware Technologies
> http://people.apache.org/~vhennebert http://www.anyware-tech.com
> Apache FOP Committer FOP Development/Consulting
Jeremias Maerki
Re: Next release - when?
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Hi,
Jeremias Maerki wrote:
> On 14.01.2008 08:58:04 Max Berger wrote:
>> Dear Fop Devs,
>>
>> I think we are mixing two ideas here:
>>
>> One idea (1) was to release 0.95rc, and then two weeks later 0.95
>>
>> The other idea (2) is to release 0.95 and call it 0.95rc instead of 0.95beta.
>>
>> (1) I think makes sense. It would mean after releasing the rc there
>> would be a short phase (2 weeks) where only bugfixed could be
>> commited. This is a good idea anyways. +1
>>
>> (2) The traditional dev steps are alpha - beta - final. Some companies
>> use Release Candidate to make their beta-phase sound nicer. I strongly
>> disagree of the use of this word without actually meaning it - as long
>> as this is not a feature-complete version of fop 1.0 I'd vote -1 for
>> calling it rc.
>
> I think we mean (1), at least I do.
Yes that’s what I was meaning too, although 2 weeks seem rather short to
me. I’d extend the testing phase to at least one month.
And according to [1] we would name this release 0.95 beta, as RC is
targetted to a smaller audience. At least that’s how I understand it.
[1] http://apache.org/dev/release.html#release-typeso
>> Btw: Other projects, such as GNOME and eclipse have a strong
>> time-based release plan. Maybe this would be a good idea for the fop
>> project as well? It would give users (and plugin developers) more
>> certainty about whats going on.
>
> Well, nice in theory but that's only possible if there are enough
> resources. We have to do it based on available time and that's not
> really predictable in our case.
Agreed. I seem to have seen somewhere on the website that we would try
to make a new release about every 6 months. It’s not such a bad
indication IMO.
Vincent
--
Vincent Hennebert Anyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer FOP Development/Consulting
Re: Next release - when?
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 14.01.2008 08:58:04 Max Berger wrote:
> Dear Fop Devs,
>
> I think we are mixing two ideas here:
>
> One idea (1) was to release 0.95rc, and then two weeks later 0.95
>
> The other idea (2) is to release 0.95 and call it 0.95rc instead of 0.95beta.
>
> (1) I think makes sense. It would mean after releasing the rc there
> would be a short phase (2 weeks) where only bugfixed could be
> commited. This is a good idea anyways. +1
>
> (2) The traditional dev steps are alpha - beta - final. Some companies
> use Release Candidate to make their beta-phase sound nicer. I strongly
> disagree of the use of this word without actually meaning it - as long
> as this is not a feature-complete version of fop 1.0 I'd vote -1 for
> calling it rc.
I think we mean (1), at least I do.
> Btw: Other projects, such as GNOME and eclipse have a strong
> time-based release plan. Maybe this would be a good idea for the fop
> project as well? It would give users (and plugin developers) more
> certainty about whats going on.
Well, nice in theory but that's only possible if there are enough
resources. We have to do it based on available time and that's not
really predictable in our case.
Jeremias Maerki
Re: Next release - when?
Posted by Max Berger <ma...@berger.name>.
Dear Fop Devs,
I think we are mixing two ideas here:
One idea (1) was to release 0.95rc, and then two weeks later 0.95
The other idea (2) is to release 0.95 and call it 0.95rc instead of 0.95beta.
(1) I think makes sense. It would mean after releasing the rc there
would be a short phase (2 weeks) where only bugfixed could be
commited. This is a good idea anyways. +1
(2) The traditional dev steps are alpha - beta - final. Some companies
use Release Candidate to make their beta-phase sound nicer. I strongly
disagree of the use of this word without actually meaning it - as long
as this is not a feature-complete version of fop 1.0 I'd vote -1 for
calling it rc.
Btw: Other projects, such as GNOME and eclipse have a strong
time-based release plan. Maybe this would be a good idea for the fop
project as well? It would give users (and plugin developers) more
certainty about whats going on.
Max
2008/1/11, J.Pietschmann <pi...@databaar.ch>:
> Jeremias Maerki wrote:
> >> So, what about a 0.95 beta?
> >
> > Like Chris, I'd prefer calling it a release candidate, but +1 to the
> > general idea.
>
> I like the idea of an release candidate too.
>
> J.Pietschmann
>
Re: Next release - when?
Posted by "J.Pietschmann" <pi...@databaar.ch>.
Jeremias Maerki wrote:
>> So, what about a 0.95 beta?
>
> Like Chris, I'd prefer calling it a release candidate, but +1 to the
> general idea.
I like the idea of an release candidate too.
J.Pietschmann
Re: Next release - when?
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 11.01.2008 11:28:47 Vincent Hennebert wrote:
> Jeremias Maerki wrote:
> > I think we should start to plan the next release. How about targeting
> > the end of February or beginning of March?
>
> Seems good.
>
>
> > Without much thinking, the following items are on the table:
> > - Stabilizing tables.
> > - Stabilizing the image package once I've merged the brach into trunk.
> > - Verifying the AFP output works correctly.
> >
> > What else?
>
> Refactoring the website? I’ve already been told several times that it
> was difficult to find its way on it. Last time I mainly rephrased a few
> sentences and removed broken links, but didn’t do much more. And
> I didn’t even touch the ‘Development’ tab which is progressively
> becoming out-of-date.
>
> Should I add that this is not a trivial task and that I’ll have no time
> for that in the next couple of months? :-P
I know a lot more of these little thing we could do. ;-)
> I was also thinking about making this a beta release. With the major
> changes that we made we can’t be sure that no regression has been
> introduced as well. The 0.94 release taught me that even if many bugs
> were fixed, users will stumble upon regressions and (rightly) complain
> about them.
>
> So, what about a 0.95 beta?
Like Chris, I'd prefer calling it a release candidate, but +1 to the
general idea.
Jeremias Maerki
Re: Next release - when?
Posted by Chris Bowditch <bo...@hotmail.com>.
Vincent Hennebert wrote:
> Jeremias Maerki wrote:
>
>>I think we should start to plan the next release. How about targeting
>>the end of February or beginning of March?
>
>
> Seems good.
+1 from me too.
>
> I was also thinking about making this a beta release. With the major
> changes that we made we can’t be sure that no regression has been
> introduced as well. The 0.94 release taught me that even if many bugs
> were fixed, users will stumble upon regressions and (rightly) complain
> about them.
>
> So, what about a 0.95 beta?
Good point. In the old days when we used to do Releases from the 0.20.x
branch, we would usually do at least 2 builds, the first labelled as
"rc" for release candidate. Perhaps we should start using that practise
here. The release candidate build was done first and then 2-3 weeks
later after fixing any issues reported on fop-user the final build was
done. This gives a better assurance of stability.
Chris
Re: Refactoring the website [was: Next release - when?]
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Another thing that has just occurred to me: it’s a shame that the PDFs
available from our website are generated by FOP 0.20.5, while OTOH we
advertise that this is an ancient version that is no longer supported
and should really not be used anymore. Do what I say, not what I do.
Either we find a way to plug the latest release of FOP in Forrest
(Cocoon), or we better disable PDF links until we have handled that.
That’s a very bad signal I think.
Vincent
--
Vincent Hennebert Anyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer FOP Development/Consulting
Re: Next release - when?
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 29.02.2008 11:18:57 Vincent Hennebert wrote:
> Hi,
>
> Jeremias Maerki wrote:
> > Looks good, Clay. Please commit it to Trunk. I'll take it from there and
> > make sure we can incorporate this in the 0.95 release. I'll also see
> > about switching to Forrest Trunk so we can use FOP 0.94/0.95 for the
> > PDFs.
>
> Just curious: do you mean the trunk/ branch of the Forrest repo (future
> 0.9)? Or the “trunk” version of the 0.8 branch? IIC up to now we had to
> use the trunk version of Forrest 0.7 as auto publish wasn’t working with
> the released version, so there seems to be trunks for every version
> (0.7, 0.8, 0.9...).
It's confusing if you use "trunk" in the context of a branch. What you
mean is the "HEAD" revision of a branch.
I mean the HEAD revision (or at some point a fixed revision that we find
stable enough to work with) of the trunk.
>
> > On 29.02.2008 08:34:00 The Web Maestro wrote:
> >> Howdy Folks,
> >>
> >> I've got an update to the FOP web site for the 0.95 release:
> >>
> >> http://people.apache.org/~clay/fop_refactored_0.95/
>
> This is already looking better ;-)
>
>
> >> It's not too different from before, except for the 'Using FOP 0.95' &
> >> 'FOP 0.95 Features' menus in the nav for the Home tab, and I've
>
> I’m not sure those entries should be added to the Home tab. Basically
> they duplicate what’s in the 0.95 tab, so that will add to the confusion
> IMO. The Home tab should remain dedicated to general informations about
> the project. What do others think?
I'm 0 on this if it doesn't cause a maintenance problem.
> Also, have you looked at disabling the menu auto-rolling feature? If
> not, I will ;-)
>
> <snip/>
>
> Thanks Clay,
> Vincent
>
>
> --
> Vincent Hennebert Anyware Technologies
> http://people.apache.org/~vhennebert http://www.anyware-tech.com
> Apache FOP Committer FOP Development/Consulting
Jeremias Maerki
Re: Updating to a newer Forrest (was: Next release - when?)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
I don't see a need to change that. I'll concentrate on the actual
contents to get the release out of the door.
On 03.03.2008 06:43:11 The Web Maestro wrote:
> I was thinking about updating the tabs to be more meaningful. Here's
> what we currently have:
>
> * Home
> * Version 0.93
> * Version 0.94
> * FOP Trunk
> * Development
>
> And I"m thinking about changing that to:
> * Home
> * FOP Previous Release (0.93)
> * FOP Stable Release 0.94
> * FOP Trunk
> * Development
>
> We could go the 'Versioned Docs' tab route a la Forrest like this:
>
> * Home
> * Versioned Docs
> o Version 0.93
> o Version 0.94
> * FOP Trunk
> * Development
>
> It would be fairly easy to do, and it doesn't require Forrest:Views
> but I'm not a big fan of it myself. Then again I believe the new Quick
> Start Guide will be a big help.
>
> Any comments?
>
> Regards,
>
> The Web Maestro
> --
> <th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
Jeremias Maerki
Re: Updating to a newer Forrest (was: Next release - when?)
Posted by The Web Maestro <th...@gmail.com>.
I was thinking about updating the tabs to be more meaningful. Here's
what we currently have:
* Home
* Version 0.93
* Version 0.94
* FOP Trunk
* Development
And I"m thinking about changing that to:
* Home
* FOP Previous Release (0.93)
* FOP Stable Release 0.94
* FOP Trunk
* Development
We could go the 'Versioned Docs' tab route a la Forrest like this:
* Home
* Versioned Docs
o Version 0.93
o Version 0.94
* FOP Trunk
* Development
It would be fairly easy to do, and it doesn't require Forrest:Views
but I'm not a big fan of it myself. Then again I believe the new Quick
Start Guide will be a big help.
Any comments?
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Updating to a newer Forrest (was: Next release - when?)
Posted by The Web Maestro <th...@gmail.com>.
> > > > I removed those links in the nav, and instead replaced them with a
> > > > link to a new Quick Start guide.
> > >
> > > Only that Quick Start Guide is missing!?!
> >
> > No...
>
> Are you really sure? http://svn.apache.org/viewvc?rev=632558&view=rev
D'oh! I'd `svn add`d it, but I wasn't using an svn co with https, so I
had to 'fix' it:
http://svn.apache.org/viewvc?view=rev&revision=632716
> > I added a new file called 'Quick Start Guide' for the Home
> > navigation. At present, the Quick Start Guide merely has links to the
> > important Newbie stuff (mostly what I copied to the Nav from 0.95:
> > Download, Build, Configure; as well as what you can do with FOP:
> > graphics, embedding, servlets, etc.). My intention is to turn it into
> > a 'real' Quick Start Guide.
> >
> > > > > Also, have you looked at disabling the menu auto-rolling feature? If
> > > > > not, I will ;-)
> > > >
> > > > Fixing that should be as easy as adding this to the bottom of the
> > > > <extra-css> block in src/documentation/skinconf.xml:
> > > >
> > > > <extra-css>
> > > > .menuitemgroup{ display: block;}
> > > > </extra-css>
> > > >
> > > > I just added a change to skinconf.xml in svn. Unfortunately, the
> > > > change did not show in my local build. Nevertheless that's how Forrest
> > > > works.
> >
> > Did you get the .menuitemgroup CSS to work?
>
> Haven't tried it, yet. I will later today.
Cool!
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Updating to a newer Forrest (was: Next release - when?)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 02.03.2008 06:01:08 The Web Maestro wrote:
> On Sat, Mar 1, 2008 at 1:53 PM, Jeremias Maerki <de...@jeremias-maerki.ch> wrote:
> > Thanks, Clay! I've already fixed most problems locally. There's a
> > problem with Forrest 0.8 and trunk concerning compliance.pdf. I've
> > already submitted a patch [1] against Forrest Trunk to fix this (plus
> > some other improvements). The "knownissues-overview" problem is for
> > tomorrow. I'll upload the changes when everything is working. The new
> > PDFs will look quite nice when this is finished. Except for the missing
> > auto-table-layout support, of course. :-(
> >
> > [1] https://issues.apache.org/jira/browse/FOR-1072
> <snip/>
> > > I removed those links in the nav, and instead replaced them with a
> > > link to a new Quick Start guide.
> >
> > Only that Quick Start Guide is missing!?!
>
> No...
Are you really sure? http://svn.apache.org/viewvc?rev=632558&view=rev
> I added a new file called 'Quick Start Guide' for the Home
> navigation. At present, the Quick Start Guide merely has links to the
> important Newbie stuff (mostly what I copied to the Nav from 0.95:
> Download, Build, Configure; as well as what you can do with FOP:
> graphics, embedding, servlets, etc.). My intention is to turn it into
> a 'real' Quick Start Guide.
>
> > > > Also, have you looked at disabling the menu auto-rolling feature? If
> > > > not, I will ;-)
> > >
> > > Fixing that should be as easy as adding this to the bottom of the
> > > <extra-css> block in src/documentation/skinconf.xml:
> > >
> > > <extra-css>
> > > .menuitemgroup{ display: block;}
> > > </extra-css>
> > >
> > > I just added a change to skinconf.xml in svn. Unfortunately, the
> > > change did not show in my local build. Nevertheless that's how Forrest
> > > works.
>
> Did you get the .menuitemgroup CSS to work?
Haven't tried it, yet. I will later today.
> Regards,
>
> The Web Maestro
> --
> <th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
Jeremias Maerki
Re: Updating to a newer Forrest (was: Next release - when?)
Posted by The Web Maestro <th...@gmail.com>.
On Sat, Mar 1, 2008 at 1:53 PM, Jeremias Maerki <de...@jeremias-maerki.ch> wrote:
> Thanks, Clay! I've already fixed most problems locally. There's a
> problem with Forrest 0.8 and trunk concerning compliance.pdf. I've
> already submitted a patch [1] against Forrest Trunk to fix this (plus
> some other improvements). The "knownissues-overview" problem is for
> tomorrow. I'll upload the changes when everything is working. The new
> PDFs will look quite nice when this is finished. Except for the missing
> auto-table-layout support, of course. :-(
>
> [1] https://issues.apache.org/jira/browse/FOR-1072
<snip/>
> > I removed those links in the nav, and instead replaced them with a
> > link to a new Quick Start guide.
>
> Only that Quick Start Guide is missing!?!
No... I added a new file called 'Quick Start Guide' for the Home
navigation. At present, the Quick Start Guide merely has links to the
important Newbie stuff (mostly what I copied to the Nav from 0.95:
Download, Build, Configure; as well as what you can do with FOP:
graphics, embedding, servlets, etc.). My intention is to turn it into
a 'real' Quick Start Guide.
> > > Also, have you looked at disabling the menu auto-rolling feature? If
> > > not, I will ;-)
> >
> > Fixing that should be as easy as adding this to the bottom of the
> > <extra-css> block in src/documentation/skinconf.xml:
> >
> > <extra-css>
> > .menuitemgroup{ display: block;}
> > </extra-css>
> >
> > I just added a change to skinconf.xml in svn. Unfortunately, the
> > change did not show in my local build. Nevertheless that's how Forrest
> > works.
Did you get the .menuitemgroup CSS to work?
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Updating to a newer Forrest (was: Next release - when?)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 01.03.2008 09:01:56 The Web Maestro wrote:
> On Fri, Feb 29, 2008 at 2:18 AM, Vincent Hennebert
> <vi...@anyware-tech.com> wrote:
> > Jeremias Maerki wrote:
> > > Looks good, Clay. Please commit it to Trunk. I'll take it from there and
> > > make sure we can incorporate this in the 0.95 release. I'll also see
> > > about switching to Forrest Trunk so we can use FOP 0.94/0.95 for the
> > > PDFs.
>
> It's in there...
Thanks, Clay! I've already fixed most problems locally. There's a
problem with Forrest 0.8 and trunk concerning compliance.pdf. I've
already submitted a patch [1] against Forrest Trunk to fix this (plus
some other improvements). The "knownissues-overview" problem is for
tomorrow. I'll upload the changes when everything is working. The new
PDFs will look quite nice when this is finished. Except for the missing
auto-table-layout support, of course. :-(
[1] https://issues.apache.org/jira/browse/FOR-1072
> > > On 29.02.2008 08:34:00 The Web Maestro wrote:
> > >> Howdy Folks,
> > >>
> > >> I've got an update to the FOP web site for the 0.95 release:
> > >>
> > >> http://people.apache.org/~clay/fop_refactored_0.95/
> >
> > This is already looking better ;-)
> >
> > >> It's not too different from before, except for the 'Using FOP 0.95' &
> > >> 'FOP 0.95 Features' menus in the nav for the Home tab, and I've
> >
> > I'm not sure those entries should be added to the Home tab. Basically
> > they duplicate what's in the 0.95 tab, so that will add to the confusion
> > IMO. The Home tab should remain dedicated to general informations about
> > the project. What do others think?
>
> I removed those links in the nav, and instead replaced them with a
> link to a new Quick Start guide.
Only that Quick Start Guide is missing!?!
> > Also, have you looked at disabling the menu auto-rolling feature? If
> > not, I will ;-)
>
> Fixing that should be as easy as adding this to the bottom of the
> <extra-css> block in src/documentation/skinconf.xml:
>
> <extra-css>
> .menuitemgroup{ display: block;}
> </extra-css>
>
> I just added a change to skinconf.xml in svn. Unfortunately, the
> change did not show in my local build. Nevertheless that's how Forrest
> works.
>
> --
> Regards,
>
> The Web Maestro
> --
> <th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
Jeremias Maerki
Re: Next release - when?
Posted by Andreas Delmelle <an...@telenet.be>.
On Mar 1, 2008, at 09:01, The Web Maestro wrote:
Hi
Just noticed this:
> On Fri, Feb 29, 2008 at 2:18 AM, Vincent Hennebert
>
>> Also, have you looked at disabling the menu auto-rolling feature? If
>> not, I will ;-)
>
> Fixing that should be as easy as adding this to the bottom of the
> <extra-css> block in src/documentation/skinconf.xml:
>
> <extra-css>
> .menuitemgroup{ display: block;}
> </extra-css>
>
> I just added a change to skinconf.xml in svn. Unfortunately, the
> change did not show in my local build. Nevertheless that's how Forrest
> works.
That would make all the nodes expanded by default, but if I interpret
Vincent correctly, it's not /that/ simple...? :/
Just checked a few other projects' sites and the 'annoying' behavior
mentioned earlier is also present there, most notably also Forrest's
own homepage.
BTW: Checking the HTML and JavaScript source, I don't see any sign of
something session-persistent. The structure is relatively simple: if
you switch to tab B, then the browser will be redirected to a new
page, forgetting what the state of the menu on tab A was. Switching
back to A means reloading the page corresponding to the first tab
from scratch.
It could turn out to be not too much effort to add, I guess.
Unfortunately, I'm not fluent in Forrest, so I have no idea how far a
user can go in terms of embedding custom scripts. If they do not
already have something for this, I may just know enough HTML/
JavaScript to hack this together, and if it works well on our end,
donate it back to Forrest one day. Right now, I know little more than
how to generate the site. I know roughly what the resulting pieces of
script should look like, and how the generated HTML should be
modified, but not enough Forrest-related configuration details to
know /where/ to make those changes...
Cheers
Andreas
Re: Next release - when?
Posted by The Web Maestro <th...@gmail.com>.
On Fri, Feb 29, 2008 at 2:18 AM, Vincent Hennebert
<vi...@anyware-tech.com> wrote:
> Jeremias Maerki wrote:
> > Looks good, Clay. Please commit it to Trunk. I'll take it from there and
> > make sure we can incorporate this in the 0.95 release. I'll also see
> > about switching to Forrest Trunk so we can use FOP 0.94/0.95 for the
> > PDFs.
It's in there...
> > On 29.02.2008 08:34:00 The Web Maestro wrote:
> >> Howdy Folks,
> >>
> >> I've got an update to the FOP web site for the 0.95 release:
> >>
> >> http://people.apache.org/~clay/fop_refactored_0.95/
>
> This is already looking better ;-)
>
> >> It's not too different from before, except for the 'Using FOP 0.95' &
> >> 'FOP 0.95 Features' menus in the nav for the Home tab, and I've
>
> I'm not sure those entries should be added to the Home tab. Basically
> they duplicate what's in the 0.95 tab, so that will add to the confusion
> IMO. The Home tab should remain dedicated to general informations about
> the project. What do others think?
I removed those links in the nav, and instead replaced them with a
link to a new Quick Start guide.
> Also, have you looked at disabling the menu auto-rolling feature? If
> not, I will ;-)
Fixing that should be as easy as adding this to the bottom of the
<extra-css> block in src/documentation/skinconf.xml:
<extra-css>
.menuitemgroup{ display: block;}
</extra-css>
I just added a change to skinconf.xml in svn. Unfortunately, the
change did not show in my local build. Nevertheless that's how Forrest
works.
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Next release - when?
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Hi,
Jeremias Maerki wrote:
> Looks good, Clay. Please commit it to Trunk. I'll take it from there and
> make sure we can incorporate this in the 0.95 release. I'll also see
> about switching to Forrest Trunk so we can use FOP 0.94/0.95 for the
> PDFs.
Just curious: do you mean the trunk/ branch of the Forrest repo (future
0.9)? Or the “trunk” version of the 0.8 branch? IIC up to now we had to
use the trunk version of Forrest 0.7 as auto publish wasn’t working with
the released version, so there seems to be trunks for every version
(0.7, 0.8, 0.9...).
> On 29.02.2008 08:34:00 The Web Maestro wrote:
>> Howdy Folks,
>>
>> I've got an update to the FOP web site for the 0.95 release:
>>
>> http://people.apache.org/~clay/fop_refactored_0.95/
This is already looking better ;-)
>> It's not too different from before, except for the 'Using FOP 0.95' &
>> 'FOP 0.95 Features' menus in the nav for the Home tab, and I've
I’m not sure those entries should be added to the Home tab. Basically
they duplicate what’s in the 0.95 tab, so that will add to the confusion
IMO. The Home tab should remain dedicated to general informations about
the project. What do others think?
Also, have you looked at disabling the menu auto-rolling feature? If
not, I will ;-)
<snip/>
Thanks Clay,
Vincent
--
Vincent Hennebert Anyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer FOP Development/Consulting
Re: Next release - when?
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Looks good, Clay. Please commit it to Trunk. I'll take it from there and
make sure we can incorporate this in the 0.95 release. I'll also see
about switching to Forrest Trunk so we can use FOP 0.94/0.95 for the
PDFs.
On 29.02.2008 08:34:00 The Web Maestro wrote:
> Howdy Folks,
>
> I've got an update to the FOP web site for the 0.95 release:
>
> http://people.apache.org/~clay/fop_refactored_0.95/
>
> It's not too different from before, except for the 'Using FOP 0.95' &
> 'FOP 0.95 Features' menus in the nav for the Home tab, and I've
> removed the 0.93 (although I haven't yet removed it from SVN). And
> it's built with Forrest 0.8.
>
> svn status
> M forrest.properties
> ! src/documentation/sitemap.xmap
> ? src/documentation/content/xdocs/0.95
> M src/documentation/content/xdocs/tabs.xml
> M src/documentation/content/xdocs/0.94/index.xml
> M src/documentation/content/xdocs/site.xml
> M src/documentation/content/doap.rdf
>
> NOTE: We've still got the 0.93/ directory in there, since I haven't
> taken the initiative to `svn delete` it yet.
>
> Here're the BROKEN items from the forrest STDOUT:
> X [0] knownissues.html
> BROKEN: Resource not found: cocoon://knownissues-raw-fotree.xml
> X [0] 0.95/releaseNotes_0.95.html
> BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/releaseNotes_0.95.xml
> (No such file or directory)
> X [0]
> 0.95/knownissues_overview.html BROKEN:
> /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/knownissues_overview.xml
> (No such file or directory)
> X [0] 0.94/changes_0.94.html
> BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/changes_0.94.xml
> (No such file or directory)
> X [0] /0.94/releaseNotes_0.94.html
> BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/releaseNotes_0.94.xml
> (No such file or directory)
> X [0] /0.94/changes_0.94.html
> BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/changes_0.94.xml
> (No such file or directory)
> X [0]
> /0.95/knownissues_overview.html BROKEN:
> /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/knownissues_overview.xml
> (No such file or directory)
> X [0] /changes.html BROKEN:
> /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/changes.xml
> (No such file or directory)
> X [0] /knownissues.html
> BROKEN: Resource not found: cocoon://knownissues-raw-fotree.xml
> X [0]
> /0.95/releaseNotes_0.95.html BROKEN:
> /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/releaseNotes_0.95.xml
> (No such file or directory)
> X [0] /0.95/changes_0.95.html
> BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/changes_0.95.xml
> (No such file or directory)
> X [0] compliance.pdf
> BROKEN: internal-destination or external-destination must be specified
> in basic-link
> X [0] changes.html BROKEN:
> /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/changes.xml
> (No such file or directory)
> X [0] 0.94/releaseNotes_0.94.html
> BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/releaseNotes_0.94.xml
> (No such file or directory)
> X [0]
> /0.94/knownissues_overview.html BROKEN: Resource not found:
> cocoon://knownissues-raw-fotree_0.94.xml
> X [0] 0.95/changes_0.95.html
> BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/changes_0.95.xml
> (No such file or directory)
> X [0]
> 0.94/knownissues_overview.html BROKEN: Resource not found:
> cocoon://knownissues-raw-fotree_0.94.xml
>
> --
> Regards,
>
> The Web Maestro
> --
> <th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
Jeremias Maerki
Re: Next release - when?
Posted by The Web Maestro <th...@gmail.com>.
Howdy Folks,
I've got an update to the FOP web site for the 0.95 release:
http://people.apache.org/~clay/fop_refactored_0.95/
It's not too different from before, except for the 'Using FOP 0.95' &
'FOP 0.95 Features' menus in the nav for the Home tab, and I've
removed the 0.93 (although I haven't yet removed it from SVN). And
it's built with Forrest 0.8.
svn status
M forrest.properties
! src/documentation/sitemap.xmap
? src/documentation/content/xdocs/0.95
M src/documentation/content/xdocs/tabs.xml
M src/documentation/content/xdocs/0.94/index.xml
M src/documentation/content/xdocs/site.xml
M src/documentation/content/doap.rdf
NOTE: We've still got the 0.93/ directory in there, since I haven't
taken the initiative to `svn delete` it yet.
Here're the BROKEN items from the forrest STDOUT:
X [0] knownissues.html
BROKEN: Resource not found: cocoon://knownissues-raw-fotree.xml
X [0] 0.95/releaseNotes_0.95.html
BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/releaseNotes_0.95.xml
(No such file or directory)
X [0]
0.95/knownissues_overview.html BROKEN:
/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/knownissues_overview.xml
(No such file or directory)
X [0] 0.94/changes_0.94.html
BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/changes_0.94.xml
(No such file or directory)
X [0] /0.94/releaseNotes_0.94.html
BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/releaseNotes_0.94.xml
(No such file or directory)
X [0] /0.94/changes_0.94.html
BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/changes_0.94.xml
(No such file or directory)
X [0]
/0.95/knownissues_overview.html BROKEN:
/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/knownissues_overview.xml
(No such file or directory)
X [0] /changes.html BROKEN:
/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/changes.xml
(No such file or directory)
X [0] /knownissues.html
BROKEN: Resource not found: cocoon://knownissues-raw-fotree.xml
X [0]
/0.95/releaseNotes_0.95.html BROKEN:
/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/releaseNotes_0.95.xml
(No such file or directory)
X [0] /0.95/changes_0.95.html
BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/changes_0.95.xml
(No such file or directory)
X [0] compliance.pdf
BROKEN: internal-destination or external-destination must be specified
in basic-link
X [0] changes.html BROKEN:
/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/changes.xml
(No such file or directory)
X [0] 0.94/releaseNotes_0.94.html
BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/releaseNotes_0.94.xml
(No such file or directory)
X [0]
/0.94/knownissues_overview.html BROKEN: Resource not found:
cocoon://knownissues-raw-fotree_0.94.xml
X [0] 0.95/changes_0.95.html
BROKEN: /Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.95/changes_0.95.xml
(No such file or directory)
X [0]
0.94/knownissues_overview.html BROKEN: Resource not found:
cocoon://knownissues-raw-fotree_0.94.xml
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Next release - when?
Posted by The Web Maestro <th...@gmail.com>.
On Jan 15, 2008 1:09 AM, Jeremias Maerki <de...@jeremias-maerki.ch> wrote:
> On 14.01.2008 15:21:00 The Web Maestro wrote:
> > I'll spend some more time working on the 0.8 upgrade. I'll also look
> > into implementing 'views' for the versioned docs. I guess things have
> > changed enough between 0.93 & 0.94 so we really do need 0.93 (although
> > when 0.95 is released we should be able to omit 0.94?)...
>
> You meant: omit 0.93, right? I'd always keep the last two stable
> releases.
Yes... 0.93 is what I meant.
> > If we're going to have releases around, should we put them under
> > 'Versioned Docs' (like Forrest) or do they deserve their own tabs?
>
> I'd prefer a tab per release but if the views approach requires a single
> tab for version docs, that's fine, too.
>
> Thanks for looking into this!
I've gotten the FOP site to build with forrest-0.8, but I have a few
of broken links (mostly having to do with release notes, changes, and
known issues--see the bottom of this msg).
I also had to exclude a few files from validation:
forrest.validate.skinconf=false
..
forrest.validate.xdocs.excludes=site.xml, knownissues.xml, news.xml,
0.93/knownissues_overview.xml, 0.94/knownissues_overview.xml
(I'll look into those issues and see what I can do to fix them)
Broken links (I assume we can ignore the 0.93-specific errors):
<broken-links>
<link message="Resource not found:
cocoon://knownissues-raw-fotree_0.94.xml"
uri="/0.94/knownissues_overview.html">
</link>
<link message="/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/releaseNotes_0.94.xml
(No such file or directory)" uri="0.94/releaseNotes_0.94.html">
</link>
<link message="Resource not found:
cocoon://knownissues-raw-fotree_0.93.xml"
uri="/0.93/knownissues_overview.html">
</link>
<link message="/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.93/releaseNotes_0.93.xml
(No such file or directory)" uri="0.93/releaseNotes_0.93.html">
</link>
<link message="/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/releaseNotes_0.94.xml
(No such file or directory)" uri="/0.94/releaseNotes_0.94.html">
</link>
<link message="/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.93/changes_0.93.xml
(No such file or directory)" uri="/0.93/changes_0.93.html">
</link>
<link message="Resource not found:
cocoon://knownissues-raw-fotree_0.93.xml"
uri="0.93/knownissues_overview.html">
</link>
<link message="Resource not found:
cocoon://knownissues-raw-fotree.xml" uri="knownissues.html">
</link>
<link message="/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/changes_0.94.xml
(No such file or directory)" uri="0.94/changes_0.94.html">
</link>
<link message="internal-destination or external-destination must be
specified in basic-link" uri="compliance.pdf">
<referrer uri="/compliance.html"/>
<referrer uri="compliance.html"/>
</link>
<link message="Resource not found:
cocoon://knownissues-raw-fotree_0.94.xml"
uri="0.94/knownissues_overview.html">
</link>
<link message="/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.94/changes_0.94.xml
(No such file or directory)" uri="/0.94/changes_0.94.html">
</link>
<link message="/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/changes.xml
(No such file or directory)" uri="changes.html">
</link>
<link message="/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.93/changes_0.93.xml
(No such file or directory)" uri="0.93/changes_0.93.html">
</link>
<link message="/Users/Shared/_WebDLs/_repos/apache/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.93/releaseNotes_0.93.xml
(No such file or directory)" uri="/0.93/releaseNotes_0.93.html">
</link>
</broken-links>
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Next release - when?
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 14.01.2008 15:21:00 The Web Maestro wrote:
> I'll spend some more time working on the 0.8 upgrade. I'll also look
> into implementing 'views' for the versioned docs. I guess things have
> changed enough between 0.93 & 0.94 so we really do need 0.93 (although
> when 0.95 is released we should be able to omit 0.94?)...
You meant: omit 0.93, right? I'd always keep the last two stable
releases.
> If we're going to have releases around, should we put them under
> 'Versioned Docs' (like Forrest) or do they deserve their own tabs?
I'd prefer a tab per release but if the views approach requires a single
tab for version docs, that's fine, too.
Thanks for looking into this!
> Clay
>
>
>
> On 1/14/08, Vincent Hennebert <vi...@anyware-tech.com> wrote:
> > Hi Clay,
> >
> > Sorry I have to agree with Jeremias here, I think the 0.93, 0.94, Trunk
> > tabs are ok. In fact the general structure of the website is more or
> > less ok to me. But I think the following could be improved:
> > - the skin looks a bit old now. Maybe upgrading to Forrest 0.8 (+1, BTW)
> > will improve things but anyway some work is needed in this area
> > I think. (Actually the Batik website doesn't look bad... ;-) )
> > At some point I guess we will need our own branding, rather than
> > relying on a default stylesheet.
> > - the behaviour of the menu on the left is a bit annoying: having to
> > click on a sub-menu to unroll it is a pain. Every time you switch to
> > another tab then switch back to the previous one, you have to unroll
> > the menus again. That's confusing I think.
> > Example: on the Home tab, click on 'Resources', then click on the
> > 'Version 0.94' tab, then go back to the 'Home' tab: you have to
> > re-click on 'Resources' to unroll it again.
> > I guess there is a parameter to disable that, and have flat menus by
> > default?
> > - there should be a short 'news' sections on the home page, to show that
> > the project is alive. Currently you have to click on 'Project' to
> > unroll the menu, then on 'News'. That's two superfluous clicks ;-) We
> > could leave older news in this section, and put the most recent ones
> > on the home page.
> > - many other pages could be reworked/updated/removed/merged, but the
> > previous points are the most important to me.
> >
> >
> > Jeremias Maerki wrote:
> > > Sorry to be a little late but I'm -1 on merging product documentation
> > > with project documentation again. I found that VERY nice to have because
> > > it gives us a cleaner structure. For me, the most important thing is to
> > > be able to simplify release management which is still somewhat too
> > > work-intensive. I really like how Forrest did it (although I still
> > > haven't checked how. I think they do something with views) and they do
> > > publish versioned docs. I like keeping the difference between Trunk and
> > > the latest stable release especially since we don't do releases every
> > > two or three months. It produces less confusion if we add new features
> > > in Trunk for those who use the latest release.
> > >
> > > +1 to switching to Forrest 0.8.
> >
> > <snip/>
> >
> > Vincent
> >
> >
> > --
> > Vincent Hennebert Anyware Technologies
> > http://people.apache.org/~vhennebert http://www.anyware-tech.com
> > Apache FOP Committer FOP Development/Consulting
> >
>
> --
> Sent from Gmail for mobile | mobile.google.com
>
> Regards,
>
> The Web Maestro
> --
> <th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
Jeremias Maerki
Re: Next release - when?
Posted by The Web Maestro <th...@gmail.com>.
I'll spend some more time working on the 0.8 upgrade. I'll also look
into implementing 'views' for the versioned docs. I guess things have
changed enough between 0.93 & 0.94 so we really do need 0.93 (although
when 0.95 is released we should be able to omit 0.94?)...
If we're going to have releases around, should we put them under
'Versioned Docs' (like Forrest) or do they deserve their own tabs?
Clay
On 1/14/08, Vincent Hennebert <vi...@anyware-tech.com> wrote:
> Hi Clay,
>
> Sorry I have to agree with Jeremias here, I think the 0.93, 0.94, Trunk
> tabs are ok. In fact the general structure of the website is more or
> less ok to me. But I think the following could be improved:
> - the skin looks a bit old now. Maybe upgrading to Forrest 0.8 (+1, BTW)
> will improve things but anyway some work is needed in this area
> I think. (Actually the Batik website doesn't look bad... ;-) )
> At some point I guess we will need our own branding, rather than
> relying on a default stylesheet.
> - the behaviour of the menu on the left is a bit annoying: having to
> click on a sub-menu to unroll it is a pain. Every time you switch to
> another tab then switch back to the previous one, you have to unroll
> the menus again. That's confusing I think.
> Example: on the Home tab, click on 'Resources', then click on the
> 'Version 0.94' tab, then go back to the 'Home' tab: you have to
> re-click on 'Resources' to unroll it again.
> I guess there is a parameter to disable that, and have flat menus by
> default?
> - there should be a short 'news' sections on the home page, to show that
> the project is alive. Currently you have to click on 'Project' to
> unroll the menu, then on 'News'. That's two superfluous clicks ;-) We
> could leave older news in this section, and put the most recent ones
> on the home page.
> - many other pages could be reworked/updated/removed/merged, but the
> previous points are the most important to me.
>
>
> Jeremias Maerki wrote:
> > Sorry to be a little late but I'm -1 on merging product documentation
> > with project documentation again. I found that VERY nice to have because
> > it gives us a cleaner structure. For me, the most important thing is to
> > be able to simplify release management which is still somewhat too
> > work-intensive. I really like how Forrest did it (although I still
> > haven't checked how. I think they do something with views) and they do
> > publish versioned docs. I like keeping the difference between Trunk and
> > the latest stable release especially since we don't do releases every
> > two or three months. It produces less confusion if we add new features
> > in Trunk for those who use the latest release.
> >
> > +1 to switching to Forrest 0.8.
>
> <snip/>
>
> Vincent
>
>
> --
> Vincent Hennebert Anyware Technologies
> http://people.apache.org/~vhennebert http://www.anyware-tech.com
> Apache FOP Committer FOP Development/Consulting
>
--
Sent from Gmail for mobile | mobile.google.com
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Next release - when?
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Hi Clay,
Sorry I have to agree with Jeremias here, I think the 0.93, 0.94, Trunk
tabs are ok. In fact the general structure of the website is more or
less ok to me. But I think the following could be improved:
- the skin looks a bit old now. Maybe upgrading to Forrest 0.8 (+1, BTW)
will improve things but anyway some work is needed in this area
I think. (Actually the Batik website doesn’t look bad... ;-) )
At some point I guess we will need our own branding, rather than
relying on a default stylesheet.
- the behaviour of the menu on the left is a bit annoying: having to
click on a sub-menu to unroll it is a pain. Every time you switch to
another tab then switch back to the previous one, you have to unroll
the menus again. That’s confusing I think.
Example: on the Home tab, click on ‘Resources’, then click on the
‘Version 0.94’ tab, then go back to the ‘Home’ tab: you have to
re-click on ‘Resources’ to unroll it again.
I guess there is a parameter to disable that, and have flat menus by
default?
- there should be a short ‘news’ sections on the home page, to show that
the project is alive. Currently you have to click on ‘Project’ to
unroll the menu, then on ‘News’. That’s two superfluous clicks ;-) We
could leave older news in this section, and put the most recent ones
on the home page.
- many other pages could be reworked/updated/removed/merged, but the
previous points are the most important to me.
Jeremias Maerki wrote:
> Sorry to be a little late but I'm -1 on merging product documentation
> with project documentation again. I found that VERY nice to have because
> it gives us a cleaner structure. For me, the most important thing is to
> be able to simplify release management which is still somewhat too
> work-intensive. I really like how Forrest did it (although I still
> haven't checked how. I think they do something with views) and they do
> publish versioned docs. I like keeping the difference between Trunk and
> the latest stable release especially since we don't do releases every
> two or three months. It produces less confusion if we add new features
> in Trunk for those who use the latest release.
>
> +1 to switching to Forrest 0.8.
<snip/>
Vincent
--
Vincent Hennebert Anyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer FOP Development/Consulting
Re: Next release - when?
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Sorry to be a little late but I'm -1 on merging product documentation
with project documentation again. I found that VERY nice to have because
it gives us a cleaner structure. For me, the most important thing is to
be able to simplify release management which is still somewhat too
work-intensive. I really like how Forrest did it (although I still
haven't checked how. I think they do something with views) and they do
publish versioned docs. I like keeping the difference between Trunk and
the latest stable release especially since we don't do releases every
two or three months. It produces less confusion if we add new features
in Trunk for those who use the latest release.
+1 to switching to Forrest 0.8.
On 14.01.2008 06:17:45 The Web Maestro wrote:
> On Jan 12, 2008 8:42 AM, The Web Maestro <th...@gmail.com> wrote:
> > On Jan 11, 2008 2:28 AM, Vincent Hennebert wrote:
> > > Refactoring the website? I've already been told several times that it
> > > was difficult to find its way on it. Last time I mainly rephrased a few
> > > sentences and removed broken links, but didn't do much more. And
> > > I didn't even touch the 'Development' tab which is progressively
> > > becoming out-of-date.
> > >
> > > Should I add that this is not a trivial task and that I'll have no time
> > > for that in the next couple of months? :-P
> >
> > I'd be happy to help with the web site. It's not perfectly clear to me
> > what else it needs, but I have some ideas. In a nutshell, 'Home'
> > should include 'user' related general stuff (all the stuff it has,
> > plus using FOP, upgrading, running, etc.--all the content from Version
> > 0.94). The Develop should contain all that it has, plus any 'FOP
> > Trunk' specific stuff. I don't what that is ATM... on first glance the
> > nav for 'Version 0.94' and 'FOP Trunk' are identical nav (except
> > V-0.94 has Release Notes, Changes & Known Issues).
> >
> > I imagine a good start would be to remove all tabs except for 'Home'
> > and 'Development'
> > - 'Version 0.93' just goes away
> > - 'Version Trunk' content moves to 'Home'
> > - I think 'FOP 0.94' just goes away. I don't see anything different
> > between the nav links in the 'FOP Trunk' and 'Version 0.94' tabs--if
> > there is, that content should move to 'Development'. I'll run `diff`
> > on the fop/0.94/ and fop/trunk/ directories to see what's different.
> > If anyone has an specific ideas on what's different, that'd help
> > greatly.
> >
> > We could retain the 'Home', 'Version xxx', 'FOP Trunk', 'Development'
> > tab structure, but I think less tabs may be better now that we've
> > retired 'Version 0.20.5', during which time, I believe the multiple
> > tab structure was necessary.
>
> Here's my first stab at a refactored FOP site:
>
> http://people.apache.org/~clay/fop_refactored/
>
> Of course, I'm open to suggestions.
>
> In a nutshell, here's what I did:
> - rm -R 0.93/
> - rm -R 0.94/
> - mv trunk/* ../
> - modify site.xml
> - change links to /0.94/* & /trunk/* to /*
> - check for broken links
>
> I'll likely need to do the above again when we're ready to deploy.
> Notice, I didn't do an `svn delete` on any of the above, since I'm
> hoping for feedback first. I'll likely do the SVN equivalents to the
> above when we're ready for primetime. If that time is now, I could do
> it fairly quickly.
>
> I'm also considering updating the Forrest build process to use Forrest
> 0.8 instead of Forrest 0.7.
>
> If anyone's interested, here're zip'd versions of the site.xml & tabs.xml files:
> http://people.apache.org/~clay/fop_refactored/site.xml.zip
> http://people.apache.org/~clay/fop_refactored/tabs.xml.zip
>
> Web Maestro Clay
> --
> Regards,
>
> The Web Maestro
> --
> <th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
Jeremias Maerki
Re: Next release - when?
Posted by The Web Maestro <th...@gmail.com>.
On Jan 12, 2008 8:42 AM, The Web Maestro <th...@gmail.com> wrote:
> On Jan 11, 2008 2:28 AM, Vincent Hennebert wrote:
> > Refactoring the website? I've already been told several times that it
> > was difficult to find its way on it. Last time I mainly rephrased a few
> > sentences and removed broken links, but didn't do much more. And
> > I didn't even touch the 'Development' tab which is progressively
> > becoming out-of-date.
> >
> > Should I add that this is not a trivial task and that I'll have no time
> > for that in the next couple of months? :-P
>
> I'd be happy to help with the web site. It's not perfectly clear to me
> what else it needs, but I have some ideas. In a nutshell, 'Home'
> should include 'user' related general stuff (all the stuff it has,
> plus using FOP, upgrading, running, etc.--all the content from Version
> 0.94). The Develop should contain all that it has, plus any 'FOP
> Trunk' specific stuff. I don't what that is ATM... on first glance the
> nav for 'Version 0.94' and 'FOP Trunk' are identical nav (except
> V-0.94 has Release Notes, Changes & Known Issues).
>
> I imagine a good start would be to remove all tabs except for 'Home'
> and 'Development'
> - 'Version 0.93' just goes away
> - 'Version Trunk' content moves to 'Home'
> - I think 'FOP 0.94' just goes away. I don't see anything different
> between the nav links in the 'FOP Trunk' and 'Version 0.94' tabs--if
> there is, that content should move to 'Development'. I'll run `diff`
> on the fop/0.94/ and fop/trunk/ directories to see what's different.
> If anyone has an specific ideas on what's different, that'd help
> greatly.
>
> We could retain the 'Home', 'Version xxx', 'FOP Trunk', 'Development'
> tab structure, but I think less tabs may be better now that we've
> retired 'Version 0.20.5', during which time, I believe the multiple
> tab structure was necessary.
Here's my first stab at a refactored FOP site:
http://people.apache.org/~clay/fop_refactored/
Of course, I'm open to suggestions.
In a nutshell, here's what I did:
- rm -R 0.93/
- rm -R 0.94/
- mv trunk/* ../
- modify site.xml
- change links to /0.94/* & /trunk/* to /*
- check for broken links
I'll likely need to do the above again when we're ready to deploy.
Notice, I didn't do an `svn delete` on any of the above, since I'm
hoping for feedback first. I'll likely do the SVN equivalents to the
above when we're ready for primetime. If that time is now, I could do
it fairly quickly.
I'm also considering updating the Forrest build process to use Forrest
0.8 instead of Forrest 0.7.
If anyone's interested, here're zip'd versions of the site.xml & tabs.xml files:
http://people.apache.org/~clay/fop_refactored/site.xml.zip
http://people.apache.org/~clay/fop_refactored/tabs.xml.zip
Web Maestro Clay
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Next release - when?
Posted by The Web Maestro <th...@gmail.com>.
On Jan 11, 2008 2:28 AM, Vincent Hennebert
<vi...@anyware-tech.com> wrote:
> Jeremias Maerki wrote:
> > I think we should start to plan the next release. How about targeting
> > the end of February or beginning of March?
>
> Seems good.
>
> > Without much thinking, the following items are on the table:
> > - Stabilizing tables.
> > - Stabilizing the image package once I've merged the brach into trunk.
> > - Verifying the AFP output works correctly.
> >
> > What else?
>
> Refactoring the website? I've already been told several times that it
> was difficult to find its way on it. Last time I mainly rephrased a few
> sentences and removed broken links, but didn't do much more. And
> I didn't even touch the 'Development' tab which is progressively
> becoming out-of-date.
>
> Should I add that this is not a trivial task and that I'll have no time
> for that in the next couple of months? :-P
I'd be happy to help with the web site. It's not perfectly clear to me
what else it needs, but I have some ideas. In a nutshell, 'Home'
should include 'user' related general stuff (all the stuff it has,
plus using FOP, upgrading, running, etc.--all the content from Version
0.94). The Develop should contain all that it has, plus any 'FOP
Trunk' specific stuff. I don't what that is ATM... on first glance the
nav for 'Version 0.94' and 'FOP Trunk' are identical nav (except
V-0.94 has Release Notes, Changes & Known Issues).
I imagine a good start would be to remove all tabs except for 'Home'
and 'Development'
- 'Version 0.93' just goes away
- 'Version Trunk' content moves to 'Home'
- I think 'FOP 0.94' just goes away. I don't see anything different
between the nav links in the 'FOP Trunk' and 'Version 0.94' tabs--if
there is, that content should move to 'Development'. I'll run `diff`
on the fop/0.94/ and fop/trunk/ directories to see what's different.
If anyone has an specific ideas on what's different, that'd help
greatly.
We could retain the 'Home', 'Version xxx', 'FOP Trunk', 'Development'
tab structure, but I think less tabs may be better now that we've
retired 'Version 0.20.5', during which time, I believe the multiple
tab structure was necessary.
Of course, there's likely to be content updates, as well as minor nav
changes needed (Changes, Release Notes, Known Issues), but that should
already be in 'FOP Trunk' content.
If anyone else has ideas, I'm open to them.
> I was also thinking about making this a beta release. With the major
> changes that we made we can't be sure that no regression has been
> introduced as well. The 0.94 release taught me that even if many bugs
> were fixed, users will stumble upon regressions and (rightly) complain
> about them.
>
> So, what about a 0.95 beta?
>
> Vincent
Like Chris, I think appending 'rc' as in fop-0.95rc would be better than 'beta'.
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Next release - when?
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Jeremias Maerki wrote:
> I think we should start to plan the next release. How about targeting
> the end of February or beginning of March?
Seems good.
> Without much thinking, the following items are on the table:
> - Stabilizing tables.
> - Stabilizing the image package once I've merged the brach into trunk.
> - Verifying the AFP output works correctly.
>
> What else?
Refactoring the website? I’ve already been told several times that it
was difficult to find its way on it. Last time I mainly rephrased a few
sentences and removed broken links, but didn’t do much more. And
I didn’t even touch the ‘Development’ tab which is progressively
becoming out-of-date.
Should I add that this is not a trivial task and that I’ll have no time
for that in the next couple of months? :-P
I was also thinking about making this a beta release. With the major
changes that we made we can’t be sure that no regression has been
introduced as well. The 0.94 release taught me that even if many bugs
were fixed, users will stumble upon regressions and (rightly) complain
about them.
So, what about a 0.95 beta?
Vincent
--
Vincent Hennebert Anyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer FOP Development/Consulting