asterisk users - Apr 2004 - *** Hang on, we're on our way to 1.0

We're getting closer and closer to a 1.0 release of Asterisk. In order to
get there,
the development is now 110% focused on solving major, critical and crash bugs.
(And yes, if you follow the CVS updates, you'll see the impossible extra 10%
:-)

* YOU'RE NOT FORGOTTEN, BUT ON HOLD (WITHOUT ON-HOLD-MUSIC) *
If you're reporting other bugs, please don't be disappointed or require
immediate action
if nothing happens for a while. We need to focus in order to get to a 1.0. Those
reports
will not be ignored forever, but maybe for a short while. And if you get
questions or
requests for additional information from a bug marshal, please answer. The bug
marshals
are there to help collect all the information a developer needs in order to
locate
the problem and try to fix it.

This also applies to patches adding new functionality. We will consider them for
additions later on, but not now. So hang on to your patch report, refine your
code,
make sure the community tests it and remind us later if nothing happens. While
waiting
on hold, make sure you've submitted a disclaimer to Digium and confirm that
on the
bug report.

* THE GRAND PLAN *
The plan is first to release a 1.0 stable release. As soon as that is out, new
features
added to CVS head but not to stable will be ported into the stable CVS tree and
we're
going 1.1 as soon as that code is tested and considered stable.

After that, work will restart on adding new code, new functions and new
architectures.
There's quite a lot of work out there that will be very good additions to an
after-1.1
release of Asterisk, especially in the area of general functions that will add
major
flexibility both for applications and for how me manage configurations. Database
driven configuration handlers, embedded script interpreters and extensions to
various API:s. A lot of code that needs extensive testing before considered
stable.

* HELP US *
In order to help us move ahead, please spend some extra time testing the stable
CVS
source tree and help us solve problems. Visit the bug tracker, see if you
recognize some
of the unresolved problems  discussed there. Maybe you can help us with
additional information.

* REFERENCES *
Bug tracker: http://bugs.digium.com
CVS stable download instructions:
http://www.asterisk.org/index.php?menu=download

Regards,
/Olle

Olle E. Johansson wrote:
> We're getting closer and closer to a 1.0 release of Asterisk. In order 
> to get there,
> the development is now 110% focused on solving major, critical and 
> crash bugs.
> (And yes, if you follow the CVS updates, you'll see the impossible 
> extra 10% :-)
>
All sounds very exciting.. :)

Later..