Hi all, I have taken a look at the requirements to release a new library. There is some points I like to discuss. Technically speaking gil::io is a replacement of the older gil io extension. So, it's not really a new library. But of course, I don't mind fulfilling all the requirements. Here are the requirements before merging: * root/libs/libraries.htm entry is OK, both in the alphabetic list and in the category lists. Should I add a gil::io entry? * root/libs/maintainers.txt entry is OK. Should I add a gil::io entry? * The library's root/libs/xxx directory contains an index.html file with either the main docs or a redirection to the main docs. Done * The primary docs pages meet Boost requirements and guidelines. Don't leave this until too late; it has turned up lots of issues in the past. I'm using boostbook and the default templates. * Trunk inspection report is clean. I would need some help here to hook up gil::io test with general boost testing. * Trunk regression tests are reasonably clean or marked up. TODO Thanks, Christian
On 25 February 2013 01:16, Christian Henning <chhenning@gmail.com> wrote:
Hi all,
I have taken a look at the requirements to release a new library. There is some points I like to discuss.
Technically speaking gil::io is a replacement of the older gil io extension. So, it's not really a new library. But of course, I don't mind fulfilling all the requirements.
How it's listed in the library lists is up to the gil maintainers and you.
* Trunk inspection report is clean.
You can see the inspection report at: http://boost.cowic.de/rc/docs-inspect-trunk.html#gil *C* = missing copyright, *Lic* = missing license.
I would need some help here to hook up gil::io test with general boost testing.
I'd normally just include it from the gil tests (using 'build-project' I think). But if you want it to be separate you can add it to 'status/Jamfile.v2'. I think you'll also need to add an empty 'sublibs' file in 'libs/gil/' to indicate that it has sub-libraries - you can see these in the algorithm, functional, numeric, spirit and utility libraries. Btw. if it isn't obvious, the release process is up in the air for this cycle due to the git migration.
H Daniel, thanks for your reply.
Technically speaking gil::io is a replacement of the older gil io extension. So, it's not really a new library. But of course, I don't mind fulfilling all the requirements.
How it's listed in the library lists is up to the gil maintainers and you.
Since, I'm the maintainer I think it's just fine when gil::io is not listed. But I like to add a notice in the release notes that the old gil::io has been replaced.
* Trunk inspection report is clean.
You can see the inspection report at:
http://boost.cowic.de/rc/docs-inspect-trunk.html#gil
*C* = missing copyright, *Lic* = missing license.
I have added all the missing notices, removed tab characters, and missing newlines for boost::gil.
I would need some help here to hook up gil::io test with general boost testing.
I'd normally just include it from the gil tests (using 'build-project' I think). But if you want it to be separate you can add it to 'status/Jamfile.v2'. I think you'll also need to add an empty 'sublibs' file in 'libs/gil/' to indicate that it has sub-libraries - you can see these in the algorithm, functional, numeric, spirit and utility libraries.
I like to test that first on my machine. What would be the command line to build all boost test suits? gil::io has some compiler symbols to turn off reading from hard drive and writing to hard drive. I though that might be helpful for regression test servers that have limited capacities. When all tests are enabled there are 300 files written and like 500 files read. Also I don't wanna get into licensing issues for some of the test images I'm using.
Btw. if it isn't obvious, the release process is up in the air for this cycle due to the git migration.
I have to learn git? ;-) Thanks again, Christian
How it's listed in the library lists is up to the gil maintainers and you.
Since, I'm the maintainer I think it's just fine when gil::io is not listed. But I like to add a notice in the release notes that the old gil::io has been replaced.
Sure. You probably should also add your name to maintainers.txt, possibly as a separate entry there.
I have added all the missing notices, removed tab characters, and missing newlines for boost::gil.
I've updated the report: http://boost.cowic.de/rc/docs-inspect-trunk.html#gil
I would need some help here to hook up gil::io test with general boost testing.
I'd normally just include it from the gil tests (using 'build-project' I think). But if you want it to be separate you can add it to 'status/Jamfile.v2'. I think you'll also need to add an empty 'sublibs' file in 'libs/gil/' to indicate that it has sub-libraries - you can see these in the algorithm, functional, numeric, spirit and utility libraries.
I like to test that first on my machine. What would be the command line to build all boost test suits?
I think you just run 'b2' from the status directory.
gil::io has some compiler symbols to turn off reading from hard drive and writing to hard drive. I though that might be helpful for regression test servers that have limited capacities. When all tests are enabled there are 300 files written and like 500 files read. Also I don't wanna get into licensing issues for some of the test images I'm using.
You could ask about that on the testing list.
participants (2)
-
Christian Henning -
Daniel James