Currently a TeamForge release is not always complete.
The TeamForge application integrates with Subversion Edge, has training material which depends on the version, the documentation. All this kind of assets should be releases as a set.
So per quarterly release it should be clear at the moment you release:
- what is in the TeamForge release (this is often well done)
- related tools (Subversion Edge) is updated in case of dependencies
- documentation is consistent with release (new functionality is well defined)
- training material is updated, or I is clearly indicated this release is without training updates
by: Hans T. | over a year ago | Documents
Comments
Speaking for the Documentation part, TeamForge documentation is always complete when a release happens. This includes new feature docs, Release Notes, and so on. This is also being reviewed and signed off by relevant stakeholders from the Engineering/PMO.