> This raises an interesting issue though. If bugs are meant to be reported
to the site and patches are also meant to be posted there, who is in charge
of keeping it up to date. I see that there are some bugs listed there that
are obviously fixed (PathAnimation.run() bug for eg.).
the bug/patch stuff is updated by the admins now and then (remember the
freetime issues :)
if things are posted to this mailinglist in moste cases it will get lost,
because we're not going thru all
the mails to see if we still need to fix a certain thing. We only browse
the patches/bug lists now and then.. and that's it.
> I'm not saying that having it on the site is a bad thing. I just find
that the site is often behind the latest code and still lists bugs that
don't exist anymore.
That's just how it works with these projects, remember that there are only 3
guys doing the major work here.. (that is development, faq's, tuts,
documentation, CVS maintaining, bug/patches) luckily Henrik and Cameron are
now doing the website mostly, so that's one thing less.
--------------------
now in reply to richard's mail (just got in :) :
> It might help if we actually use the functions like assigned to, priority,
etc that are available at source-forge.
> Then we would at least know if someone had taken it on themselves to look
into the bug, and that it was not being forgotten.
Read the above, there are only 3 active developers at this point (not
counting all those bug submissions into this list, cause we are still the
ones having to implement them and test them) I would be happy to assign
bugs to anyone else, but I don't think Jordi and Richard would like it :)
Developers should assign them to them selves, but that's something that's
not being done (there are about 13 names on the developers list !! guys!?)
No bugs are being forggoten, but a lot of bugs currently at sourceforge are
1. Mac related.. nuff said
2. Include huge examples that are usually causing the problems, not the
dynapi code. I requested this a few times to please keep your bug report as
short as possible (this means leaving out all the redundant code). Once
that's done the code usually works, because all other non-dynapi code was
removed.. I for one get very cranky having to debug other peoples code and
finding out that that code is causing the bug, not the dynapi.
and the patch area contains one patch..
> Also, I've seen so many fixes for all kinds of things pass through the
list without any comment, couldn't we have somewhere to > submit bugFIXES,
where they would be acknowledged, and kept for reference, until they are
tested and committed to CVS. Otherwise people are going to stop posting
their bugfixes, because it seems the rest just don't care.
that IS the patch area.. that's how we can look at fixes, and try and test
them out.. no need for another area to do that.. We have also requested many
times to NOT post bug fixes/patches/whatever to this list, we are just not
able to walk thru all these emails to see for bug fixes, that's what
Sourceforge is for, if people would simply take the time to visit
sourceforge, goto the patch/bug area, and add your patch/bug..
again, I'm the one speaking out on this one, something I don't like, but
sadly one of us has to do it.. so sorry for kicking people again
(especially you two), but in my personal opinion (not sure about the others)
people complain to much without really helping out. And 3 guys, working in
sparetime/freetime, can't do all the work that hundreds are
requesting/using, simple.
...
Pascal Bestebroer
[EMAIL PROTECTED]
http://www.dynamic-core.net
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
