Thanks so much for the reply. I wanted to clarify that I READ day-in and day-out those typical "whats going on with this project? I HATE YOU" emails, and I really didn't intend mine to sound that way. I was really just curious about what was going on because I was new to the list (thanks for the tip abou subscribing to dev, I'll do that today!)
comments below:
Steve Raeburn wrote:
Also, perhaps the question you should be asking is, "How can *I* helpNope, I'm pretty sure my original question is what I wanted to ask :D
speed things up?"
Here's a couple of ideas:Very cool I didn't know this. After hitting bugzilla with those queries I'm REALLY stoked for 1.2.x (800 bug fixes? Wow -- note I realize bugs == features in bugzilla and not all of those were defects)
- Try out the Stuts 1.2.0 release and report back any problems, or (hopefully) report how stable and reliable it is for your applications. - Get the source code and try applying some of those patches that you've seen on the bug reports. Let us know whether they work for you.
There *has* been a first 1.2.x release, it's just not considered
production quality so we're aiming for a 1.2.1 release that hopefully
will be. Ted & Martin, particularly, put a lot of effort into getting
that release out, so it's not like there's nothing going on here :-)
Yes I see your point, sorry for drawing such rash conclusions.One of the misconceptions about supplying patches is that once a patch has been submitted, that's the end of the job. However, a committer still has to: 1) understand the original bug report and be able to reproduce the problem 2) apply the patch and *test* it for himself this can be quite a lot of work, even if you the patch works as advertised (not all do).
If you also go through that process and report back that it works for
you, the committers' confidence in the patch is increased. We still have
to do our own testing, but if your results match ours, then we can be
reasonably confident that the patch is good.
To address your points, specifically:Again, definately right. What triggered the questions was that I was using THAT list as a gauge to see when 1.2 was comming out, and for the last month (maybe more) that list has closed 1 bug and added 2... so I was like "what the heck's going on here with progress?". I had no idea about the already closed bugs, OR the dev lists... again, it was an uneducated comment on my part.
(a) they don't seem to be getting closed out for months at a time and
I don't think that's uncommon in any software project. Some things get
fixed quickly because they're easy or urgent; others take a while. Only
recently, I noticed a bug for Mozilla that has been open for 4 *years*
:-) That doesn't mean Mozilla is a bad product or isn't being actively
developed, just that they had other priorities.
Oh absolutely, I just figured with Struts being such a high profile project that there would be more people. So combined with my comment above, I thought most of the devs had gone onto something else, or stopped contributing... either way I was wrong and you are all working very hard.
bugs and(b) I see the same developer name(s) over and over again on these
So only a few people are doing all the work? And you wonder why
everything isn't done immediately!
This is my mistake, I should have checked the lists.
(slow)....(c) the communication over the bugs are not very verbal at all
I don't agree with you on this (or maybe I misunderstand). Communication
on the Struts project seems to be very good, to me. We have an excellent
user list, an active developer list and lots of communication via
bugzilla. Don't forget that some discussion about open issues may move
from bugzilla to the dev list, or the user list. It's worth monitoring
dev, if you're interested in where things are going.
Lastly, don't forget that nobody gets paid to develop Struts. We allWe ALL appreciate it, but this is also what probably all of us on this list, along with 20,000 other developers around the globe do on our weekends and for relaxaction and I think we would be thrilled if a community formed around any of our hobby projects (not to say Struts is a hobby, but you get the point).
have to work full-time jobs to make a living. Struts is what we do for
relaxation on the weekends :-)
Now everyone repeat after me, "The next version will be released 'WhenThat's fine by me, I almost went crazy trying to convince the NetBeans development team to adopt a release cycle like the Jakarta projects: release when the bugs are fixed. Then I finally realized that my efforts were equivalent to putting a saddle on a rock and trying to ride it in a race.
It's Ready'" ;-)
Again I really appreciate the reply, I'll get myself up to speed more approrpiately before asking sweeping questions like that in the future.
Best wishes, Riyad
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
