Candy,
I'm afraid there's no best way. Unfortunately, we never had a
decent issue manager in place. It will be a prerequisite when we
start making plans for some kind of 2.0 version...
In the meantime, there's not a lot going on. Looking at the
subversion logs (or subscribing to the quantlib-cvs mailing list) will
show you what code is committed--and as I said, there's not a lot of
traffic. If you want to work on something in particular, just write
to this list and say what you're going to do.
Later,
Luigi
On Tue, Aug 28, 2012 at 5:12 PM, Candy Chiu <
[hidden email]> wrote:
> Luigi,
>
> What's the best way to keep track of the items being worked on? Thanks.
>
> Candy
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev
Locked
