> I'm just curious when this bug will be fixed. It was reported months
ago.
> I've got three more months left on my support contract and don't
think I'm
> going to renew if it takes six months for the Declude dev team to fix one
> bug. Sorry yall, but my confidence is waning.
I think it might help if I comment here. I believe this was a
"necessary evil" -- kind of like getting a tooth removed, it's no fun,
but it needs to be done.
As many of you know, about 6 months ago I stopped working full time for
Declude. I'm still involved, just not nearly to the extent that I was
before. Before that point, I was essentially in charge of the Declude
source code. Part of the transition of me leaving was to get the
development team to take that on.
That transition worked very well, except for one flaw. And it was a
major one, which I recognized and understood. I was faced with a
choice: either push until the problem was fixed (in which case I would
not be around to handle the next problem), or let the team handle it on
their own (which gives them the opportunity to learn from their
mistake). This one flaw caused most (if not all) the issues that have
been discussed here with the 2.x releases. Making matters more
difficult, the issues were not easily reproducible.
Fortunately, the flaw eventually exposed itself, and has been addressed
and removed. There's still a bit more work to be done, however, and
some more testing to do. But with that flaw out of the way, it should
be smooth sailing from here. This whole process has helped give the
team the experience they need to be able to recognize and deal with
future issues that come up much more quickly. And as I mentioned in a
post a few days ago, I think that you will be pleased with the next release.
-Scott
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
