Upcoming Releases, etc

[Arved Sandstrom <Ar...@chebucto.ns.ca>]

Hi, all

In order not to have too long a stretch between releases I am proposing one 
for the first week of February. This means it will likely happen on the 
weekend of 3-4 February.

Versioning:

I'd like to maintain the release tempo, but refactoring will mean that a 
number of releases will not reflect significant new or improved _user_ 
functionality, so I think we ought not to present them at the same revision 
level as 0.15 or 0.16. So I am suggesting that this next release be 0.16.1, 
and any subsequent ones which do not add major new user stuff will continue 
as 0.16.x. Bumping up by 1 in the revision level (our last place) indicates 
that these are maintenance releases.

If significant new user functionality is added then that would be 0.17.0 
(incrementing the minor release number).

Feedback:

Please let me know if the above release schedule and versioning works for 
you. Thanks.

Other Stuff:

1. Maintenance of Distribution on Locus

I'd like to identify distributions that are currently up on fop/dist that we 
do not want to support. Currently we have releases 12 through 16 available. 
This is not a space consideration; it is more a question of why are they 
there? One idea would be to have them in an "old" directory.

I am also going to review each one to ensure that we have a means of 
recovering that distribution. If I forgot to put an rtag in, which is 
possible, then I'm going to diff against a known point (a recent rtagged 
release), and CVS the diff. I will likely create a "recovery" folder in CVS 
for any stuff like this. Just in case.

So here I could use some feedback on how do we want to structure our dist 
directory. This includes the option of leaving it as is.

Regards,
Arved

Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Upcoming Releases, etc + PATCH: text-decoration

[Arved Sandstrom <Ar...@chebucto.ns.ca>]

At 11:07 PM 1/29/01 +0100, Karen Lease wrote:
>Hi all,
>
>Is anyone else working on Christian's patch? If not, I will try to do
>this before the weekend release, since I haven't done much except
>cogitate recently.

Hi, Karen

If you'd be so kind? Every so many days I'd see this message but not have 
the time to get into FOP mode, and feel a bit guilty about it. I appreciate 
it. In any case I promised to get some contributed design docs uploaded to 
CVS...

Appreciate it.

Arved

Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Upcoming Releases, etc + PATCH: text-decoration

[Karen Lease <kl...@club-internet.fr>]

Hi all,

Is anyone else working on Christian's patch? If not, I will try to do
this before the weekend release, since I haven't done much except
cogitate recently.

-Karen

Christian Geisert wrote:
> 
> Arved Sandstrom wrote:
> >
> > Hi, all
> >
> > In order not to have too long a stretch between releases I am proposing one
> > for the first week of February. This means it will likely happen on the
> > weekend of 3-4 February.
> 
> Could you please (or any other committer) have a look a my text-decoration
> patch sent about three weeks ago.
> My motivation for working on FOP is going down at the moment...
[snip]

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Upcoming Releases, etc

[Christian Geisert <Ch...@isu-gmbh.de>]

Arved Sandstrom wrote:
> 
> Hi, all
> 
> In order not to have too long a stretch between releases I am proposing one
> for the first week of February. This means it will likely happen on the
> weekend of 3-4 February.

Could you please (or any other committer) have a look a my text-decoration
patch sent about three weeks ago.
My motivation for working on FOP is going down at the moment...

> If significant new user functionality is added then that would be 0.17.0
> (incrementing the minor release number).

+1

> 1. Maintenance of Distribution on Locus
> 
> I'd like to identify distributions that are currently up on fop/dist that we
> do not want to support. Currently we have releases 12 through 16 available.
> This is not a space consideration; it is more a question of why are they
> there? One idea would be to have them in an "old" directory.

Maybe someone needs the version which supports the old draft or has build a
system which only works with a particular version of fop.
I think an "old" directory is a good idea.

> I am also going to review each one to ensure that we have a means of
> recovering that distribution. If I forgot to put an rtag in, which is
> possible, then I'm going to diff against a known point (a recent rtagged

