On Mon, 21 Jun 2004, Thorsten Ottosen wrote:

|"Joaqu�n M� L�pez Mu�oz" <joaquin@tid.es> wrote in message news:40D28963.573B38E9@tid.es... |Aleksey talked about June 28th: | |http://lists.boost.org/MailArchives/boost/msg62871.php | |but seems like there has been no activity wrt to releasing |Boost 1.32 since. Is that date still valid? I guess it is not, |for the one week remaining is probably to little time to |arrange everything.

I don't know how exactly we usually do this. Some people would like one of my libraries, Boost.Range, to be included in the next version of boost.

If the june 28th is the deadline, I won't make it. If july 28th is the deadline, I might be able to make it.

You're including time to stabilize the code in that estimate, I assume? If we're to pull together a release in the near future, we'd want to get all major changes (new libraries, etc.) in "soon" and then have a week or two to whack the portability bugs that always crop up. Doug

On Mon, Jun 21, 2004 at 10:44:59AM -0400, Douglas Paul Gregor wrote:

On Mon, 21 Jun 2004, Thorsten Ottosen wrote:

...

|"Joaquín MŞ López Muńoz" <joaquin@tid.es> wrote in message news:40D28963.573B38E9@tid.es... |Aleksey talked about June 28th: | |http://lists.boost.org/MailArchives/boost/msg62871.php | |but seems like there has been no activity wrt to releasing |Boost 1.32 since. Is that date still valid? I guess it is not, |for the one week remaining is probably to little time to |arrange everything.

I don't know how exactly we usually do this. Some people would like one of my libraries, Boost.Range, to be included in the next version of boost.

If the june 28th is the deadline, I won't make it. If july 28th is the deadline, I might be able to make it.

You're including time to stabilize the code in that estimate, I assume? If we're to pull together a release in the near future, we'd want to get all major changes (new libraries, etc.) in "soon" and then have a week or two to whack the portability bugs that always crop up.

I'd like to second the deadline of 28th july if I can. I still need to do some work on the string_algo library and the inclusion of Range library would save me a substantial part of work on the documentation, that would have to be changed anyway afterwards. Regards, Pavol

"Thorsten Ottosen" <nesotto@cs.auc.dk> writes:

|"Joaquín Mª López Muñoz" <joaquin@tid.es> wrote in message news:40D28963.573B38E9@tid.es... |Aleksey talked about June 28th: | |http://lists.boost.org/MailArchives/boost/msg62871.php | |but seems like there has been no activity wrt to releasing |Boost 1.32 since. Is that date still valid? I guess it is not, |for the one week remaining is probably to little time to |arrange everything.

I don't know how exactly we usually do this. Some people would like one of my libraries, Boost.Range, to be included in the next version of boost.

If the june 28th is the deadline, I won't make it. If july 28th is the deadline, I might be able to make it.

I think June 28th is out of the question at this point. I hope to have the release done a week or so before July 28th, though, say July 21. If we start today, that gives us a month or so. There's going to be some disruption when Aleksey moves the mplbook branch of MPL over to the trunk. In many ways the code is backwards-compatible, but significant elements have been redesigned during the writing of the book. I know he has some porting work to older compilers to do before we can make that move, though, so I don't know when it'll happen. If there are any accepted Boost libraries that people can be ready to add to CVS soon, they should do so as soon as possible, so we have as much time as possible to shake out the issues. Incidentally, we ought to think about ways to encourage newly-accepted libraries to be added well in advance of an upcoming release, to amortize the problems. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com