Hello Basil, mkitezr wrote: > Thanks Jani and Christian for your responses. > > On the topic of picking unstable? trunk vs stable released... I was > thinking working with a known working and stable version, perhaps even > released, with good test case coverage, will give me a great baseline > to be sure whatever mods my team produces will work, or the issues we > are seeing are surely a result of our changes. If the target trunk or > sandbox code is changing then our objective port will also be moving.
I can understand the reasoning, but ... > Or is trunk now pretty stable? /trunk has in practice pretty much the same "stability" as /branches/0.11-stable. We have the same set of tests (probably a bit more) and we usually only commit known working sets of changes. Unstable development happen in the /sandbox, and even there ... well, the /sandbox/multirepos is what I use everyday so it gets synced from trunk quite frequently and has also to work correctly. So nothing prevents you to take a baseline on /trunk for example and stick with it so that in this scenario as well any new issue would be most probably due to your changes (given that 0.11.5 is also not 100% bug free). Now, when you consider the integration part, as you said you'd like to see your work merged in mainline Trac, such a big change has less likeliness to be integrated in a further 0.11.x release than it has in the upcoming 0.12 release. Especially if you end up requiring SQLAlchemy, then this likeliness drops to 0%, as we won't suddenly add a new mandatory requirement for a stable release line ;-) Also, we decided to freeze the 0.11-stable branch a few weeks ago and therefore 0.11.6 will be the last release made on that branch - we're not that far away from that point, see http://trac.edgewall.org/milestone/0.11.6. Last reason to target 0.12 rather than 0.11: as Jani said, there are chances that compatibility changes would be required in plugins, and plugins are usually branched according to major Trac releases as well, so this would be a better fit. > > I was thinking we would have to be one rev behind the latest work in > progress, but up to date with the latest stable release. In other > words, 0.11.5 is stable, we would be creating an Oracle port of > 0.11.5. Is it branched/tagged at that release? Is trunk work towards > 0.11.6? it doesn't look like a branch/tag is there for 11.5 per se. And now some ASCII art to summarize the situation: /tags/0.11 ... /tags/0.11.5 (/tags/0.11.6) / / / / /branches/0.11-stable +-------------------- 0.11.6dev --? / (/branches/0.12-stable) / +-- ... / / /trunk -- 0.11dev --------- 0.12dev ------------?------?--- ... \ / /sandbox/multirepos +------------------+ In the above "?" represents future branch/merge points and "(/path)" corresponds to a path to be created. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
