Subject: [ecasound] ecasound 2.0 and beyond
From: Kai Vehmanen (email@example.com)
Date: Sun Feb 25 2001 - 22:31:24 EET
Now that ecasound has a cleaner MIDI-subsystem implementation (although
with not that many features/services), I don't see a reason for a separate
1.10 release. In other words, I'd like to get ecasound 2.0, the next
stable release, out in a few weeks. The initial timetable is...
01.03.2001 ecasound feature freeze
xx.03.2001 silent ecasound 2.0 release for packagers a few days ahead of
the public announcement
xx.03.2001 ecasound 2.0 release
xx.03.2001 qtecasound 0.2.0 and ecawave 0.4.0 stable releases that are
based on the new ecasound
xx.04.2001 ecasound 2.1dev1 released (... and development continues)
Now the important thing here is freezing the library interfaces. This
means that you can develop ECI and "native" (like qtecasound and ecawave)
applications based on ecasound 2.0.x. All 2.0.x releases will be both
source and binary compatible.
Another thing is how stable the 2.0 release will be. As I don't have any
extra time to spend on testing, I wouldn't be suprised if 2.0 turned out
to have serious bugs. But this is not really that big of a problem, we'll
just release 2.0.1 and all is well. ;)
Of course, if you've encountered a problem/bug in ecasound, now is a very
good time to report it! A short known-bugs list is at
Btw; It's likely that I won't make a separate CVS-branch for the stable
tree, but instead, have a local stable tree (for possible 2.0.1, 2.0.2,
... comments, suggestions?
-- . http://www.eca.cx ... [ audio software for linux ] /\ . . http://www.eca.cx/aivastus ... [ aivastus net radio ] /\ .
-- To unsubscribe send message 'unsubscribe' in the body of the message to <firstname.lastname@example.org>.
This archive was generated by hypermail 2b28 : Sun Feb 25 2001 - 21:45:00 EET