On 17 Okt., 19:55, Christopher Lenz <[EMAIL PROTECTED]> wrote: > Am 17.10.2007 um 19:34 schrieb David Abrahams: > > > on Wed Oct 10 2007, Noah Kantrowitz <kantrn-AT-rpi.edu> wrote: > > >>> so if you release now, and then do a bugfix release by changing the > >>> context like cmlenz suggests, who would care? and then release > >>> something further developped with maybe an idea of cboos in it > >>> discussed? > > >> We do not want to declare some of these APIs as available for public > >> consumption if they are going to break or be removed very shortly. > > > Suggestion: so don't declare those APIs available, and keep working on > > them until you're ready to release them. If they're in the code, > > under the covers, they won't hurt anybody as long as they work as > > currently expected. > > In general I'd agree, however we're talking about the Context API, > which is used *all over the place*, with some other APIs (timeline) > building on it. There's no way to simply hide this API and say it's > not ready for prime time. It *needs* to be fixed before a release. >
why? how all these currently running 0.11 installations using 0.11 api compatible plugins will handle such a change? why not just tag and release cboos context changes as new version 0.12? i think calling 0.11 calling "release" is the wrong word - as it is already out. tagging what you have to guarantee some managed change cycle seems not a bad strategy. rupert. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
