Ralph Goers wrote: > Stefano Mazzocchi wrote: > >Ralph Goers wrote: > >>Vadim Gritsenko wrote: > >>>Torsten Curdt wrote: > >>> > >>>>We only need a few more people using it to find the corner cases. > >>> > >>>Stable API != Stable Implementation. If API is stable, you should > >>>start vote on marking javaflow stable. > >> > >>I second that. We really need to find a better term than "stable". > > > >Mozilla uses 'frozen'. > > > I've always used that term to mean that there can't be any more code > changes - such as just before a release. What we are after here is > something that says that the component is mature in the sense that its > APIs are stable and that the community is willing to maintain it while > adhering to our release guidelines (i.e. maintaining binary > compatibility and/or deprecating things over time).
Then how about "mature". -David
