Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] CDT 5.0 Rampdown Policy

Perhaps everyone should send a quick message to the list giving an update on what they've been working on and what their plans are between now and the final release. That way we all get a general idea of what everyone is thinking and doing.

I'm putting the finishing touches on the parsers I've been working on, which I have named the LR parsers, because they use an LALR parser generator. I now have working parsers for C99, UPC and C++, with full support for ambiguity resolution. The LR parsers pass all the tests in the core parser test suite, except for gcc extension tests. I plan on adding support for gcc extensions in the future but I don't think I will have time before the 5.0 release (and besides that probably qualifies as a feature). Some of the gcc extensions are designed so that they can be defined as macros for parsers that don't support them, so I may do that as a temporary measure.

The core tests pass but there are failures when running the UI test suite with these parsers replacing the DOM parsers. Mostly these are problems with content assist, and I plan on fixing these before the release.

I also plan on doing some performance testing. I'm not really worried about performance all that much because the C99 parser had decent performance last time around. Also Jason did some performance tests last time and it turned out that some of the performace issues were coming from the preprocessor that I wrote. I have since deleted that preprocessor and replaced it with Markus' CPreprocessor so that should help things out even more.

I still haven't tried running the C++ parser on firefox source yet. That should be fun :)

I haven't been opening bugs for any of the stuff I've been working on, but I will from now on.


Mike Kucera
Software Developer
IBM CDT Team, Toronto
mkucera@xxxxxxxxxx



Inactive hide details for "Schaefer, Doug" ---05/16/2008 10:27:06 AM---Hey guys, as discussed at the conf call, here is the ram"Schaefer, Doug" ---05/16/2008 10:27:06 AM---Hey guys, as discussed at the conf call, here is the ramp down policy for CDT 5.0

          "Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>
          Sent by: cdt-dev-bounces@xxxxxxxxxxx

          05/16/2008 10:26 AM

          Please respond to
          "CDT General developers list." <cdt-dev@xxxxxxxxxxx>

To

"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

cc


Subject

[cdt-dev] CDT 5.0 Rampdown Policy

Hey guys, as discussed at the conf call, here is the ramp down policy for CDT 5.0

Release Candidates:
RC1 - Build Fri, May 16 - Release Tues, May 20
RC2 - Build Fri, May 23 - Release Mon, May 26
RC3 - Build Fri, May 30 - Release Mon, June 2
RC4 - Build Fri, June 6 - Release Mon, June 9
Final - Build Fri, June 13 - Release Mon June 16

Starting immediately (M7/RC0), no new features.

Starting Fri, May 30 (after M3 build), all commits must be accompanied with a notification to the cdt-dev list providing a link to the bug that was fixed. The CVS logs will be monitored to ensure compliance (i.e., I'll send a nasty mail if you forget to notify us of a change :)

The idea is to ensure we're only fixing bugs during the RC cycle. And as we get closer, it's important that we all understand what's changing and can object if too much is changing too late to ensure we stabalize by the end of the release.

I'll also continue to send countdown e-mails as we go to track open bugs. Please make sure you mark bugs you are thinking of fixing with the 5.0 target milestone.

I'll add this to the CDT wiki and the Ganymede process wiki.

Cheers,
Doug._______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

GIF image

GIF image

GIF image


Back to the top