Hi Rene, I've accepted the org invite. Regards, Abel On 2015-10-18 18:16, Rene Rivera wrote:

On Sun, Oct 18, 2015 at 7:03 AM, Abel Sinkovics wrote:

...

I'd like to transfer my Metaparse repository ( https://github.com/sabel83/metaparse) to Boostorg. Based on another thread on Hana, I assume I need temporary admin rights to boostorg to be able to transfer the repository. Please give me temporary admin rights (I've posted an issue for it as well: https://github.com/boostorg/admin/issues/110) or suggest another method for the repository transfer.

Ping again when you accept the org invite.

Looks like you are done.. And should be all set. Ping if you need help with something else. On Sun, Oct 18, 2015 at 2:11 PM, Rene Rivera wrote:

OK, please transfer the repo now.

On Sun, Oct 18, 2015 at 2:01 PM, Abel Sinkovics wrote:

...

Hi Rene,

I've accepted the org invite.

Regards, Abel

On 2015-10-18 18:16, Rene Rivera wrote:

...

On Sun, Oct 18, 2015 at 7:03 AM, Abel Sinkovics wrote:

...

I'd like to transfer my Metaparse repository ( https://github.com/sabel83/metaparse) to Boostorg. Based on another thread on Hana, I assume I need temporary admin rights to boostorg to be able to transfer the repository. Please give me temporary admin rights (I've posted an issue for it as well: https://github.com/boostorg/admin/issues/110) or suggest another method for the repository transfer.

Ping again when you accept the org invite.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

-- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

-- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

On Sun, Oct 18, 2015 at 3:37 PM, Abel Sinkovics wrote:

Hi Rene,

Yes, I'm done and it looks like the CI environments work as well. Thank you for your help.

For the rest of the migration: am I supposed to create a pull request for the boostorg/boost repository adding the new submodule, the new entries to maintainers.txt, libraries.htm, etc? Or is it maintained by scripts? (Is there maybe a description of this somewhere?)

For most of those, yes, create a PR. But also make sure to have the meta info in your repo also as some of the files are updated from that info. Although I don't remember which ones are :-\ -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

Hi Rene, I've created a pull request to the develop branch. The CI scripts of Metaparse have been testing the library in the Boost source tree, so I expect the tests and examples to build fine. I've migrated the documentation to Quickbook, so I added it to the list of BoostBook-based libraries. I can generate the documentation in the doc directory of the library, however, when I try to generate all BoostBook documentations from the "main" doc directory of the Boost source tree, the png images don't get copied to the right place. So currently they need to be copied to html/images/metaparse manually after the documentation generation in that case. Regards, Abel On 2015-10-18 23:02, Rene Rivera wrote:

On Sun, Oct 18, 2015 at 4:01 PM, Rene Rivera wrote:

...

On Sun, Oct 18, 2015 at 3:37 PM, Abel Sinkovics wrote:

...

Hi Rene,

Yes, I'm done and it looks like the CI environments work as well. Thank you for your help.

For the rest of the migration: am I supposed to create a pull request for the boostorg/boost repository adding the new submodule, the new entries to maintainers.txt, libraries.htm, etc? Or is it maintained by scripts? (Is there maybe a description of this somewhere?)

For most of those, yes, create a PR. But also make sure to have the meta info in your repo also as some of the files are updated from that info. Although I don't remember which ones are :-\

Forgot to mention.. Remember that all PRs should be for develop branch first.

Hi Rene, Thank you for merging the PR. How will it move to the master branch? Will the develop branch be propagated at some point or should I create another pull request for the master branch? Regards, Abel On 2015-10-20 07:51, Abel Sinkovics wrote:

Hi Rene,

I've fixed the image copying issue (inside Metaparse and I've updated the pull request to point the submodule to the latest commit).

I'm not aware of any further issues with Metaparse and its integration.

Regards, Abel

On 2015-10-20 00:47, Abel Sinkovics wrote:

...

Hi Rene,

I've created a pull request to the develop branch. The CI scripts of Metaparse have been testing the library in the Boost source tree, so I expect the tests and examples to build fine.

I've migrated the documentation to Quickbook, so I added it to the list of BoostBook-based libraries. I can generate the documentation in the doc directory of the library, however, when I try to generate all BoostBook documentations from the "main" doc directory of the Boost source tree, the png images don't get copied to the right place. So currently they need to be copied to html/images/metaparse manually after the documentation generation in that case.

Regards, Abel

On 2015-10-18 23:02, Rene Rivera wrote:

...

On Sun, Oct 18, 2015 at 4:01 PM, Rene Rivera wrote:

...

On Sun, Oct 18, 2015 at 3:37 PM, Abel Sinkovics wrote:

...

Hi Rene,

Yes, I'm done and it looks like the CI environments work as well. Thank you for your help.

For the rest of the migration: am I supposed to create a pull request for the boostorg/boost repository adding the new submodule, the new entries to maintainers.txt, libraries.htm, etc? Or is it maintained by scripts? (Is there maybe a description of this somewhere?)

For most of those, yes, create a PR. But also make sure to have the meta info in your repo also as some of the files are updated from that info. Although I don't remember which ones are :-\

Forgot to mention.. Remember that all PRs should be for develop branch first.

Hi Rene, On 2015-10-20 21:39, Rene Rivera wrote:

Usually it's a combination of PRs and some manual labor by the release managers. But before that can happen the release managers need to see some test results from the develop branch. Which given that the cutoff for new libs is tomorrow I highly doubt you'll make it for this release. We tend to prefer that new libs go in shortly after a new release goes out the door so that we get as much of a full cycle of testing and working out the kinks as possible.

So it looks like it should go in after the release. Are there further things on my side I should prepare during the release period or are the next steps up to the release managers? Regards, Abel