Rev 78 |
Rev 80 |
Go to most recent revision |
Last modification |
Compare with Previous |
View Log
| RSS feed
Last modification
- Rev 79 2007-07-25 08:59:45
- Author: rsolanki
- Log message:
- DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
<b>DEVI-021352</b>
For projects such as Sydney and Seattle that have an associated MASS_REF release we need a mechanism to prevent users adding/modifying a .mas or a .cr pakage to the Sydney/Seatte release. The package must be manipulated in the associated MASS_REF release.
I have marked this issue critical as it keeps on causing problems that are taking valuable time to resolve.
Suggested solution.
Need per-release flag to indicate that the release has a related MASS_REF release.
It would be very nice to actually configure the associated ( linked) MASS_REF set - this could be used inplace of the flag.
When the flag is set then it should not be possible to add a .mas/.cr package within the release, nor should it be possible to: create a new version of a .mas/.cr package or change the version.
<b>Release Date:</b> 04-Jan-2006