Push cvs to 4.7

Quiz answers of "0" get ignored:
http://drupal.org/node/88686

this can be easely fixed ; the trick was said (the bug is because the test is done using empty() instead of != '' : for PHP 0 and '0' are empty values too..) If need, if post the patch file tomorrow.

Feedback options not supported: (we might want to consider just hiding the interface option for now)
http://drupal.org/node/88678

you were closed to it Sean. your new dancing function can help in that direction ;)

Review and rewrite help text:
http://drupal.org/node/88905

And finally, the documentation needs updating:
http://drupal.org/node/73607

maybe people with good english can help? i know they are some people who are reading the issues and are also using cvs code... come on ladies and gentlemen :)

Could someone please just tag the current head as 4.7.x-1.x-dev, and commit the code in http://drupal.org/node/114885 as 5.x-1.x-dev? It's *so* much easier to work on tags, and it makes it easier for us to provide new code.

Something like...

cvs -d :pserver:myusername@cvs.drupal.org:/cvs/drupal-contrib co contributions/modules/quiz
cd contributions/modules
cvs tag -r DRUPAL-4-7 quiz
tar xzvf /tmp/quiz-5.tgz
cvs tag -r DRUPAL-5 quiz

go to http://drupal.org/project/quiz
select add new release
add releases for 4.7 and 5.x

Thank you.

It's branch, not tag. :P

I'd like some more reviews of the new 5.x version before I commit it.

Also, the reason I've been holding off making releases for quiz module because I don't have time to maintain it atm, and the only other person I'd be comfortable handling maintainer privileges to at this point (Sean B. Fuller) doesn't either. Creating releases means that more people will start downloading the module, using it on their site, and expecting it to work. There are still many bugs, as you can see.

So the best way to ensure that it's branched faster is to help by submitting patches back to clean up various issues in the bug queue. Once that's done, it'll be much easier to branch the code and accept new features.

Having 4.7 and 5.x dev branches would nonetheless make things easier for testers and developers, you don't have to make releases.

Hey webchick. I think I understand where you're coming from.

However, I don't think anyone is asking so much for a 'release' as a dev-branch for 5.x? There are a few good reasons for this:

1) The assertion that creating a 5.x branch will encourage more downloads may be true, but a) The warning that exists on the Quiz project page, regarding being in development, still holds, b) Those bugs are already out in the open, have been documented - perhaps they could be shifted to the 5.x branch (and summarily processed) when the time is right.

2) Increasingly over time, developer interest in working on a 4.x module will naturally wane. For example, I don't really have any interests in working through 4.x dev cycles (patching, reviewing, testing and such) because, well, quite simply, that's not the Drupal version I need it for.

3) Consequently, developers working on 5.x don't have the proper dev. context (issue system and such) to participate within. You can't post a patch for the 5.x version in the issue system, because there is no entry for that branch, and the changes will likely not be applicable to 4.x (HEAD) and would be prone to cause error.

Anyway, don't mean to sound like an expletive :), just trying to figure out the best way to proceed. I did post some thoughts here

http://drupal.org/node/114885#comment-205112

on trying to get the 5.x version to a point where it may be ready for a branch. Would appreciate any thoughts. Cheers.

done a while ago now