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. > 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. -- 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 -~----------~----~----~----~------~----~------~--~---
