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 Rhett Aultman <Ra...@fcci-group.com> on 2002/11/27 06:36:52 UTC
Still on for freeze deadline?
Guys,
I finally got myself out from under my grad school apps long enough to employ a patch that helps nerf certain kinds of infinite loops in the maintenance branch of FOP. I'd like to see it go into the final release of the maintenance branch, but I don't know if I'll have time to give it a full test and build the diff before I have to go away for Thanksgiving to a town that doesn't have any Internet access of any kind (meaning I can't make the uploads). Is the Thanksgiving deadline for patches and whatnot strictly in effect? If so, I'll see about hauling buns to get this together.
--
Rhett.
Re: Still on for freeze deadline?
Posted by Oleg Tkachenko <ol...@multiconn.com>.
Rhett Aultman wrote:
> I have to go away for Thanksgiving to a
> town that doesn't have any Internet access of any kind (meaning I can't
> make the uploads).
Are such places still exist? :)
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by Ralph LaChance <Ra...@compuserve.com>.
At 06:30 AM 11/27/02, you wrote:
>I don't even know when Thanksgiving is .. asking Google .. ah
>it's on the fourth Thursday in November (i.e. tomorrow).
Well you might ask.
It is different in Canada (one month earlier) and then there
are the wags who suggest that July 4th, the anniversary
of America's independence is called Thanksgiving day
in the UK ;-)
' Best,
-Ralph LaChance
In theory, there is no difference between
theory and practice, but in practice there is.
(Someone wrote that, but I don't know who.)
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by Jeremias Maerki <de...@greenmail.ch>.
On 28.11.2002 17:15:46 Christian Geisert wrote:
> Jeremias Maerki wrote:
> > From your original plan we still have to finish the documentation stuff,
>
> Yes the documentation needs at least to be checked for old versions,
> errors etc. And it would be nice to document the ant task and new
> extensions.
I can do some of this as soon as I know where to do it. (See my other
mail)
> > right? Maybe we can also include the reorganized directory layout. But
>
> I would rather do this after the release.
ok.
> > that will take another week or two, I guess. Especially because I'd like
> > to leave Jörg a chance to voice his opinion. Until then I will be able
> > to include my tutorial.
>
> IMHO documentation changes (in contrast to code changes) are no problem
> after the release candidate.
You're right.
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: CVS changes (was Re: Still on for freeze deadline?)
Posted by Oleg Tkachenko <ol...@multiconn.com>.
Christian Geisert wrote:
> Won't this break old releases?
> For example checking out FOP with tag fop-0_20_3 then build.sh
> will probably fail.
I think you right :(
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
CVS changes (was Re: Still on for freeze deadline?)
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Oleg Tkachenko wrote:
> Jeremias Maerki wrote:
[..]
> Hack of the repository looks feasible, I did it once (one more to do is
> to modify parent CVS/Entry file, which lists all child directories as
> D/foo-dir////). Lets try on a non crucial directory first :)
Won't this break old releases?
For example checking out FOP with tag fop-0_20_3 then build.sh
will probably fail.
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by Oleg Tkachenko <ol...@multiconn.com>.
Jeremias Maerki wrote:
> Thanks, Victor and Peter. It all sounds a bit scary (I knew that before).
> Let's look at it the other way: Is there a downside to moving all the
> files on the client and checking in everything?
Lost history?
What do you guys think
> would be the best way to accomplish such a thing?
Hack of the repository looks feasible, I did it once (one more to do is to
modify parent CVS/Entry file, which lists all child directories as
D/foo-dir////). Lets try on a non crucial directory first :)
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by "Peter B. West" <pb...@powerup.com.au>.
Victor Mote wrote:
> Jeremias Maerki wrote:
>
>
>>Let's look at it the other way: Is there a downside to moving all the
>>files on the client and checking in everything? What do you guys think
>>would be the best way to accomplish such a thing?
>
>
> The downside to moving the files on the client & then checking in is that
> you have now disconnected the current files from their history.
>
> I don't know how much access we have to the cvs server, but, if we have
> enough, I think the preferred way to go is to 1) lock the repository down,
> 2) burn a copy of the repository onto a CD for backup & a permanent archive,
> 3) hack away at the repository until everything is as you wish, and 4)
> unlock the repository.
>
> However, the truth is that doing it the right "clean" way will be fine as
> well. I don't think we have any pressing needs to be greatly attached to the
> history. Peter has already documented how to leave an audit trail if you
> move in the repository & a similar thing could be done using the other
> method.
The '-m"comment"' option on 'cvs add' will set the descriptive text.
alt.design 8:04$ cvs add -m"THIS FILE IS BEING ADDED." junk
cvs add: scheduling file `junk' for addition
cvs add: use 'cvs commit' to add this file permanently
The '-m"comment"' option on the subsequent 'cvs commit' will set the log
text on the first revision of the added file.
alt.design 8:05$ cvs ci -m"It's little me" junk
RCS file: /tmp/pbw/cvstest/alt.design/junk,v
done
Checking in junk;
/tmp/pbw/cvstest/alt.design/junk,v <-- junk
initial revision: 1.1
done
alt.design 8:06$ cvs log junk
RCS file: /tmp/pbw/cvstest/alt.design/junk,v
Working file: junk
head: 1.1
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
THIS FILE IS BEING ADDED.
----------------------------
revision 1.1
date: 2002/11/28 22:05:55; author: pbw; state: Exp;
It's little me
=============================================================================
> Another issue to consider is that if you move the files in the repository,
> you need to worry about the dependencies in both branches at the same time.
> If you move them in your sandbox & check them in, I am pretty sure that you
> will need to either 1) only want them moved in one branch (probably not
> desirable), or 2) move them twice, once for each branch. Especially on the
> maintenance branch, you will want to be careful to get the new files tagged
> with the maintenance branch tag.
I don't think anyone here knows all of the implications of hacking the
repository. Safety first.
Peter
--
Peter B. West pbwest@powerup.com.au http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: Still on for freeze deadline?
Posted by Victor Mote <vi...@outfitr.com>.
Jeremias Maerki wrote:
> Let's look at it the other way: Is there a downside to moving all the
> files on the client and checking in everything? What do you guys think
> would be the best way to accomplish such a thing?
The downside to moving the files on the client & then checking in is that
you have now disconnected the current files from their history.
I don't know how much access we have to the cvs server, but, if we have
enough, I think the preferred way to go is to 1) lock the repository down,
2) burn a copy of the repository onto a CD for backup & a permanent archive,
3) hack away at the repository until everything is as you wish, and 4)
unlock the repository.
However, the truth is that doing it the right "clean" way will be fine as
well. I don't think we have any pressing needs to be greatly attached to the
history. Peter has already documented how to leave an audit trail if you
move in the repository & a similar thing could be done using the other
method.
Another issue to consider is that if you move the files in the repository,
you need to worry about the dependencies in both branches at the same time.
If you move them in your sandbox & check them in, I am pretty sure that you
will need to either 1) only want them moved in one branch (probably not
desirable), or 2) move them twice, once for each branch. Especially on the
maintenance branch, you will want to be careful to get the new files tagged
with the maintenance branch tag.
Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by Jeremias Maerki <de...@greenmail.ch>.
Thanks, Victor and Peter. It all sounds a bit scary (I knew that before).
Let's look at it the other way: Is there a downside to moving all the
files on the client and checking in everything? What do you guys think
would be the best way to accomplish such a thing?
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by "Peter B. West" <pb...@powerup.com.au>.
J.Pietschmann wrote:
> Arved Sandstrom wrote:
>
>> Considering that our new chief executive is Greg Stein, I'd be
>> surprised if
>> this isn't on the horizon. :-)
>
>
> Gosh! Can we have it before Christmas? :-)
2003?
Good to see you back, Joerg. Good holiday?
Peter
--
Peter B. West pbwest@powerup.com.au http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Arved Sandstrom wrote:
> Considering that our new chief executive is Greg Stein, I'd be surprised if
> this isn't on the horizon. :-)
Gosh! Can we have it before Christmas? :-)
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: Still on for freeze deadline?
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
Considering that our new chief executive is Greg Stein, I'd be surprised if
this isn't on the horizon. :-)
> -----Original Message-----
> From: J.Pietschmann [mailto:j3322ptm@yahoo.de]
> Sent: December 1, 2002 4:12 PM
> To: fop-dev@xml.apache.org
> Subject: Re: Still on for freeze deadline?
>
>
> Jeremias Maerki wrote:
> > Moving around directories on the server so we don't lose history on
> > files. See my proposal on directory structure reorganization, ex.
> > moveing src/org to src/java/org.
>
> Any chance to get the ASF interested in SubVersion?
> http://subversion.tigris.org/
>
> Apart from being accessible through firewalls, it allows moving
> files and directories, while being largely CVS compatible for
> everything else.
>
> J.Pietschmann
>
>
> ---------------------------------------------------------------------
> 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
Re: Still on for freeze deadline?
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Jeremias Maerki wrote:
> Moving around directories on the server so we don't lose history on
> files. See my proposal on directory structure reorganization, ex.
> moveing src/org to src/java/org.
Any chance to get the ASF interested in SubVersion?
http://subversion.tigris.org/
Apart from being accessible through firewalls, it allows moving
files and directories, while being largely CVS compatible for
everything else.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by "Peter B. West" <pb...@powerup.com.au>.
Jeremias Maerki wrote:
> Moving around directories on the server so we don't lose history on
> files. See my proposal on directory structure reorganization, ex.
> moveing src/org to src/java/org.
>
> On 27.11.2002 16:19:26 Peter B. West wrote:
>
>>Jeremias Maerki wrote:
>>
>>>BTW: Anybody around with experience in CVS surgery???
>>>
>>
>>Not really, but what do you want to do?
Jeremias,
Look at Sections 7.4 and 7.5 of the Per Cederqvist et al paper. From
that, I would say that the easiest and safest thing is simply move the
files. When you move them, make sure the descriptive next of the (now)
new file contains a loud note of the file's original location. Mind
you, I haven't experimented with the descriptive text of a new file in
CVS, as opposed to RCS, so I can't say that it work the same way.
Make sure you tag the tree before and after, and make sure no-one else
is trying to do commits while this is going on.
The above approach has no special dangers, and allows the complete tree
of previous releases to be recovered. The history (if the descriptive
text is working, and displays normally) will tel the enquirer where to
look for the prior history of the file.
It's certainly inconvenient for someone who wants to track down the
history, but it protects the primary requirement - the ability to fully
recover previous releases.
Peter
--
Peter B. West pbwest@powerup.com.au http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: Still on for freeze deadline?
Posted by Victor Mote <vi...@outfitr.com>.
Jeremias Maerki wrote:
> Moving around directories on the server so we don't lose history on
> files. See my proposal on directory structure reorganization, ex.
> moveing src/org to src/java/org.
>
> On 27.11.2002 16:19:26 Peter B. West wrote:
> > Jeremias Maerki wrote:
> > >
> > > BTW: Anybody around with experience in CVS surgery???
> > >
> >
> > Not really, but what do you want to do?
The only repository work I have done had to do with getting some RCS file
safely into one, which was a mild form of hacking. The O'Reilly book "CVS
Pocket Reference" has a section (p. 26) on "Hacking the Repository". It
urges extreme caution, backups, etc., then suggests simply moving the
directories around in the repository. It also warns that this is dangerous
when there are active sandboxes. Cederqvist also seems to indicate that a
simple move will work, Sec. 7.4.2, and points out that this will basically
break any checkouts of previous tags. In other words, trying to check out an
old tag will put the files in the /new/ location, which is inconsistent with
the references to it in other files.
If you're going to do this, it makes sense to do it while the release is
frozen, as everyone will want to get a new sandbox after the fact anyway.
Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by Jeremias Maerki <de...@greenmail.ch>.
Moving around directories on the server so we don't lose history on
files. See my proposal on directory structure reorganization, ex.
moveing src/org to src/java/org.
On 27.11.2002 16:19:26 Peter B. West wrote:
> Jeremias Maerki wrote:
> >
> > BTW: Anybody around with experience in CVS surgery???
> >
>
> Not really, but what do you want to do?
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by "Peter B. West" <pb...@powerup.com.au>.
Jeremias Maerki wrote:
>
> BTW: Anybody around with experience in CVS surgery???
>
Not really, but what do you want to do?
Peter
--
Peter B. West pbwest@powerup.com.au http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Jeremias Maerki wrote:
> From your original plan we still have to finish the documentation stuff,
Yes the documentation needs at least to be checked for old versions,
errors etc. And it would be nice to document the ant task and new
extensions.
> right? Maybe we can also include the reorganized directory layout. But
I would rather do this after the release.
> that will take another week or two, I guess. Especially because I'd like
> to leave Jörg a chance to voice his opinion. Until then I will be able
> to include my tutorial.
IMHO documentation changes (in contrast to code changes) are no problem
after the release candidate.
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by Jeremias Maerki <de...@greenmail.ch>.
From your original plan we still have to finish the documentation stuff,
right? Maybe we can also include the reorganized directory layout. But
that will take another week or two, I guess. Especially because I'd like
to leave Jörg a chance to voice his opinion. Until then I will be able
to include my tutorial.
BTW: Anybody around with experience in CVS surgery???
On 27.11.2002 12:30:36 Christian Geisert wrote:
> Rhett Aultman wrote:
> > Guys,
> >
> > I finally got myself out from under my grad school apps long
> > enough to employ a patch that helps nerf certain kinds of
> > infinite loops in the maintenance branch of FOP.
> > I'd like to see it go into the final release of the maintenance
>
> [..]
>
> > Is the Thanksgiving deadline for patches and whatnot strictly
> > in effect? If so, I'll see about hauling buns to get this together.
>
> Huh? Never heard of a Thanksgiving deadline.
> I don't even know when Thanksgiving is .. asking Google .. ah
> it's on the fourth Thursday in November (i.e. tomorrow).
>
> My plan was to apply one last small patch later today and
> then ask for a freeze.
> As much as I would like to finish this release the patch
> should IMHO make it into this last maintenance release.
> Other opinions?
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Still on for freeze deadline?
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Rhett Aultman wrote:
> Guys,
>
> I finally got myself out from under my grad school apps long
> enough to employ a patch that helps nerf certain kinds of
> infinite loops in the maintenance branch of FOP.
> I'd like to see it go into the final release of the maintenance
[..]
> Is the Thanksgiving deadline for patches and whatnot strictly
> in effect? If so, I'll see about hauling buns to get this together.
Huh? Never heard of a Thanksgiving deadline.
I don't even know when Thanksgiving is .. asking Google .. ah
it's on the fourth Thursday in November (i.e. tomorrow).
My plan was to apply one last small patch later today and
then ask for a freeze.
As much as I would like to finish this release the patch
should IMHO make it into this last maintenance release.
Other opinions?
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org