Hi all,
this year seems a nice year to release version 1.0. Except for one or
two things that still need changing (see below) I'd go for it with what
we currently have in the repository. My idea was to call it 0.9.9 and
release it as a kind of beta for 1.0. In fact, I'd either create a 1.0
release branch at the same time that I create the 0.9.9, or use the same
branch for both. Once 0.9.9 is released, I'd fix reported bugs (if any)
and release 1.0 after a short while (say, one or two months.)
As for 0.9.9, I'd release it as soon as it's in shape. The couple of
things that are still missing before we can freeze the interfaces are:
- inflation curves need to include seasonality. According to Chris
Kenyon, this will be done shortly---correct, Chris? Any schedule?
- we should clean up the OptionletStripper1/OptionletStripper2 classes
(are they all still needed? Can they have better names?) The same goes
for SwaptionVolCurveX. Nando, any thoughts on these ones?
As I said, at 0.9.9 and onward the interfaces would be frozen---meaning
that client code that compiles against 0.9.9 should compile without
modifications against 1.0 and later releases. This means that adding
stuff to existing classes is ok, removing or renaming it is not (unless
it's private methods or data members.)
Later,
Luigi
--
A child of five would understand this. Send someone to fetch a child of
five.
-- Groucho Marx
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev
Locked
