comment on

Sometime within the next month, the dev branch of KinoSearch, 0.3x, will displace the current 0.1x branch on CPAN. The branches, which split years ago, are neither API-compatible nor file-format compatible.

To accomodate the existing 0.1x user base, a fork of KinoSearch 0.165 has been released into a new namespace, KinoSearch1. Projects based on 0.165 should strongly consider switching to KinoSearch1 so that they do not break when KinoSearch 0.31 is released.

KinoSearch1 is file-format compatible with 0.165. The API is identical, so switching involves sweeping through a code base and replacing all instances of "KinoSearch" with "KinoSearch1". The distribution will only be updated for crucial bugfixes.

Looking forward, the main namespace, "KinoSearch", will return to being the unstable branch where where active development takes place. We expect to spin off an additional stable fork, KinoSearch3, in the near future, so that users who require strong backwards compatibility will be able to take advantage of the many significant advances offered by KinoSearch 0.3x.

--
Marvin Humphrey, KinoSearch developer

In reply to Stable fork of KinoSearch, "KinoSearch1" by creamygoodness

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.


Syntactic Confectionery Delight
	PerlMonks