Glad to hear you're happily ensconced in your new gig.
I'll go ahead and jump, as you say. In general, these are the goals for the restructuring: 1. Repo structure as hammett outlined previously, using subtrees rather than submodules. For those not familiar check out http://progit.org/book/ch6-7.html 2. Branching and Tagging per http://nvie.com/posts/a-successful-git-branching-model/ 3. Consolidate and refactor disparate build scripts, merging and refactoring until we have a central build tool/scripts repository. This is consistent with using the methodology Henrik Feldt previously outlined. 4. ????? High Level Action Plan 1. Restructure current repositories, consolidating and retiring per the new structure (e.g. Binder and Validator moved into Core, etc). 2. Branch and Tag specific changesets within each Repository to reflect most recent releases. 3. Ensure each restructured repository builds using the current build process, and that the VS.NET Solution works. 4. Build aggregate repository (Castle.sln) composed of the various restructured repos. 5. ????? Questions: 1. To support the Castle-wide use of a consistent Branching/Tagging scheme, I'll need some help determining which changesets best represents the release point, and which subsequent changesets should be considered bugfixes that need to be backported into that release branch (assuming we use the model above). 2. Should there be trimming of history within the individual repos? If so, how far back? 3. How much trimming of history should there be within the aggregate Repo? For that matter, should the subtree merge squash commit messages, like it suggests in the Pro Git subtree article? I say no, since that article is focused on local development using an externally managed repository, and we're talking about all-internal repositories. Which is to say, I think the aggregate Repo should include the commit history of each of it's components. 4. ????? -rb -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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/castle-project-devel?hl=en.
