Granted.
But here's another question.
Why did you not develop your own branch independently of DynAPI.
If you are coding a largescale commercial site, you should have absolute control over
the code.
With an opensource distro, you don't.
I did exactly this with dynAPI1 ways back, as stuff was not working etc.
> >So now the only interesting question remaining, as I see it, is:
> >Who is more stupid? The developer committing an unstable release, or the
> developer committing _to_ an unstable >release (even if neither one knows
> it's unstable).
>
> How about the person who packedges it and send's it off as a 'stable
> release' ?
>
> Nevermind.
>
> For the very lst time.
> I am sorry. I was upset and said things I sould have not.
>
> We (as a group) made a decision to follow a standard and have faild to do so
> (as seems the norm these days for this group).
>
> Management knows fully well that this is an opensource project developed by
> people who are volunteering their time.
> I just don't think it's too much to check out the examples before calling
> something a 'stable release'.
>
> Not only that, I am still waiting for the next 'stable release' so That I
> can show them some sort of forward motion.
>
> This project is intended to make a coder's life easier.
> Most of the people who have gotten invloved in this project did so for their
> own good: to be able to produce quick, cross-browser solutions.
> I would think that the people using this product in the real world would
> have some interest in have the DynAPI somewhat resemble a real tool.
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
