Hi, >>> [permissions conflict on dist ‘NEXT’] >>> From past experience I’m guessing Damian would be ok giving me co-maint. >> >> I just did. :-) > > Thanks for that Damian! > > I’ve just done a developer release of NEXT, given it’s a core module. In > addition to hiding “EVERY” from PAUSE, I updated the Makefile.PL to follow > recent conventions for the dist metadata, and fixed a couple of pod issues on > RT. > > I’ll wait 8 days, and if CPAN Testers is all green, then I’ll do a > non-developer release and let P5P know. Once that’s done, I’ll schedule > deletion of old releases, and then drop the permissions on EVERY.
There was also an indexing issue, with “NEXT” not being indexed (there was an RT for that). With Andreas’s help, that is now resolved. The 0.66 release had the change needed, and I fixed some of the outstanding doc RT issues; it reported all clear on CPAN Testers. With 0.67 I addressed one more doc issue, and so far it’s testing clean. The doc now directs people to look at next::method in mro as well. I’ve dropped DCONWAY’s and FLORA’s permissions on package EVERY, and have schedule deletion of the old releases of NEXT from their author directories. I’ll wait another week before emailing P5P. Cheers, Neil
