Version 21 (modified by c2dietric, 2 years ago)

--

OSSIE 0.8.2 Test and Release Plan (DRAFT) 3/2/2011

Changes to 0.8.2 (things to test)

  • (Works using two nodes on single computer) Multiple instances of the same component on different nodes in the same waveform should work.
    • re-test on two computers. Test by changing configure on one instance and verify that the other one doesn’t change.
  • OSSIE preferences file.
    • Use your own license text. Test by changing, from the Eclipse menu bar, Window->Preferences-> OSSIE -> License and paste in new text. Generate a component, see if the new text shows up in the source files.
  • Create a python component. Test long, bool and string properties, both in OEF and in the generated component.
    • Properties dialog. Create component. Test “string” property. (Check the XML, call configure() and query().)
    • Use this component in a waveform that also has a C++ component, e.g., TxDemo?. Make sure that WaveDash? can configure properties of both components without crashing the waveform.
  • ALF should start nodeBooter
    • ALF tries to find a local nodeBooter. If it can’t, it pops up a dialog. The user needs to click OK on the dialog, then,
      • To run nodeBooter locally, click the nodeBooter icon (rightmost icon on the ALF toolbar) and select the Domain and Device Managers, or
      • To use a remote naming service, click the network icon (two computers) and provide the IP address of the computer that runs the naming service.
  • ALF config. Test under a different install path. (How?) Move /sdr, test compform files. This might require an update to the ALF config file (change installpath in /usr/local/lib/python2.x/dist-packages/alf/config/alf.cfg)
  • Wavedash preferences. (Update properties on refresh)
  • Multi-select drag-and-drop.
    • Drag 2 components onto one waveform
    • 2 components from a waveform onto one device on platform
    • Multiple devices to one platform
  • Test and document any ALF features not already included in User Guide

ALF features include: Launch WaveDash? using IP address from ALF, config file (paths)

  • Test and document new WaveDash? features, document any WaveDash? features not already documented (HTTP server, WaveCLI)
  • Test/document OEF updates (multiselect and multiple component instances/waveform)
  • Test and document OEF features not already included in User Guide

Test and Release Plan

Make a release

  1. Produce an ISO image with Ubuntu 10.04 and dependencies for OSSIE 0.8.1 (Jeffery can rebuild the image by 2/23/11 and he may have documentation for installing the dependencies in 10.04), update dependency installation in user guide if needed.
  2. Add UHD device, nodes, and waveforms.
    1. Install UHD drivers and document installation process
    2. Add the UHD device, nodes, and waveforms to the tarball
    3. Test installation and operation
  3. Submit fixes to trunk
    1. Produce an 0.8.x pre-release tarball (make distclean; make dist), making sure to include updates since the last tarball was made, need to include all new Python files in Makefile.am files, and include new component, device, and waveform directories in bootstrap, configure.ac, and Makefile.am

Test Release

  1. Test tarball, submit changes to trunk
    1. Run through installation instructions and examples in User Guide, update as needed (may require new screen shots)
  2. Run labs 1-8, using the latest versions, identify and document problems/changes. Each lab should take an hour or less, excluding documentation, so this could be done by 2-3 people in a day or two. Changes for 0.8.2 are listed above.

Create final release

  1. Once stable, create 0.8.x branch and tag to 0.8.2 after both svn install and tarball from trunk work.
  2. Test and add any new sample waveforms, e.g., WDC MAC, FlexFrame?, USRP2 AM receiver, Narrowband FM Transceiver (USRP/USRP2 versions) (release these separately)
  3. Post final tarball, OEF, labs, user guide
  4. Create and post live DVD and VM with sounds off, SVN credentials, firefox history, and bash history removed, lab folder and User Guide on desktop, desktop and command line icons for Eclipse, ALF, and WAVEDASH
  5. Note: in /etc/omniORB4.cfg, DefaultInitRef? needs to be set to corbaloc::127.0.0.1, not corbaloc::
  6. OpenEmbedded? recipe and image for Beagleboard and post on web page
  7. Versions of images that include demo applications, Liquid DSP library, GNURadio, GC