RE: [phpBT-dev] RE: [Phpbt-users] Bug fixes or features?

[Steve D. - C. <ste...@cu...>]

> I'm thinking of "stability" in areas such as the database 
> schemas and the translatable strings.. 

Ok, I see.

> I have only used phpBT for about half a year, but looking at 
> the mail archives it is clear that it took over a year to go 
> from rc1 to final release of v1.0. Still, half the 
> translations from 0.9 had falled out together with support 
> for Oracle. 

(Just thinking out loud): A database abstraction layer might be nice.  

<snip>

> Yes, downloadable bundles would have to be offered at 
> strategic points.
> Testing could then be focused on the newly added/repaired 
> parts. Any chance you can help with a test plan? Something 
> simple with a bit of a guideline for new testers.

I am keen to see this project gather some momentum again.  Count me in :)
 
> I'm not too sure about forcing testers to register.. Wouldn't 
> that cut their number down from few to very few?

To be honest I have no idea on the numbers here, but given the paucity of
responses to this message, I'd argue that this is a moot point.  If we did
encourage a core group of testers to make themselves known, collaborate,
recognise "ownership" in certain areas, etc, that could really help the
development process.


> >  * Is the current development version safe and stable (and feature 
> > rich  and bug free) enough for a new release?
> > 
> > Yes, it is here.
> 
> I meant CVS head.

Whoops.  I must remember to read all the words in the sentence :)

 
> >  * What new features would you expect in a new release?
> > 
> > Should we set up an opinion poll for all users to contribute their 
> > thoughts to?
> 
> Sounds good. Ideas on how to handle it?

Well, I don't mind coding a PHP-driven questionnaire, but the real question
is how to structure the questions.

I'm not really an expert on that - designing objective questionnaires is
(apparently) a bit of an art. Anyone know anyone...?
 
> >  * What old bugs would you expect to be fixed in a new release?
> > 
> > I would expect all *known* old bugs to appear fixed in any new 
> > release, in addition to functional improvememts. :)
> 
> Of course. But the bugs that I know, the ones I can reproduce 
> and confirm, are not the same as the ones you know. There are 
> too many different Os:s, web servers, database servers, mail 
> servers, and web browsers (each one of those applications in 
> different versions and
> configurations) together with the php versions and 
> configurations, pear versions, and maybe more.. 

I don't really think there is a golden rule here. One way the testing could
be approached is risk-based: Use a forum, where developers express concerns
over the areas that they perceive currently have the greatest risk -
consequently, more testing effort can focus in that area.  

It really depends how much creative freedom developers are allowed - the
more they want, the more fluid testing must be (And the harder it is to
manage).  The more structured/controlled the dev process, good testing
becomes more manageable.

Can we have any more votes on this subject by other list recipients please?
:)

Thanks,
Steve