Hi, > Seems like if we drop 3rd-party support, we should remove 3rdparty.xml > from the source package and update the RELEASE_NOTES.
-1 to that we would have to revert about a dozen fixes (via cherry picking) to remove 3rd party example support for Tour De Flex. > To say in the RELEASE_NOTES that there is support and then not support it on > the > flex.a.o version doesn’t feel right to me. It does support it we just not showing any 3rd party examples in the public Tour De Flex web site. I was trying to make a compromise to get the release out the door, but seems fairly clear that is not possible. > Or at minimum, mention in RELEASE_NOTES that 3rd-party support isn’t fully > implemented. This sounds like bike shedding to me. > In the “no RC” process we’re practicing, there is no new RC to cut and > upload to dist, or VOTE to cancel until this discussion reaches the point > where it is pretty clear there are enough PMC votes to ship. Which currently seem impossible so at this point I think I'm just going to give up on releasing it. Sorry to the 15,000 + users who use this and the 3rd party contributors who were waiting on the new release. The whole point of the release process is not to have consensus of the entire PMC, but to only have enough people who will vote +1, following this new no RC process I can't see how this point can be reached. Currently we have PMC members who are effectively blocking the release or a vote on it but are unwilling to help out in fixing with they see as issues. If we have these issues on a simple release like this I can't imagine this process working for the installer or the SDK. Thanks, Justin
