Hi
Lars,
In general, I would
like to make no code changes to the MBS at this point in the schedule.
Any fix that I would consider would need to be either:
- A “show stopper”,
i.e., some aspect of the functionality is unusable without a
fix
- A combination of
high-priority and low-risk
Your suggested change
doesn’t seem, to me, to meet either criteria.
Here are my thoughts
on where we are in the schedule – maybe I’m wrong, and we can discuss at the
CDT call tomorrow.
The Final Release
Candidate is scheduled for a week from today (7/27). I think the process
is to take a few days to test, and then declare it to be the GA release. This
means that RC2 was the last CDT 3.0 milestone that will receive more than a
few days of testing. Of course, we have the “documentation” time that
was added, but I believe the code is supposed to be frozen.
At this year’s
EclipseCon, I attended a talk on the Eclipse development process. One
aspect of the talk was about the “end-game” and restricting the changes that
are made as you go through the end of the release. The speaker (I think
it was Erich Gamma) discussed that, in their experience, 1 out of 10 fixes
results in a regression. I’ve always believed that every fix has an
associate risk of breaking something else. I don’t know what the ratio
is and it’s likely to be different on different projects, but let’s use 1 in
10 as an example. At RC2, CDT had about 60 open bugs that were intended
to be addressed before GA. If those 60 bugs are fixed, there will be 6
unintended and undiscovered regressions in the GA. The MBS had 0 bugs at
RC2, and I think we have fixed 2 since then – so, we have a 33% chance of a
regression.
Regards,
Leo
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of
Lars.Kurth@xxxxxxxxxxx
Sent: Wednesday, July 20, 2005 3:34
AM
To:
cdt-dev@xxxxxxxxxxx
Cc:
Chetana.Koulagi@xxxxxxxxxxx; EXT-Lokesha.Ramu@xxxxxxxxxxx;
EXT-Jagan.Varanganti@xxxxxxxxxxx
Subject: [cdt-dev] Extra access method
setUserDefinedMacros(StorableMacros)in ManagedProjec
t?
Hi,
I know it's quite late in the
project for CDT3.0, but I was wondering whether you would be OK with adding an
extra public access method to
org.eclipse.cdt.managedbuilder.internal.core.ManagedProject.
/*
* Set user defined macros
*/
public void setUserDefinedMacros(StorableMacros macrosToSet ) {
userDefinedMacros = macrosToSet;
}
We would need this because we
are implementing a build configuration management view (in a typical Symbian
environment it is not common to work with more than 20 build configurations)
which amongst other things allows to delete a configuration, but re-instate a
back-up if needed later. We can work around not having the access
functionality, but it will be much harder and messier to restore user defined
macros.
Please let me know what you
are thinking. If you are happy with this, I can submit a patch as soon as I
get the all clear.
Best Regards
-- Lars
**********************************************************************
Symbian Software Ltd is a company registered in England and Wales with
registered number 4190020 and registered office at 2-6 Boundary Row,
Southwark, London, SE1 8HP, UK. This message is intended only for use by the
named addressee and may contain privileged and/or confidential information. If
you are not the named addressee you should not disseminate, copy or take any
action in reliance on it. If you have received this message in error please
notify postmaster@xxxxxxxxxxx and delete the message and any attachments
accompanying it immediately. Neither Symbian nor any of its subsidiaries
accepts liability for any corruption, interception, amendment, tampering or
viruses occurring to this message in transit or for any message sent by its
employees which is not in compliance with Symbian corporate policy.
**********************************************************************