on Wed Oct 17 2007, Christopher Lenz <cmlenz-AT-gmx.de> 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. Can you make the API (temporarily) backward-compatible with 0.10.x, and then just document it as being the 0.10.x API, even if various parts of Trac's own code (and even some existing plugins) are reaching in and using the partially-baked newer bits? > If we were talking about some optional, obscure API used somewhere in > some part of the internal Trac code, things would be different. But > we're really talking about an API that has had much more impact to > many more places of the code than it should have had, IMHO. Hm. >>> This is why we will not release until the devs are all happy with >>> this new system. >> >> In my opinion the cost of further release delays is high, and paying >> it is unnecessary. > > The cost is high, but I think paying it *is* necessary, otherwise the > follow-up cost will be tremendous. > > This is why I wrote a "What's gone wrong..." thread. Ideally, we > shouldn't even gotten ourselves into this situation, but we're here, > and we need to fix it. Agreed. It's just a question of how much needs to be fixed before people can have another release target to shoot at. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
