Drupal 5: Quiz 5.x-2.x-RC1 has been removed

Events happening in the community are now at Drupal community events on www.drupal.org.
mbutcher's picture

I've never done an UNrelease message before....

The short version: I have just removed Quiz 5.x-2.0 RC1 from the list of downloads. For D5, use Quiz 5.x-1.1. Only the D6 branches are currently under development. All D5 development as stopped.

I inherited the Quiz code base relatively recently, and have been working to get a D6 port of this venerable module released and polished.

Quiz 2.0 underwent a lot of development in the 5.x branch before the D6 port began. But the D5 version was not ready for release. Unfortunately, I don't have the time to fix the 5.x branch, and it is simply too buggy to use on a production system (as I have learned from reading the issue queue).

So if you are on Drupal 5, you are advised to either upgrade to 6 or stay with the Quiz 5.x-1.1 module (which is unsupported, but stable).

Going forward, Quiz will not enter the RC phase until all open bugs marked "normal" or "critical" are resolved, downgraded to "minor", or dormant (e.g. "needs info" with no response in a while). We are there with the Drupal 6 version. RC 1 was released with no open bugs. RC 2 is waiting for just a couple more to be closed. And we'll keep up this process until bugs stop trickling in. Then a final release will be issued.

Quiz 6.x-3.x is open for development. If you have a new feature in mind, please file it as a 3.x feature request. No new features are going into the 6.x-2.x branch. It is bugfixes only from this point on.

Comments

Stable is a relative term...

westwesterson's picture

Stable is a relative term... Quiz 1.1 was plagued with just as many bugs probably more fyi

Implications

mbutcher's picture

True, but the real consideration is this: An rc implies that a release is immanent and that we will continue fixing it till it is ready. I can't work on a 5.x release, and from the issue queue, it is clear that expectations are otherwise.

Removing the release clears that up.

Implications

mbutcher's picture

True, but the real consideration is this: An rc implies that a release is immanent and that we will continue fixing it till it is ready. I can't work on a 5.x release, and from the issue queue, it is clear that expectations are otherwise.

Removing the release clears that up.

Quiz

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week