On Sep 10, 1:44 pm, "Lucas Stephanou" <[EMAIL PROTECTED]> wrote: > I agree with you Luis, > I'm using 0.11 trunk in production ( Yes, I'm crazy) but that it quite > stable after all. > > After 1 mount working in production with 0.11 trunk, I think that is very > close of a stable version. >
I agree with you on the stability - from a user perspective 0.11dev is looking very nice, with the new features and the old mostly working as expected. Normally I would have no problem recommending/accepting a beta - it could have been made months ago if the end-user features where all that mattered. However, I do feel most of the issues raised by Christopher deals with the internals - used by the other Trac developers, plugin developers and those customising Trac for their own purposes in various ways. Having through the last couple of months worked to convert my solution to 0.11dev (15+ own customisations/plugins, 5+ external ones) I have bumped into a number of issues - some are fixed, some core issues that are still open, and some are issues that sort of works but just feels awkward or half-finished (like the context, security and timeline api examples mentioned). With the Trac focus of minimalim, component archtecture, active plugin development, and flexibility for customisation and re-use, the most important criteria for starting a new release cycle should be that the internals (core entities, mechanisms and interfaces) are as we want them - the building bloks for making features. An official beta is a signal for a lot of people to start requesting, converting and supporting their code/plugins for 0.11, and out of respect for the time and effort of developers it should not be shipped knowing they might have to redo it before official 0.11. So, personally - and from an external developer perspective - I'm -1 on any 'official' release until some core issues have been sorted out (even though I have no vote :-). 'Sorted out' could be as easy as the core developers agreeing to leave it as it is, or as complicated as re- writing a number of internals. I encourage you all to reach some sort of consensus on what needs to be done, as I (like others) would obviously like to see a release soon. I suppose this discussion also nicely underlines the need for more formal and review based implementation of features - using branches, having complete patches, and achieving consensus on important changes... :::simon http://www.coderesort.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 -~----------~----~----~----~------~----~------~--~---
