Subversion glitches

[Luigi Ballabio]

Hi all,
        there are still a couple of glitches left after the migration to
Subversion. Here they are:

a) due to non-ASCII characters in a few past commit messages, "svn log"
is currently broken. I can fix it, but I'll need to take the repository
down for a day or two. I might be able to do it during the next weekend
or the one after, which means that you won't be able to commit on those
Saturday and Sunday. Any objections?

b) the migration tool we used preserved the branches and tags we had in
CVS based on their name. This means that, for instance, the latest
releases of QuantLib, QuantLib-SWIG and QuantLibXL all live in
branches/R000400f0-branch while the latest releases of ObjectHandler and
gensrc (which had a different version number) live in
branches/R000200f0-branch.  Starting with next release, Subversion will
make it more convenient to branch the whole trunk; therefore, the
branches for all modules would live in the same directory.  Should I
also regroup past branches so that all modules in sync for a particular
release live in the same directory (which would make it easy to checkout
all related modules at the right versions, but would make it a bit more
difficult to find where any particular ObjectHandler release lives) or
should I leave the repository as it is (which would make it easy to find
any specific release of ObjectHandler, but would make it a bit more
difficult to find what QuantLibXL version it relates to?)  Opinions?

Later,
        Luigi


----------------------------------------

standards, n.:
The principles we use to reject other people's code.



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev

[Ferdinando M. Ametrano-3]

Hi Luigi

> a) due to non-ASCII characters in a few past commit messages, "svn log"
> is currently broken.
how can I see the problem? on which file?

> I can fix it, but I'll need to take the repository
> down for a day or two. I might be able to do it during the next weekend
> or the one after, which means that you won't be able to commit on those
> Saturday and Sunday. Any objections?
during week-ends it's ok for me

> Starting with next release, Subversion will
> make it more convenient to branch the whole trunk; therefore, the
> branches for all modules would live in the same directory.
I've appreciated that very much as it is my favorite approach.

>  Should I also regroup past branches so that all modules in sync for a particular
> release live in the same directory
In my opinion I would leave past branches the way the are. Maybe just
move old breanches in a subfolder, so that we could have a "clean"
branches (and tags) folder

thank you for all this SVN job you are taking care of

ciao -- Nando

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev

[Luigi Ballabio]

On Mon, 2007-04-16 at 11:15 +0200, Ferdinando Ametrano wrote:
> > a) due to non-ASCII characters in a few past commit messages, "svn log"
> > is currently broken.
> how can I see the problem? on which file?

>From the command line, execute "svn log" from within your working copy
of the trunk. Wait, let me see if Tortoise somehow hides the error...
no, it doesn't. With Tortoise, choose "Show Log" on the trunk and check
the "Show all" checkbox. It starts chugging along and it breaks after a
while. You'll still be able to see part of the log, though (as with the
command line.)

> >  Should I also regroup past branches so that all modules in sync for a particular
> > release live in the same directory
> In my opinion I would leave past branches the way the are. Maybe just
> move old breanches in a subfolder, so that we could have a "clean"
> branches (and tags) folder

It seems to me it's already as clean as it can be. Currently, they
contain only branches and tags for past releases, which I'd leave in the
corresponding folders.

> thank you for all this SVN job you are taking care of

No problem.

Later,
        Luigi


----------------------------------------

There are no rules of architecture for a castle in the clouds.
-- Gilbert K. Chesterton



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev

[Luigi Ballabio]

On Mon, 2007-04-16 at 11:15 +0200, Ferdinando Ametrano wrote:
> > Starting with next release, Subversion will
> > make it more convenient to branch the whole trunk; therefore, the
> > branches for all modules would live in the same directory.
> I've appreciated that very much as it is my favorite approach.
>
> >  Should I also regroup past branches so that all modules in sync for a particular
> > release live in the same directory
> In my opinion I would leave past branches the way the are.

Also, I might note (since I might not have been very clear) that
regrouping would follow your favorite approach as described above.

Later,
        Luigi


----------------------------------------

A programming language is low-level when its programs require attention
to the irrelevant.
-- Alan Perlis



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev

[Luigi Ballabio]

On Mon, 2007-04-16 at 10:36 +0200, Luigi Ballabio wrote:
> a) due to non-ASCII characters in a few past commit messages, "svn log"
> is currently broken. I can fix it, but I'll need to take the repository
> down for a day or two. I might be able to do it during the next weekend
> or the one after, which means that you won't be able to commit on those
> Saturday and Sunday. Any objections?

As you might have noticed, this is now fixed.

On a related note, do you think that it still makes sense to include the
ChangeLog in the release? With the switch to Subversion, we might just
point the interested user to, say,
<http://quantlib.svn.sf.net/viewvc/quantlib/trunk/QuantLib/?view=log>
(or the equivalent URL for the release branch) and make the distributed
tarball 200k slimmer.

Later,
        Luigi


----------------------------------------

Humphrey's Requirements Uncertainty Principle:
For a new software system, the requirements will not be
completely known until after the users have used it.



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev