Even if we are not testing, just marking issues CNW because the patch lo longer applies would be terrific. We already have an issue closing script which is able to change issue status.

Comments

hunmonk’s picture

hunmonk commented
Status: Active » Postponed (maintainer needs more info)

i'd really like to hear from rok, regarding the stability of the patching code on testing.drupal.org. the last time i checked, it was still returning too many false negatives.

Rok Žlender’s picture

Rok Žlender commented

ATM we only test if patch applies example http://testing.drupal.org/node/12625 or http://testing.drupal.org/node/12624 I don't expect any false negatives here.

hunmonk’s picture

hunmonk commented
Priority: Critical » Normal
Status: Postponed (maintainer needs more info) » Postponed

i don't want to write more custom code to add comments to issues. the issue closing code in project issue needs to be abstracted to provide a general mechanism for this: http://drupal.org/node/271216

boombatower’s picture

boombatower commented

I have been working with solotan and I believe #271216: abstract comment creation functionality is almost ready. Once it is complete we need to decide how to expose the API for remote calling. Some sort of menu callback, but do we need any sort of anti-spam code or is that already delt with?

Edit: there is a patch now, just wait for review.

boombatower’s picture

boombatower commented
Status: Postponed » Closed (duplicate)

#325481: Mark issues as CNW when most recent patch has failed testing