| |||||||||||||
LinuxConf.eu: Documentation and user-space API designLinuxConf.eu: Documentation and user-space API designPosted Sep 5, 2007 6:29 UTC (Wed) by mkerrisk (subscriber, #1978)In reply to: LinuxConf.eu: Documentation and user-space API design by lacostej Parent article: LinuxConf.eu: Documentation and user-space API design
Could it help to state that a particular system call released in stable n release isn't considered stable until n+2 ? and that we allow breaking it in that time-frame ? That's probably just pushing the problem...This is an idea that has been getting some consideration. It might help matters a little, but it causes other types of pain (e.g., a new interface becomes moderately used by a number of apps, but then a critical design issue causes a interface change at n+2; or, userland developers refrain from using an interface until n+2, because they know it might change). My hypothesis is that we could get a lot of the benefit, and avoid the sorts of pain I just described, if we could improve and rigorously apply a documentation and testing process for new interfaces (i.e., a process that occurs in parallel with the implementation of the interface, and is completed by the time of initial stable release, rather than after the fact).
(Log in to post comments)
|
|||||||||||||