...I believe Patrick's request for comments about such commitments, and concrete steps designed to meet them, are appropriate, sincere, serious and have already been productive.
in reply to Re^4: Perl 6: Managing breakages across Rakudo versions
in thread Perl 6: Managing breakages across Rakudo Star versions
You've got to be kidding me and all of us. A question was posted on stability policy for Rakudo. So then a question was asked if Rakudo is mature enough for a backwards compatible release which warrants a support/stability policy
What follows next is Perl 6 developers announcing there is no such thing like a backwards compatible release going to happen any sooner but they need a stability policy regardless. Ask why they would need one when there is no release that could even use it and answers go around arguing strange semantics of stability and support
The fact is you know it pretty well, you don't have a release with you for which you can promise any kind of stability whatsoever. You also know that the monthly releases and star releases of rakudo are basically 'works on my machine' trunk snapshot of the code repo zipped and uploaded.
The purpose of a monthly release is to have a stack of work finished and well supported without breakages to previous releases. With documentation and libraries shipped. Its not a ritual you need to execute in front of a deity every month.
You are not in need of a stability/support policy currently as you don't need it. You don't have a release that you can apply it to.