RE: [cdt-dev] CDT 3.0 Closing

[Alain Magloire <alain@xxxxxxx>]

> 
> I have a couple of thoughts, for whatever they are worth...
> 
> > From Doug: This is one of the biggest concerns I have with the CDT
> today. The
> quality and timing of our releases are pretty unpredictable.
> 
> This is certainly a problem for the sort of projects that I have worked
> on throughout my career (30 yrs on developer tools).  Typically on these
> projects we are asked to make commitments for functionality and schedule
> 6 - 12 months in advance.  Depending upon a CDT release to ship on a
> particular date with acceptable quality has been "challenging".
> 
> My initial reaction to how to make this work better is to have a longer
> testing period after "feature freeze" than we currently do.  Of course,
> we need to stick to the meaning of "feature freeze".  Also we would need
> to increase the "selectivity" of which bugs to fix as we proceed through
> the testing period towards a final release.
> 
> >  From Dave: I guess this leads to the question of which defects do you
> think QNX can fix after RC3 but before RC4?    At IBM we were assuming
> that ALL the defects would be addressed by RC3, and we were only doing
> Doc work after this.
> 
> This was my assumption as well.  Here is one reason why I don't want to
> wait until RC3 is done before I know whether there will be an RC4.  I
> don't want to make any changes after RC"final - 1" unless it is a very
> important fix.  Right now, I'm assuming RC3 is the final RC.  If there
> is going to be an RC4, this might change the bugs that I'm willing to
> fix now.
> 

Loud and clear and I also agree with the testing part. But again, they are
things beyond the control of the CDT project. This is always the problem for
open source; I can not force you to fix that xx PR even if I know it is
vital to the release of my own product.  Open source give us a lot of mind
share and other benefice but we also have to deal with its ... what the
corporate folks would say lack of structure or control.  We seem to deal
with this by an excellent cooperation between the committers and also good
communication.

As a committer, I'm please to see the constant iteration improvement we do
at every release and yes also aware of some of the shortfalls of the project
8-(.

Of course my 2 cents Canadian value.