You can create an rtag with a date.

> Regards,
> Arved

Christian

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Upcoming Releases, etc

["Randall J. Parr" <RP...@TemporalArts.COM>]

Arved Sandstrom wrote:

> Hi, all
>
> In order not to have too long a stretch between releases I am proposing one
> for the first week of February. This means it will likely happen on the
> weekend of 3-4 February.
>
> Versioning:
>
> I'd like to maintain the release tempo, but refactoring will mean that a
> number of releases will not reflect significant new or improved _user_
> functionality, so I think we ought not to present them at the same revision
> level as 0.15 or 0.16. So I am suggesting that this next release be 0.16.1,
> and any subsequent ones which do not add major new user stuff will continue
> as 0.16.x. Bumping up by 1 in the revision level (our last place) indicates
> that these are maintenance releases.
>
> If significant new user functionality is added then that would be 0.17.0
> (incrementing the minor release number).
>

Do you mean NEW functionality or CHANGED functionality? Maybe better stated as
changed access of functionality?

I ask because I am currently stuck using FOP 0.14 because I am using Oracle XSQL
which only supports FOP 0.14. Both people from Oracle and this list have
indicated they aren't planning to support newer FOP releases until the API
settles down and things are more stable.

As I read this and other threads on this list, the API, required parser, etc.
could change significantly from 0.16.0 to 0.16.1 but would be considered a
maintenance release because it didn't contain new user functionality.

Seeking clarification and enlightenment.
Thanks

R.Parr
Temporal Arts




---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Upcoming Releases, etc

[Fotis Jannidis <fo...@lrz.uni-muenchen.de>]

From:           	Arved Sandstrom <Ar...@chebucto.ns.ca>

> In order not to have too long a stretch between releases I am proposing one 
> for the first week of February. This means it will likely happen on the 
> weekend of 3-4 February.

What would you (means all;-) like to see changed in the docs.  
I have already noted the following: 

- include the description of the build process 
- new FAQ website
- bugzilla for Fop (which must be setup)
- new article on xsl:fo

 
> Versioning:
> 
> I'd like to maintain the release tempo, but refactoring will mean that a 
> number of releases will not reflect significant new or improved _user_ 
> functionality, so I think we ought not to present them at the same revision 
> level as 0.15 or 0.16. So I am suggesting that this next release be 0.16.1, 
> and any subsequent ones which do not add major new user stuff will continue 
> as 0.16.x. Bumping up by 1 in the revision level (our last place) indicates 
> that these are maintenance releases.
> 
> If significant new user functionality is added then that would be 0.17.0 
> (incrementing the minor release number).

Principally I think you are right. Maybe we could define the 
categories simpler: a release without any user functionality is 
released under a small revision level. In this case the next release 
has new user functionality: fo:footnote, font-variant="small-caps", 
italian hyphenation. 

 
 
> 1. Maintenance of Distribution on Locus
> 
> I'd like to identify distributions that are currently up on fop/dist that we 
> do not want to support. Currently we have releases 12 through 16 available. 
> This is not a space consideration; it is more a question of why are they 
> there? 
Because people have something setup that works with one of the 
older libraries and just want the old Fop jar.

> One idea would be to have them in an "old" directory.
> 
> I am also going to review each one to ensure that we have a means of 
> recovering that distribution. If I forgot to put an rtag in, which is 
> possible, then I'm going to diff against a known point (a recent rtagged 
> release), and CVS the diff. I will likely create a "recovery" folder in CVS 
> for any stuff like this. Just in case.
> 
> So here I could use some feedback on how do we want to structure our dist 
> directory. 

> This includes the option of leaving it as is.
+1 Nobody has problems with it; date and version number are 
informative enough. Best: No links pointing to one of the older 
version break. 

Fotis












> 
> Regards,
> Arved
> 
> Fairly Senior Software Type
> e-plicity (http://www.e-plicity.com)
> Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org