| RE: [cdt-dev] Call for status I200605290500 as RC2 |
|
Actually, as a follow up, I am unable to
reproduce the problems Norbert is seeing. The search features work fine for
qhull in a linked folder as I understand the environment from the bug report.
Everyone, please fully document the environment where you are seeing such
failures as I need to fully reproduce them to fix them. Or better yet, send
patches J. The vote does need to be unanimous. A “no-go”
means you don’t think this build is good enough for testing and we value
everyone’s judgement on that. If there are certain features you find not
working but you can think of workarounds, then a bug report should be
sufficient. If you are dead in the water, and you think others will be as well,
then please vote “no-go” and we’ll stop everything until we
can get a fix and do up a new build. Not to put too much pressure on you guys
but please vote by the end of the day so I can either do up another build and/or
get the Callisto train a-rolling. Cheers, (I will be in a better mood when
3.1 is out the door and/or I get more people helping me with indexing J). Doug Schaefer, QNX Software Systems Eclipse CDT Project Lead, Tools PMC member From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer Remember,
the criteria for a no-go is that a feature is not testable. I am able to Open
Declaration/Definitions on various symbols, maybe not the symbols you talk
about in the bug, so I find the feature is testable. In fact,
I’d still recommend releasing even with the defect. It will be very
difficult to get the Search features to work with everyone’s workspace,
especially if I don’t get help resolving these bugs. For this release
I’ll just be happy that the indexer doesn’t hang and we don’t
get any exceptions in the log (which we will because there is one such defect I
don’t think I’ll be able to fix in time). People
can still get their work done even without these features. Remember emacs J. BTW,
I’m a “GO”. I find this build testable. Doug
Schaefer, QNX Software Systems Eclipse
CDT Project Lead, Tools PMC member From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ploett, Norbert Hi Doug, I have tested
a feature that you were working on, the Declarations / Definitons search.
Details see https://bugs.eclipse.org/bugs/show_bug.cgi?id=143388 .
Since in my environment the results are worse than ever I'll vote -1 for
I200605290500. Now I
don't want to sound too harsh, I am aware that there are many other people
around who don't encounter these problems and I can be persuaded to change my mind
if it turns out that I am sort of an execeptional case. Then
again, the result of _my_ tests was that the C/C++ Search features are not
working any more at all in my environment, so for the time being it is -1. Maybe
there will be so many +1s that I'll be outvoted anyway. Or do you need an
unanimous vote? I'll
help gladly to supply more information and help finding the problem if someone
will tell me what to look at. Thanks, Norbert
Ploett Von:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Doug Schaefer Hey gang, please send in your
go/no-go status for this morning’s build as RC2. The main criteria for a
go is that the features you’ve been working on are testable, which if
course is left to interpretation. As such, as a minimum I’d like to hear
from all committers who contributed to RC2 since RC1: Markus S, Doug S, Ken R,
Mikhail K, Mikhail S, Andrew N, Chris R, and Dave I. However, I encourage
everyone else to try it out as well and make sure your features haven’t
been broken. Also, as a reminder, for the
remainder of the 3.1.0 release, please report any bugs that you fix to the cdt-dev
list. I know I have a handful left. The next milestone, RC3 is in two
weeks. After that we should only be fixing critical bugs as we close up to our
final RC4 two weeks after that. Cheers, Doug Schaefer, QNX Software Systems Eclipse CDT Project Lead, Tools PMC
member |