I am concentrating on maintaining the Drupal 7 version of Fivestar, and will shortly port it to Drupal 8. I have no experience with Drupal 6. Consequently I've had to put the Drupal 6 version of Fivestar into security maintenance mode i.e. no more ordinary fixes, and set open issues to "Closed (won't fix").

I'd be happy to apply patches provided by the community and commit them to the D6 branch. But I can't test them. If a volunteer tester were to come forward, I could revert the D6 version of Fivestar to normal maintenance.

The role would be: work with me to agree a set of patches to be applied from the issue list, then test the new 6.x-2.x-dev version after I've applied the fixes. Each fix would need to be tested to confirm that it worked, and more importantly regression test the module to confirm that there has been no collateral damage from the fixes. Then repeat as required, to install another set of patches. Work with me to decide when to cut a new release from the 6.x-2.x-dev branch.

Comments

duckydan’s picture

duckydan commented

I will help test it. The thing is, I'm not good at Drupal coding styles. However, I have lots of Drupal 6 experience and servers to test stuff on. As long as the patch was verified in so far as doing things "the Drupal way" with the right styles and stuff, I would certainly volunteer to install the patch and test functionality.

whiteph’s picture

whiteph commented

Great, thanks. I'm happy to review the code for correctness, style, and so on - and then apply the patch & create new dev release for you to test. I'll need to review all of the D6 bug reports that I Closed(won't fix) to find all with patches; I'll set them back to their original Needs Review/RTBC status so we can see what work we need to do.

From that point, how do you want to proceed? I apply all of them into a single dev release for you to test? Or one/few at a time? If not all at once, how will we select the ones to go first?

I don't have skin in the D6 game, so am happy to be guided by you. If I were driving, I'd do one at a time so that we're less likely to let bugs through and destabilise things. Re priority, I'd choose the critical ones first, ordered by patch simplicity. Then majors, etc.

I've got limited time for this over this coming weekend, then on vacation for a couple of weeks.

whiteph’s picture

whiteph commented
Status: Active » Closed (won't fix)

Sorry, Drupal 6 is end of life, and is no longer supported.