What constitutes a release folder?
-
Test plan for the release
-
Cycles of the release
-
Releases of the application
-
Requirements for the release
A release folder in the Releases module contains the releases themselves (version releases of your application). It doesn't contain test plans (those are in Test Plan), cycles (those are within releases), or requirements (those are in Requirements module).
A release folder is the container that holds the actual releases (builds/versions) of the application that have been shipped or are being tracked through the release-management process — e.g., Release 1.0, Release 1.1, etc. It is not the same as: a test plan (a testing artifact, usually filed under a test-management folder), release cycles (schedule/phase information, tracked separately as milestones), or requirements (product/business specs, tracked in a requirements repository). So 'Releases of the application' is the best fit for what a release folder actually contains. Note this is fairly generic QA/release-management terminology and could vary slightly by tool (JIRA, Rational, HP ALM, etc.), so treat it as the conventional definition rather than a hard technical fact.