That feels like the best way to save the brand. Cut a Perl 7 release concurrently with the Raku v1 release, and just get on a regular schedule of incrementing t

That feels like the best way to save the brand. Cut a Perl 7 release concurrently with the Raku v1 release, and just get on a regular schedule of incrementing the version every 6 or 12 months. Edit: Okay, starting from the minor version instead of 7 sounds like an even better approach. Not exactly the same situation, but this reminds me of Angular. Angular 2 was a marketing debacle; the official stance of "Angular != AngularJS" is stubborn and nonsensical — any idiot can see that they're confusingly similar, and if they're supposed to be different then why is the first Angular release version 2.0.0 instead of 1.0.0? (I personally think they should've called it Circular.) In any case, I think the way they moved forward (with "Angular 2" no longer being a thing, except in reference to that specific release) was ultimately the best way to salvage the situation; given its recovery and growth since then I'd say Perl could take some lessons from it.