[1.39.0] New libraries?
Are there any new libraries that will be ready to go into the 1.39.0 release? Thanks, --Beman
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 05 March 2009, Beman Dawes wrote:
Are there any new libraries that will be ready to go into the 1.39.0 release?
Yes, I think Signals2 will be ready. I was going to ask for permission to add it to the release branch after the trunk regression tests have cycled one more time. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmv1q0ACgkQ5vihyNWuA4XMEgCeInNrMeEUfoXz4XGLIBfWZS+n UqYAnjN9dyHDlfJRo/IzGWuDAYzmOovw =lC21 -----END PGP SIGNATURE-----
On Thu, Mar 5, 2009 at 8:42 AM, Frank Mori Hess <frank.hess@nist.gov> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday 05 March 2009, Beman Dawes wrote:
Are there any new libraries that will be ready to go into the 1.39.0 release?
Yes, I think Signals2 will be ready. I was going to ask for permission to add it to the release branch after the trunk regression tests have cycled one more time.
Good! But first, please: * Add the library to boost-root/libs/libraries.htm * Add the library to boost-root/libs/maintainers.txt * Ask Daniel James to generate docs and check the results. I just generated them; there were some error messages and the resulting directory structure looked a bit odd to me. But I'm not very familiar with doc generation and conventions, so Daniel is one to verify all is OK. * Fix the Inspection Report issues: http://boost.cowic.de/rc/inspect-trunk.html#signals2 Thanks, --Beman
2009/3/5 Beman Dawes <bdawes@acm.org>:
* Ask Daniel James to generate docs and check the results. I just generated them; there were some error messages and the resulting directory structure looked a bit odd to me. But I'm not very familiar with doc generation and conventions, so Daniel is one to verify all is OK.
I built the standalone documentation and it looks fine. I'm building trunk's combined documentation now. Frank has done some boostbook development in the past, so he knows what's he's doing. Daniel
On Thu, Mar 5, 2009 at 1:48 PM, Daniel James <daniel_james@fmail.co.uk> wrote:
2009/3/5 Beman Dawes <bdawes@acm.org>:
* Ask Daniel James to generate docs and check the results. I just generated them; there were some error messages and the resulting directory structure looked a bit odd to me. But I'm not very familiar with doc generation and conventions, so Daniel is one to verify all is OK.
I built the standalone documentation and it looks fine. I'm building trunk's combined documentation now. Frank has done some boostbook development in the past, so he knows what's he's doing.
Great! I'm trying to get in the habit of running through the new library checklist earlier in the release cycle, since doc build integration has sometimes been problematic in the past. --Beman
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 05 March 2009, Beman Dawes wrote:
But first, please:
* Add the library to boost-root/libs/libraries.htm
* Add the library to boost-root/libs/maintainers.txt
* Ask Daniel James to generate docs and check the results. I just generated them; there were some error messages and the resulting directory structure looked a bit odd to me. But I'm not very familiar with doc generation and conventions, so Daniel is one to verify all is OK.
* Fix the Inspection Report issues: http://boost.cowic.de/rc/inspect-trunk.html#signals2
I think these issues are all fixed, although the inspection report hasn't run since Friday so it's still showing lots of violations. Is it all right to merge to release now? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkm1fW4ACgkQ5vihyNWuA4VmdgCgkDe58cti99Tj7E/0KwlqL/ZQ BC0AoNppc1jzJqRpF6T9lTMeKa/YELA3 =FjjY -----END PGP SIGNATURE-----
2009/3/9 Frank Mori Hess <frank.hess@nist.gov>:
I think these issues are all fixed, although the inspection report hasn't run since Friday so it's still showing lots of violations. Is it all right to merge to release now?
There are still a couple of inspect errors: |signals2| libs/signals2/doc/reference/mutex.xml: *C* *Lic* |unknown| boost/signals2.hpp: *C* I also just fixed a couple of minor documentation issues in trunk, so include this once you get permission to merge. https://svn.boost.org/trac/boost/changeset/51669/ Daniel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 09 March 2009, Daniel James wrote:
2009/3/9 Frank Mori Hess <frank.hess@nist.gov>:
I think these issues are all fixed, although the inspection report hasn't run since Friday so it's still showing lots of violations. Is it all right to merge to release now?
There are still a couple of inspect errors: |signals2|
libs/signals2/doc/reference/mutex.xml: *C* *Lic*
|unknown|
boost/signals2.hpp: *C*
Those should be fixed now.
I also just fixed a couple of minor documentation issues in trunk, so include this once you get permission to merge.
Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkm1iSoACgkQ5vihyNWuA4UmTwCgsWh89ZSmKENFXCzVUSC8AdaY uecAoL7oDLSXNhnOllF0fHtAsAkQb6rt =1c9E -----END PGP SIGNATURE-----
participants (3)
-
Beman Dawes -
Daniel James -
Frank Mori Hess