On Wed, 2 Apr 2003, Flavio S. Glock wrote: > Some random thoughts (not necessarily my opinions): > > - we'd rather have Right than Stable.
For now, at least, yes. Later, no. For example, I'd consider the DateTime.pm API pretty stable at this point, since other people are already using it for their modules. Additionally, I've been release it with real (non-dev) version numbers. DateTime::Set (and friends) has only been released with dev version numbers (0.00_xx), so nobody should expect it to be stable yet. > - people _know_ the modules are unstable, but they don't _like_ > unstability. Tough cookies. This is a complex area (more complex than DateTime.pm) so coming up with a good API will take longer, I think. We have to balance between making complex functionality available and making simple things simple (kind of like Perl itself ;) > - API unstability delays projects. Yeah, but it's a necessary evil. > - we know more-or-less which methods are stable - this could be > documented. > OTOH, we might know which methods are _less_ stable - we could warn > the user. I'm not sure I know yet, that's the problem. > - API and "code" stabilize at different paces. Even if we have a stable > API, the code might be "not for production". Sure. > - at some point in the project, the API should try to keep itself > backwards compatible. Yes, around release 0.10 or so, I think we're committed. Before that, it can break as much as we want. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
