Jonathan Gold wrote:
> This is very exciting to hear.
> Most of these are things which have made me stay away from building production
> systems on Yaws (the general free-for-all even in the core code, tight coupling
> of random things, lack of docs and tests), and I had it on my list to ask you if
> there would be suport for my trying to articulate what I thought would be a good
> refactoring (maybe a "defactoring") release.
> Is your 2.0 already in the works and architected, or is this message really the
> very, very beginning?
: If things are still open, and if you or other Yaws users
> are interested, I'd love the chance to share some of my thoughts on how we might
> break down a 2.0.
I'd like to have some discussion here on the list, after that
I'd like things to get a bit more organized, where we/I actually
make up a list of items through some tool (http://trac.edgewall.org/)
to be done .... etc I.e. getting the Yaws project slightly more
professional than it is today.
There are so many companies today using Yaws in production (including
several of mine) where Q&A efforts are at very serious levels on the
company internal software and I feel that Yaws should ... well get
As of today, there are no known bugs in Yaws, all fine. But when we
add features we have no way to know that all the old stuff still works
since there is no regression test suite (my fault)
So share away, and then I'll get the next step organized.