c++.announce - STLSoft 1.9 final release planning: ideas sought
- Matthew (48/48) Dec 28 2006 Hi peeps
- Neal Becker (3/67) Jan 01 2007 Do we have any cvs/svn/whatever access? I'd like to update my last down...
- Matthew (12/14) Jan 01 2007 Not as yet.
Hi peeps I think I'm nearly at the point where, technically speaking, STLSoft 1.9 is ready for off. The big tasks that remain are: - the websites - the documentation - the examples - the extras - the samples - the test programs I'm keen to hear input from users on all of these (or other) issues. Ask yourself: - What is not clear about STLSoft? - What information do you not easily get from the website and/or distributions? My current thoughts are: Website: -------- - trim down the websites significantly - have the sub-project websites be more like tutorial sections, e.g. ACESTL.org would just note that it's the ACE-related sub-project, discuss the ACESTL components, and give a few code examples Documentation: --------------- - refine as per http://stlsoft.org/doc-1.9, but add more discussion to each component (like http://stlsoft.org/doc-1.9/classstlsoft_1_1auto__buffer.html) Examples: ---------- - keep the examples format as is (see the latest beta for the current examples) but gradually add more and more until this covers (almost) all components Extras: ------ - no changes planned to format - add examples of use of them (this may have to be a 1.9.2 thing, tho) Samples -------- - refactor all the current examples for the new STLSoft include directories, and new/updated components since 1.8.9 - add more in the future Test Programs --------------- - no changes planned Please let me know any thoughts/requests, as this is pretty much the last chance to get changes into 1.9.1. Cheers Matthew
Dec 28 2006
Matthew wrote:Hi peeps I think I'm nearly at the point where, technically speaking, STLSoft 1.9 is ready for off. The big tasks that remain are: - the websites - the documentation - the examples - the extras - the samples - the test programs I'm keen to hear input from users on all of these (or other) issues. Ask yourself: - What is not clear about STLSoft? - What information do you not easily get from the website and/or distributions? My current thoughts are: Website: -------- - trim down the websites significantly - have the sub-project websites be more like tutorial sections, e.g. ACESTL.org would just note that it's the ACE-related sub-project, discuss the ACESTL components, and give a few code examples Documentation: --------------- - refine as per http://stlsoft.org/doc-1.9, but add more discussion to each component (like http://stlsoft.org/doc-1.9/classstlsoft_1_1auto__buffer.html) Examples: ---------- - keep the examples format as is (see the latest beta for the current examples) but gradually add more and more until this covers (almost) all components Extras: ------ - no changes planned to format - add examples of use of them (this may have to be a 1.9.2 thing, tho) Samples -------- - refactor all the current examples for the new STLSoft include directories, and new/updated components since 1.8.9 - add more in the future Test Programs --------------- - no changes planned Please let me know any thoughts/requests, as this is pretty much the last chance to get changes into 1.9.1. Cheers MatthewDo we have any cvs/svn/whatever access? I'd like to update my last download with the latest changes.
Jan 01 2007
Do we have any cvs/svn/whatever access? I'd like to update my lastdownloadwith the latest changes.Not as yet. As soon as v 1.9 is released, I will continue to refine the docs and so forth, including stripping out all the "old" headers - e.g. unixstl_process_mutex.h (now is unixstl/synch/process_mutex.hpp). Once all that's done to a really good level, I've been considering putting it on SourceForge with the release of 1.10, at which point svn access would be possible. For the moment, just download the latest beta zip and overwrite. (And do a backup if you're cautious.) Cheers Matthew
Jan 01 2007