[linuxtools-dev] Help needed to test 0.6 release

[Andrew Overholt <overholt@xxxxxxxxxx>]

Hi,

Our 0.6 release is the first time we'll have been a part of the Eclipse
simultaneous release.  It's coming up very soon and we want it to be a
solid part of the Helios release.  If you have a bit of spare time,
here's how you can help ensure it's great!

1. Test installation from our update site
  - start with the latest Eclipse SDK (RC3, RC4, etc.)

    http://download.eclipse.org/eclipse/downloads

  - extract it on your system and run it with ./eclipse
  - add our Helios update site (what will be a part of the main Helios
    site):

    http://download.eclipse.org/technology/linuxtools/update-helios

  - install any/all of the Linux Tools features
  - restart when prompted
  - verify that the Linux Tools features, etc. are installed properly
    and don't have broken signature icons in the About dialogue (Plugins
    tab)

2. Test installation from the Helios repository
  - same as above but just install what's in the Helios repository
    (should be enabled by default with an SDK download)

3. Test EPP package
  - this year there will be a "Linux Developer" package which is just a
    combination of the Eclipse Platform, the CDT, and the Linux Tools
    features
  - you can download one, extract it, run it, and Linux Tools features
    should be present (again, without broken signature icons in the
    About dialogue's Plugins tab)
  - downloads that will become Helios packages are here:

    http://www.eclipse.org/epp/download.php

4. Verify functionality
  - once you have the Linux Tools features installed, try them out :)
  - be mean; don't let us get off easy!  File bugs for whatever doesn't
    work as you expect, even if you think it may just be the way you're
    used to something.  Maybe we designed something in a way that's not
    great.
  - try out your existing C and C++ code bases and:
  -- see if you can use OProfile or Valgrind
  -- see if you can properly debug with the CDT
  -- verify that you can generate a call graph (if you have SystemTap
     installed on your system)
  -- make sure your Autotool'd project builds properly
  -- examine an LTTng trace
  -- try out the GCov and GProf plugins and make sure the results match
     what you'd expect
  -- edit an RPM specfile
  -- try importing an SRPM and exporting an RPM
  -- verify that glibc and libstdc++ API information is available when
     you hover in a C or C++ file 
  - file bugs if you get unhandled exceptions or error dialogues

5. File bugs
  - I can't emphasize enough that we'd rather have bugs filed than have
    issues go unnoticed
  - more bugs are better than fewer bugs

    https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Linux Tools

6. Communicate with the developers and other users
  - on the newsgroup
    (http://www.eclipse.org/forums/index.php?t=thread&frm_id=60)
  - on the mailing list
    (https://dev.eclipse.org/mailman/listinfo/linuxtools-dev)
  - on IRC (#eclipse-linux on Freenode)

Thanks for your help making Helios great!

Andrew