William A. Rowe, Jr. wrote: > Colm MacCarthaigh wrote: > >> >> Sometimes things are marked experimental not because they are unstable >> in the sense that they contain a disproportionate ammount of bugs we >> have yet to notice, but rather are unstable in the sense that their >> behaviour or API may change in future versions - because the developers >> havn't quite got a feel for what might be optimal in the majority case >> yet. > > > And all the more reason they can't exist in stable. You *CAN'T* change > the API of any shipped module, because you are forced to bump the module
Of course you can only do this on trunk, but having it shipped as experimental gives you the chance of detecting such API shortcomings due to wider usage. Of course this can lead to situations where there is a dead end for an experimental module that cannot be solved in the stable branch. In this case this problem remains a known issue / limitation that will be fixed with the next stable branch. [..cut..] Regards Rüdiger
