Hi all
welcome to quantlib-dev.
I hope this list will improve the cooperation between us.
I like to consider it as a place where I do not mind letting everybody know
that I'm not comfortable with some template machinery or the volatility
skew problem.
It's assumed that if you're a QuantLib developer you're also subscribed to
quantlib-users, especially since quantlib-users is a low volume mailing list.
I would expect that important commits wouldn't go without a comment here.
Two notes:
1) the snapshot of the CVS I published on
http://quantlib.org/snapshot.html
it's available on the CVS branch with the "R000300a2-branch" tag
The convention for the names of the CVS branches is Rxxyyzzln where:
R stand for Release
xx is the major number
yy is the minor number
zz is the minor-minor number
l can be a,b,f for alpha, beta, final respectively
n is an ordinal number
e.g. we're working towards the 0.3.0 release, there is a 0.3.0a2 branch,
while the trunk is 0.3.0a3
There should be no reason to work on 0.3.0a2, everybody is suggested to
work on the trunk unless some giant re-factoring is planned.
2) The first real issue we have is the QuantLib-Python platform-dependant
problem reported by Dirk. ASAP he or I will provide a summary of the
problem, so that we can try to solve it.
ciao -- Nando
Locked
