There's no need to change from the code control tools (e.g. CVS, Subversion, Perforce) that you use today. Conversely, you will discover that CogniDox is far superior to code control software for the task of managing and publishing releases. This is true whether you're following an Agile or a traditional waterfall methodology.
At the start of a project or release cycle the software team (or manager) create a CogniDox category with part numbers for the upcoming release. Then,for each SVN document file that will be published externally they set a property (called "cognidox") on the file to the related CogniDox part number. On a continuous basis, each developer will commit new changes as normal into SVN, and extend top-of-tree as a result. When a file is committed, SVN reads the property, and sends the file to CogniDox with the commit message. If desired, the SVN revision can also be added as a tag to the file. As time progresses, the Release Candidate (RC) is declared stable/ready and is issued and approved in CogniDox.
In parallel with code development all the other activities associated with software release management are progressing. System validation and verification tests are run to ensure release-readiness. The mechanisms for software delivery and distribution are put in place. Working with Sales, the details of software license management & delivery tracking are agreed. The software release documentation is written, reviewed and made ready for publication.
When it is time for release day, all of the software is prepared as a package with name, version, release, target architecture with the original source archive (e.g. .tar, .tgz) included. The complete package will also contain the user documentation and release notes.
When it is released it will appear on the Extranet available for customer download. They will only see the release if they are authenticated and are licensed to do so.
For Software Engineers