Re: [cdt-dev] CDT 2.0 M8 end of game plan

[Douglas Schaefer <dschaefe@xxxxxxxxxx>]

The biggest one for me is the broken emacs keys in the Java editor. At 
least there some of them work, just not the ones you need to actually make 
them useful. In the CDT editor, they are completely broken, at least as 
far as I can tell.

Doug Schaefer, IBM's Eclipse CDT Architect
Ottawa (Palladium), Ontario, Canada



"Henning Riedel" <kesselhaus@xxxxxxx> 
Sent by: cdt-dev-admin@xxxxxxxxxxx
03/27/2004 08:35 AM
Please respond to
cdt-dev


To
cdt-dev@xxxxxxxxxxx
cc

Subject
Re: [cdt-dev] CDT 2.0 M8 end of game plan







> I assume the error you got was on saving files in the CDT editor. That 
was
> nasty. I have just checked in a fix into HEAD. I'll set the build to run 

> Sat and Sun at 3 a.m. EST that should fix things up.

Yep, that has been it. The error was about an assertion "R/" something.
The build today fixed it.

> M8 looks real cool but the amount of features that landed on Tuesday, 
and 
> the churn that happened on each build right up until Friday has me a 
> little worried about the quality of it. Following the integration builds 

> over the next couple of weeks might be prudent.

Well, I too was very surprised after looking at the several I-builds going
on, and out of a sudden, an M8 was ready. I'm not sure in which state M8 
is,
lets test it (both :) ).

Happy testing,
Henning

> Cheers,
> Doug Schaefer, IBM's Eclipse CDT Architect
> Ottawa (Palladium), Ontario, Canada
> 
> cdt-dev-admin@xxxxxxxxxxx wrote on 03/26/2004 08:57:19 PM:
> 
> > 
> > > Hey all,
> > 
> > Hey Doug, ;)
> > 
> > > We are going to take the Eclipse platform M8 build and the Monday 
> morning 
> > > CDT build and bash the heck out of it. The objective is to ensure 
the 
> > > features we are working on are stable enough for the CDT user 
> community to
> > > use and that the CDT is overall stable enough (debug may be the 
known 
> > > exception). The goal would be to ensure that we can declare the 
> Wednesday 
> > > morning CDT build the CDT 2.0 M8 build. I encourage anyone out there 

> who 
> > > has the time to help us out with testing and bug raising. Hopefully 
we
> can
> > > end up with a pretty good M8 especially given the churn in the 
Eclipse
> 
> > > platform M8.
> > 
> > Just pulling the M8 build over that thin wire here.
> > I had a little trouble with the Ecl.-I2004032[356] builds and the CDT 
> builds
> > from yesterday and today with a strange error, I never got before. 
Maybe
> M8
> > will already fix it.
> > 
> > > 
> > > And as an update to those who aren't following the 
platform-releng-dev
> 
> > > list, fixes are still piling in for the M8 candidate build which 
> should 
> > > have happened already. In general, their process goes: Tuesday - 
test 
> > > candidate, Wednesday - test and fix, Thursday - milestone candidate, 

> > > Friday - declare milestone. The are about a day behind as the test 
> > > candidate wasn't declared until Wednesday. But they may still pull 
off
> a 
> > > Friday milestone yet.
> > 
> > Was this the plan for the almost ending week?
> > 
> > I liked the stuff seen from the last Ecl.-builds this week. The intro
> > feature looks damn nice. I already have an idea on this,... see if i
> > can work out
> > something.
> > 
> > *hibble* looking for an CDT M8 for an almost sane new build env.
> > 

-- 
+++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz 
+++
100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz

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