List view
"Cutover" is the point in time when modularization goes live - developers stop committing to the Subversion repo and start pushing library changes to the modularized repos on GitHub. ### Prerequisites - [ ] All github.com/ryppl/boost-svn2git/issues closed. - [ ] History Modularization Vetted and Tweaked milestone closed. - [ ] Wiki updates milestone closed. - [ ] Regression testing and reporting conversion milestone closed. - [ ] Website conversion milestone closed. ### Actions - [ ] The Subversion repo goes read-only. - [ ] The Git repo goes live. - [ ] The automatic svn to git conversion scripts stop running. - [ ] The www.boost.org website conversion goes live. - [ ] The inspect scripts are switched from the svn repo scripts to the git repo scripts. - [ ] Regression test reporting for the svn repo turned off. - [ ] An announcement of the cutover is posted to the developer, user, and announce mailing lists.
No due dateBy definition, the wiki is never complete. For this milestone to be closed, wiki updates need to be sufficient that developer documentation covers commonly occurring needs and most repo references and procedures have been updated to use git and modular boost. - [ ] Developer's documentation sufficiently complete to allow cutover to git. - [ ] Cycle as needed: - [ ] Change svn references and procedures to use git and modular boost - [ ] Ask for volunteers to review for comments and corrections
No due dateThe objective is to get the Boost website ready to go live at the time of cutover to Git and modular Boost. All current references and instructions relating to svn and the svn repo will be replaced by references and instructions for git and the modular boost git repos. Steps include: - [ ] Set up a branch? Or use svn.boost.org/svn/boost/website/public_html/beta? Or a GitHub repo? Better ask on list. - [ ] Cycles of: - Change references to svn to git. - Ask for feedback from developer and user lists. - [ ] Make the usual pre-release changes for the next release (release-managers).
No due dateSteps include: - [ ] Convert script and test locally, both for daily snapshots and quarterly releases. - [ ] Convert docs. - [ ] Volunteer verifies works on both Windows and the Mac. - [ ] Convert, test, and start running the daily snapshot chron setups.
No due dateSteps include: - [ ] Convert inspect.cpp. Verify that it works both on the master project and individual library repos. - [ ] Test on various operating systems. - [ ] Convert docs. - [ ] Volunteers start testing with converted docs and program. - [ ] Volunteers report success with converted docs and program. - [ ] Convert the daily script and place in operation for both master and develop branches.
No due dateThe overall objective is to get regression testing and reporting running for modular Boost. Steps include: - [ ] Convert testing script and test it locally. - [ ] Convert test reporting script and start it running on a temporary host. - [ ] Convert docs. - [ ] Volunteers start testing with converted docs and script. - [ ] Volunteers report success with converted docs and script. - [ ] Start test reporting running on the permanent host.
No due dateBoosters are satisfied with the state of history modularization. Steps: - [ ] "Repository Conversion Ready for Vetting" milestone closed. - [ ] Request for comments posted on the Boost developers lists. - [ ] Issues created based on comments. - [ ] Resulting issues closed.
Overdue by 12 year(s)•Due by February 27, 2013•0/4 issues closedWe've done everything we want to automate and are ready for Boosters to look at the results in detail
Overdue by 12 year(s)•Due by February 13, 2013•2/7 issues closed