Reminder: Tagging beta6 this weekend

David Nolden zwabel at googlemail.com
Wed Nov 4 14:50:21 UTC 2009


Am Dienstag 03 November 2009 09:30:44 schrieb Andreas Pakulat:
> Hmm, I'm reluctant to do this now, apparently people have already
> downloaded the beta and its "up there" since more than a day now. Also
> the next beta isn't far away anyway - only three weeks from now.
Hmm that's a pity, especially when considering that ubuntu seems to ship 
kdevelop4 betas as 'stable' now. This beta might be a step back in stability 
due to that crash, which gives me a bad feeling.

I've found another such crash and fixed it in r1044721. It is very easy to 
reproduce. Just take the following exemplary code snippet:
"
void test(int q = 3);

void test(int q)
{
}
"

And add another parameter before the 'q' in the definition -> Bang

I hope that's it with signature-assistant regressions (I should be more 
careful when merging code from bug-reports). Generally I think in future we 
should again do a mini-freeze before betas, to make sure that they really have 
better quality than random snapshots. Or maybe we should 'tag' the beta as a 
branch, and then 2 weeks later merge all important fixes that happened in 
meantime before releasing it.

How to proceed now I'm not sure, but I think this one is a show stopper, what 
do you think?

Greetings, David




More information about the KDevelop-devel mailing list