Project:
| View Revisions: Issue #17785 | [ Back to Issue ] | ||
| Summary | 0017785: Maturity level configuration is lost after updating to next MP | ||
| Revision | 2011-06-29 17:43 by gorka_gil | ||
| Description | During the test phase we have detected that the maturity level configuration is lost after updating to next MP | ||
| Revision | 2011-06-29 09:38 by gorka_gil | ||
| Description | During the test phase we have detected that the maturity level configuration is lost after updating to 2.50MP31 | ||
| Revision | 2011-06-27 16:55 by psarobe | ||
| Steps To Reproduce | 1. Install mp30 2. Go to module management console. Change the maturity level for core to QA 3. Scan for updates and install MP31 4. Rebuild After rebuilding login again and notice that the maturity level for that specific module "Core" has been removed |
||
| Revision | 2011-06-27 16:51 by psarobe | ||
| Steps To Reproduce | 1. Install mp30 2. Go to module management console. Change the maturity level for updates or core to QA 3. Scan for updates and install MP31 4. Rebuild After rebuilding login again and notice that the maturity level is different. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |