On 3/6/06, Pip Stuart <[EMAIL PROTECTED]> wrote: > use even minor versions to suggest stability and odd > to imply unstable / experimental development branches.
All releases are supposed to be "stable" until proven otherwise :) SVN is "unstable" and CPAN is "stable". You want to be bleeding edge, use SVN. You want to build a project against SDL_perl, use CPAN. People who are packaging SDL_perl for a downstream distro should use CPAN. Those developing applications for SDL_perl should probably use CPAN as well. If you are developing a new application and are adding features to SDL_perl, then obviously you need to use SVN. When you've tested your SVN contributions sufficiently, we'll release a new minor version. And you can tell everyone to use that version number. What is important is to know when an API change breaks your application. For every application there will be some range of version numbers which will work. Whether or not those versions are "stable" or "unstable" all depends on how much people submit to SVN. SDL_perl's API has been very stable for the past few years. Dave -- "The universal aptitude for ineptitude makes any human accomplishment an incredible miracle" -Stapp's Ironical Paradox
