Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Respin of CDT-2.0.1(a) ... libspawner


I too believe that 69330 should be in 2.0.2.   Is the fix high risk?  Will we need to do a large test activity?

So far we have the following committed to 2.0.2:  73250,  71437,  72901 from Alain, and 73378 from Andrew

        -Dave




"Alain Magloire" <alain@xxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx

09/08/2004 09:38 AM

Please respond to
cdt-dev

To
cdt-dev@xxxxxxxxxxx
cc
Subject
Re: [cdt-dev] Respin of CDT-2.0.1(a) ... libspawner





>
> I think that we should spin a 2.0.2 to pick up these changes -- I think
> that if we respin 2.0.1 we will get confusion (I will certainly be
> confused :-)
>

+1

> There are a couple of open defects that have been tagged for 2.0.1.   I
> would like to evaluate these defects and then spin a RC for 2.0.2. (or
> whatever number we decide on)
>

2.0.2
We've already updated the branch for a few PRs, see the previous email on this thread
for the numbers.

> Does anybody what to add more defects?  (I would like to try to limit the
> defects to critical ones)
>

PR 69330, is a good candidate.  Talk to aniefer for more details.


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top