comment on

...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.

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.

In reply to Re^5: Perl 6: Managing breakages across Rakudo versions by Anonymous Monk
in thread Perl 6: Managing breakages across Rakudo Star versions by raiph

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks