I wanted to register something I may have told Fontana already, which makes this email an HBR cure as well:
I don't think that copyleft-next should release until we actually think it's appropriate for software developers to license software under it.
And, since this came up in the GitHub thread: I don't think a release isn't going to cause network effects, if that's what you're aiming for.
For that, I suggest instead we do a discussion draft model. Granted, in git, every revision is a discussion draft, but we could mark a specific git revision for which we're willing to "take comments on" for a longer period -- even as the master branch moves forward. Basically, we'd be making a commitment to the community that comments for an older version would be considered for longer, and we'd always answer questions on that revision, even if the answer is: "We changed that text to this in the current draft which we think addresses your issue".
What do you think of that idea?