A quick update: we're trying to build GCC 4.3.0 on HP-UX/ia64 and when we're done, I'll switch to this compiler. I hope I'll be able to run Boost test in both C++0x and C++98 mode, both trunk and release branch. It is not clear yet whether we can upgrade the GCC compiler on a Linux machine I use for Boost testing. I have a question: for testing Boost 1.35, all one had to do was to specify "--tag=branches/release" on run.py command. Is this the same with Boost 1.36? I.e. is it correct that branches/release always represents the current development Boost release? Thanks, Boris ----- Original Message ----- From: <boost@lists.boost.org> To: <boost@lists.boost.org> Cc: "boris gubenko" <boris.gubenko@hp.com> Sent: Thursday, April 03, 2008 7:53 PM Subject: Re: [boost] [1.36.0] High priority compilers for this release?

Beman Dawes wrote:

...

Good! Let me know which GCC version you settle on.

Will do.

...

I'd like a Linux/ia64 release tester. Whichever version makes the most sense. If you could handle the release testing for that.

Yes, I can. Again, I'll see if we can upgrade to a more recent version of GCC on this Linux machine.

Thanks, Boris

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