help scheduling issues

[Martin Sebor <se...@roguewave.com>]

Hi guys,

Can everyone (especially committers) please review their open issues
(either those assigned to them or those they reported) to see what we
can reasonably expect to knock off before the release and what needs
to be deferred?

It would also help to go through unassigned issues if we can spot any
low hanging fruit or otherwise determine what's too big and should be
scheduled post-4.2.

My goal is to do a feature freeze sometime in early to mid September
and code freeze about a month after that. We need to have all issues
currently scheduled for 4.2 either fixed in 4.2 or rescheduled for
later.

To help with this task here are Jira queries to pull up our issues:

Andrew/Unassigned: http://tinyurl.com/yvdcja
*/Andrew:          http://tinyurl.com/2btbgh

Farid/Unassigned:  http://tinyurl.com/yoqxy2
*/Farid:           http://tinyurl.com/2fz5ex

Martin/Unassigned: http://tinyurl.com/yt2qxs
*/Martin:          http://tinyurl.com/yw5u3f

Travis/Unassigned: none
*/Travis:          http://tinyurl.com/3b49j8

Thanks
Martin

Re: help scheduling issues

[Mark Brown <mb...@inbox.com>]

> -----Original Message-----
> From: ablack@roguewave.com
> Sent: Fri, 24 Aug 2007 10:38:26 -0600
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: help scheduling issues
> 
> Greetings all.
> 
> I've taken a little time to glance over the open tasks which I reported
> but have not been assigned.  My analysis of these issues is as follows:
> 
> 336 (allow multiple config.h files in the same installation directory)
> 	Marked as critical for the 4.2.0 release, and not anywhere on our radar
> as far as I can tell.

This seems like a useful feature. I commnonly work with multiple builds of stdcxx at the same time. Having them all share the same directory would save space and simplify my makefiles.

-- Mark

____________________________________________________________
FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop!
Check it out at http://www.inbox.com/earth

Re: help scheduling issues

[Martin Sebor <se...@roguewave.com>]

Andrew Black wrote:
> Greetings all.
> 
> I've taken a little time to glance over the open tasks which I reported
> but have not been assigned.  My analysis of these issues is as follows:
> 
> 336 (allow multiple config.h files in the same installation directory)
> 	Marked as critical for the 4.2.0 release, and not anywhere on our radar
> as far as I can tell.

Yes, that's definitely one we need to discuss.

> 
> 361/362 ([Intel C++ 9.1.042] hangs compiling conditional initialization
> in template code (22.locale.money.put.cpp))
> 	361 is marked as Major, no Affects or Fix versions
> 	362 is marked as Critical, fix 4.2.0.
> 	This pair of linked bugs affects a specific set compiler/platform
> combinations, and has been fixed by the compiler vendor in newer
> versions of the compiler.  Given this, I think this pair should be
> reduced in priority and either rescheduled for 4.2.1 at the earliest, or
> closed.

Agreed. I think it's fine to close them as Won't Fix since there
is a simple workaround: update to a working compiler patch. Can
you go ahead and take care of it?

> 
> 261 (runall should parse tests and examples in the same manner)
> 366 (Add benchmarking framework)
> 	These are minor enhancements, without a specified Affects or Fix
> version.  They probably can be left unscheduled, and I can't see a
> reason to assign either a release of anything earlier than 4.2.1.

Also agreed. Please go ahead and reschedule these.

Thanks
Martin

Re: help scheduling issues

[Andrew Black <ab...@roguewave.com>]

Greetings all.

I've taken a little time to glance over the open tasks which I reported
but have not been assigned.  My analysis of these issues is as follows:

336 (allow multiple config.h files in the same installation directory)
	Marked as critical for the 4.2.0 release, and not anywhere on our radar
as far as I can tell.

361/362 ([Intel C++ 9.1.042] hangs compiling conditional initialization
in template code (22.locale.money.put.cpp))
	361 is marked as Major, no Affects or Fix versions
	362 is marked as Critical, fix 4.2.0.
	This pair of linked bugs affects a specific set compiler/platform
combinations, and has been fixed by the compiler vendor in newer
versions of the compiler.  Given this, I think this pair should be
reduced in priority and either rescheduled for 4.2.1 at the earliest, or
closed.

261 (runall should parse tests and examples in the same manner)
366 (Add benchmarking framework)
	These are minor enhancements, without a specified Affects or Fix
version.  They probably can be left unscheduled, and I can't see a
reason to assign either a release of anything earlier than 4.2.1.

--Andrew Black