[wp-hackers] User Feedback and Testing

[Ryan Boren]

On Mon, 2006-01-02 at 10:52 +0000, David House wrote:
> > 02/01/06, John Joseph Bachir <jjb at ibiblio.org> wrote:
> > But there _could_ be feature development. There are probably a good
> > handful of developers with spare cycles who don't have any bugs to squash
> > and would like to work on what will become 2.1 (or whatever is released in
> > 6 months).
> 
> Everyone has bugs to squash as long as there are bugs around.
> WordPress is still small enough such that most devs are familiar with
> most of the system; anyone can fix bugs. Hence, as Ryan pointed out,
> all our efforts at the moment are focused on bugfixing. After a
> designated period of time, we'll move into new feature development.
> 
> But before this thread dies I'd like to bring up the points of Owen's
> email in the first place.
> 
> 1. Our testing isn't good enough.
> 2. It would be nice to have a release schedule.

I'm fine with a release schedule.  I think schedules and milestone
announcements draw in contributors.

Something like:

http://live.gnome.org/TwoPointThirteen
http://developer.kde.org/development-versions/kde-3.5-release-plan.html

Those schedules include string and UI freezes so that i18n and doc teams
have time to finish.  Note that those teams are involved during the
entire development cycle.  With WP, everyone waits for the release to
drop and then they jump on it.  We need involvement throughout, and we
need a schedule so that everyone knows how long they can
procrastinate. :-)

Ryan