Hi Barak, good to hear from you again.
Barak Sober wrote:
> I used to work with OSTA a couple of years ago and lately decided to
> catch up ...
> I saw that nothing new happened and realized that you are trying to
> issue a bug fix release.
> Well, I haven't got a lot of spare time... but from time to time I
> guess I can help a bit.
> I can write in C++, C# and a bit of Python.
> let me know how can I help
Best thing that you, or anyone, can do right now is to check through
the bug list on SourceForge:
- find a bug that interests you, or you feel should be fixed.
- post here to say that you'd like to look into it and ask if
anyone has more info or hints that aren't in the bug report.
- investigate it to the point that you know the actual cause of
the bug and can reproduce it at will, then document these facts
in the bug reporting system (in case you get run down by a bus)
- attempt to fix the code in as minimalist way as possible - there
should be no changes to default behavior and as little chance of
introducing instability as possible. If this isn't possible then
we are still interested, it's just the fix will go to the 1.5
branch rather than into the 1.4 releases.
- when you are happy with a fix, post here to say you have one and
I'll post back with info on how we can get it into CVS.
Cheers
/dan
--
Daniel Sutcliffe <Da...@Op...>
OpenSTA part-time caretaker - http://OpenSTA.org/
|
