One thing I would like to add to your request is for the developers to create a clear roadmap of some sort, for them selves and those of us that do beta testing, that states what has immediate priority and what will have attention after that is fixed.
There are so many bugs that really need attention (example: bug 204379) as Chris already mentioned, but since there is no way to determine what has priority, the developers them selves just seem to look at bugs at random. It almost seems as if some of them lost interest because there are so many things that have to be fixed.
I myself keep a list of bugs I really like to see fixed and try to help out as much as possible fixing it. Why isn't there one for the project in general.
One other danger of the total lack of some sort of "control" over the Camino project at the moment is that there are tons (dozens) of finished and semi-finishes patches lying around unattended waiting to be reviewed or even checked inn. Somebody should systematically review them, test them, comment on them, and check them in in order of priority.
If I would have been a programmer or had the capability or the ambition to program I would have done this a long time ago. But since my interest is purely artistic and passion for open source software I'm not even going to try to do another man/woman job.
Would it be that hard to just release a 0.8 version even if it wasn't perfect? Let's just do it this way we would help our project and we would even get some renewed attention, which we really need since people are starting thinks this project is dying again! And while we are at it, I'm going to to another request. Let's make v 0.9 the latest official release of Camino that support's 10.1. Let's create something to aim at.
On woensdag, aug 6, 2003, at 23:52 Europe/Amsterdam, Chris Casciano wrote:
I know we've had this thread recently, and its been stated that 0.8 is planned to be a big deal... both in features and in longevity (particularly on 10.1) and therefore there is still a bit of a wait to get things in order and that it will be worth it in the end.
There were a few objections, or call for an interim release in that thread (one by myself) but going through bugzilla I really felt the need to speak up more strongly.
However, I find triaging bug reports from users of 0.7 to be an increasing source of frustration. In terms of "Bugzilla" time, 5 months is really, really old and its difficult to do things like determine what bugs still exist, when in the last 5 months their dupe was marked fixed, etc. etc. I also think that the time between major releases will make tracking down regressions reported against 0.8 a huge pain in the ass. Bugs that old filed against other products (especially if they're still off the 1.0 brach) would more then likely get immediately invalidated.
My main fear is that without an interim release there isn't much to indicate what should be a current priority if the build of reports are still skewed to the old code base. Bugs like bug 208920 just don't get the attention they deserve (or the dupes/votes/cc's that would help them to get the attention) without the additional focus on a more recent code base.
—:0-0:— jasperhauser.nl/camino _______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
