[new libraries] [sort] New Library Check list updated
As we started through the process of adding the sort library as a module, it became obvious the docs for how to do this were quite out-of-date. The best document for adding new libraries is https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList#NewL..., and that section has now been updated. Although this document is written from the perspective of release managers, the New Library Checklist section serves as a roadmap for what is expected as a new library goes through the stages of being added to a Boost distribution. Comments and corrections welcome, --Beman
On 1/22/2015 11:01 AM, Beman Dawes wrote:
As we started through the process of adding the sort library as a module, it became obvious the docs for how to do this were quite out-of-date. The best document for adding new libraries is https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList#NewL..., and that section has now been updated.
Although this document is written from the perspective of release managers, the New Library Checklist section serves as a roadmap for what is expected as a new library goes through the stages of being added to a Boost distribution.
Comments and corrections welcome,
The links "Create the library's repository" and "Create a team for the library" do not go anywhere ( 404 s ).
On 22 January 2015 at 16:01, Beman Dawes <bdawes@acm.org> wrote:
As we started through the process of adding the sort library as a module, it became obvious the docs for how to do this were quite out-of-date. The best document for adding new libraries is https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList#NewL..., and that section has now been updated.
Although this document is written from the perspective of release managers, the New Library Checklist section serves as a roadmap for what is expected as a new library goes through the stages of being added to a Boost distribution.
If there's already a repo in github, it'd be better to just transfer it to the organisation, rather than creating a new one. https://help.github.com/articles/transferring-a-repository/ I've found getting the maintainer to transfer into the organisation is a bit awkward. so it might be best to first transfer the repo to an admin, who can then transfer it into the organisation and set up the team.
On Thu Jan 22 2015 at 11:01:30 AM Beman Dawes <bdawes@acm.org> wrote:
As we started through the process of adding the sort library as a module, it became obvious the docs for how to do this were quite out-of-date. The best document for adding new libraries is https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList# NewLibraryChecklist, and that section has now been updated.
Although this document is written from the perspective of release managers, the New Library Checklist section serves as a roadmap for what is expected as a new library goes through the stages of being added to a Boost distribution.
Comments and corrections welcome,
--Beman
Thanks Beman. It looks like we're now at the "Add library as a submodule on boost master branch" stage. Who should make these changes in the boost root that the release manager is supposed to verify? Should these same changes also be made in develop?
On Thu Jan 22 2015 at 8:06:58 PM Steven Ross <spreadsort@gmail.com> wrote:
On Thu Jan 22 2015 at 11:01:30 AM Beman Dawes <bdawes@acm.org> wrote:
As we started through the process of adding the sort library as a module, it became obvious the docs for how to do this were quite out-of-date. The best document for adding new libraries is https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList# NewLibraryChecklist, and that section has now been updated.
Although this document is written from the perspective of release managers, the New Library Checklist section serves as a roadmap for what is expected as a new library goes through the stages of being added to a Boost distribution.
Comments and corrections welcome,
--Beman
I've added pull requests libs/libraries.htm and libs/maintainers.txt. Merging those in should resolve everything necessary before the library is added to master, except for this one which seems to refer to a file that doesn't exist: "root/libs/meta/libraries.json is present and contents look reasonable."
I added pull requests for these changes to both develop and master because it wasn't clear which was appropriate (develop?). Is there anything else I need to for a release manager to merge the sort library into master? Is there a specific release manager I should be talking to?
Steven Ross wrote:
Merging those in should resolve everything necessary before the library is added to master, except for this one which seems to refer to a file that doesn't exist: "root/libs/meta/libraries.json is present and contents look reasonable."
This refers to the file libs/sort/meta/libraries.json you need to add, documented here: http://www.boost.org/development/library_metadata.html
On Sat Jan 31 2015 at 3:01:21 PM Peter Dimov <lists@pdimov.com> wrote:
Steven Ross wrote:
Merging those in should resolve everything necessary before the library is added to master, except for this one which seems to refer to a file that doesn't exist: "root/libs/meta/libraries.json is present and contents look reasonable."
This refers to the file libs/sort/meta/libraries.json you need to add, documented here:
http://www.boost.org/development/library_metadata.html
Thanks. I've added that file to the sort library. I believe libs/sort is now ready to merge into master. Would somebody be willing to do that for me? Should I submit a pull request to do that?
participants (5)
-
Beman Dawes -
Daniel James -
Edward Diener -
Peter Dimov -
Steven Ross