On Tue, May 29, 2012 at 10:12 AM, Lars Viklund <zao@acc.umu.se> wrote:
On Tue, May 29, 2012 at 05:31:20AM -0700, Marshall Clow wrote:
Development of Boost will move from a monolithic subversion repository to the much-discussed Git repository structure consisting of one super-module that points (via submodules) to other repositories, each containing an individual Boost library. The Git repositories will be hosted on github.
I hope that this is coupled with very clear and unambigious instructions on things like "how to work in submodules", as that's something which I have repeatedly misunderstood and successfully use to completely destroy my own repositories.
We need proper documentation and operating procedures, preferably something that has been well tested in our future configuration.
Yes, for sure. Each of the common development scenarios needs to be covered: * Setup a clone for development work. * Doc fix. * Simple bug fix. * Complex bug fix best done on branch. * Minor feature branch for next release. * Major feature branch for future release. * Tag and release a new version of the library. We also need a virtual "Git Help Desk" so developers can get quick and accurate answers to questions. Maybe that's as simple as tagging subject lines [git help]. Help will be particularly important when a developer runs into trouble. --Beman