Changes between Version 9 and Version 10 of ModCvtFAQ

Timestamp:

Oct 28, 2013, 1:04:11 PM (9 years ago)

Author:

Beman Dawes

Comment:

Bring up to date. Add questions, Acknowledgements

ModCvtFAQ

@@ -1 +1 @@
 = Modular Boost Frequently Asked Questions =
+[[PageOutline]]
 
 == Conversion to Git and modular Boost ==
@@ -11 +12 @@
  None. The whole need for the sandbox as a part of the boost repository goes away. Proposed libraries that used to go in the sandbox now just go in their own public repositories. They are typically hosted on [https://github.com GitHub], but any public host will do. ExtractSandbox shows how to move a library from the old sandbox to !GitHub. StartModDev shows how a repository for a proposed library would work.
 
-**Is it possible to checkout only library A and its prerequisites?**
+== General Questions ==
 
- Not automatically. Automatic dependency resolution is planned for the future, but not as a part of the conversion to Git and modular Boost.**
+**Is it possible to checkout only one library and its prerequisites?**
+
+ Not automatically. Automatic dependency resolution is planned for the future, but not as a part of the conversion to Git and Modular Boost.**
 
 **So how do I get a modularized Boost that I can actually use?**
@@ -19 +22 @@
 See [TryModBoost#InstallingModularBoost these instructions].
 
-== General Questions ==
+**How do I submit fixes to a Boost library owned by someone else?**
 
-**How do I get write access to my library at {{{github.com/boost-lib}}}?**
+ Short answer: Submit a pull request at {{{github.com/boostorg}}}.
+
+ Long answer: See [https://help.github.com/articles/fork-a-repo GitHub's] description of the process. [http://stackoverflow.com/questions/2199144/github-git-how-to-submit-changes-to-an-upstream-repo Stackoverflow] also covers the topic. This [http://www.youtube.com/watch?v=75_UrC2unv4 video] shows how !GitHub manages interactions between the submitter and the library owner.
+
+** Will we keep using trac for tickets?**
+
+ There's no immediate plan to change anything about how our issue tracking works.
+
+== Library Maintainers ==
+
+**How do I get write access to my library at {{{github.com/boostorg}}}?**
 
  See [ModAdmin Administrative Privileges for public library repositories].
 
-**How do I submit fixes to a Boost library owned by someone else?**
+**Will there be a lockdown for individual libraries master branches during the release cycle?**
 
- The Git community has a usual way of submitting changes upstream. See [https://help.github.com/articles/fork-a-repo GitHub's] description of the process. [http://stackoverflow.com/questions/2199144/github-git-how-to-submit-changes-to-an-upstream-repo Stackoverflow] also covers the topic. This [http://www.youtube.com/watch?v=75_UrC2unv4 video] shows how !GitHub manages interactions between the submitter and the library owner. 
+ No, as far as we know at this point.
+
+**Will there be support branches for particular releases?**
+
+Which branches get created depends on who owns the repository in question. Thus, If you are asking about Boost super-project releases, then that is up to the community and the release managers. If you are asking about individual library releases, that is up to the individual library maintainers.
+
+**What branches will be tested**
+
+ Short answer: We don't know yet.
+
+ Long answer: We will start with something simple, and then work up to a continuous integration test scenarios. One of the key objectives of modularization, right from the start, has been to facilitate much more responsive testing.
+
+== Acknowledgements ==
+
+Thanks to Andrey Semashev and Antony Polukhin for submitting many of these questions. Dave Abrahams provided many of the answers.
+
+Beman Dawes is maintaining this page.