User:Floratos
Aris's Home | Enhancements | Release v1.1 | Bison Issues | MRA | Release Testing | Home Page |
Contents
Release Check List
Here is a list of things we need to do/test before putting a new release on the site:
- Check that the main menu option Help->Version lists the correct application and component versions.
- Check that the release notes are complete.
- Check that the online help associated with each component is correct and that it has been versioned using the same version as the one of the component.
- Verify builds for all platforms by installing/running them in "virgin" environments.
- Check that the technical documentation associated with each compoenent is up to date and that it has been versioned using the same version as the one of the component.
- Deploy new Javadocs documentation on the geWorkbench site.
Requirements To Consider
- All gew components should implement the interface WorkbenchPlugin which defines a number of methods such as:
- String getLabInfo(): returns information about the lab where the component originated from.
- String getLicenseInfo(): returns license information.
- String getLibraries(): returns information about 3rd party libraries (with approrpiate attribution).
- VersionInfo getVersion(): returns the version of the component.
- Modify VisualPlugin::getComponent() to return an object of type WorkbenchVisualComponent that extends Component and provides ways to display originating Lab, licence info, libraries and version.
Misc
- Setup nightly build.
Ken's tutorial
Links from old "Developer" section
- Introduction For Developers
- Instructions for the Developer Kit
- Building geWorkbench
- Coding Standards Style Guide
- Javadocs
- CVS Repository
- Screenshots
- Information on .GEAR files, a method of distributing plugins.
- Plugin certification checklist