Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
77:releasenotes [2021/07/09 15:48] – emr77:releasenotes [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 7: Line 7:
 Starting with version 7.7, we plan to **increase the Stages release frequency and issue a new release every 3-4 months**. As a consequence, previous releases will drop out of maintenance earlier than before. Starting with version 7.7, we plan to **increase the Stages release frequency and issue a new release every 3-4 months**. As a consequence, previous releases will drop out of maintenance earlier than before.
  
-We are aware that not all of our customers want or are able to upgrade their system every few months. For those customers, we will keep **Stages version 7.6 under Long Term Support (LTS)**. An LTS release will be maintained for at least two years until a new LTS release will replace it.+We are aware that not all our customers want or are able to upgrade their system every few months. For those customers, we will keep **Stages version 7.6 under Long Term Support (LTS)**. An LTS release will be maintained for at least two years until a new LTS release will replace it.
  
 So if you want to benefit from a stream of new features every few months, feel free to upgrade to version 7.7. You need to be prepared to upgrade to version 7.8 within 3 months after it is released though. So if you want to benefit from a stream of new features every few months, feel free to upgrade to version 7.7. You need to be prepared to upgrade to version 7.8 within 3 months after it is released though.
  
-If you want to upgrade your system less frequently, we suggest to stay on version 7.6 an benefit from its Long Term Support.+If you want to upgrade your system less frequently, we suggest to stay on version 7.6 and benefit from its Long Term Support.
  
 ===== Association Grouping* ===== ===== Association Grouping* =====
Line 45: Line 45:
 Before version 7.7, interfaces were shown between process versions with the same name. This capability has been removed. Before version 7.7, interfaces were shown between process versions with the same name. This capability has been removed.
  
-===== Scheduled process releases =====+===== Scheduled Process Releases =====
  
 Some process changes should be made effective at a specific date, e.g. at the first day of a month. With Stages 7.7, the release automations can be configured so reviewers and/or approvers can set a specific date and time when the process will be released and marked as valid. Some process changes should be made effective at a specific date, e.g. at the first day of a month. With Stages 7.7, the release automations can be configured so reviewers and/or approvers can set a specific date and time when the process will be released and marked as valid.
Line 55: Line 55:
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=53cdc6&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-schedulereleasedate2.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-schedulereleasedate2.png?direct&800x694  }}]]When the automation is being executed, the respective participants can then either select the date and time when the release should take place or select "After automation has finished" to immediately release the process. [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=53cdc6&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-schedulereleasedate2.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-schedulereleasedate2.png?direct&800x694  }}]]When the automation is being executed, the respective participants can then either select the date and time when the release should take place or select "After automation has finished" to immediately release the process.
  
-===== Value streams are available by default =====+===== Value Streams are available by Default =====
  
-The value stream mapping capabilities that have been introduced in previous releases are now available in each new Stages installation. To enable value streams, select the "Unified Configuration (with Value Streams)" metamodel under ''Management > Settings''.+Value streams are a method to manage cross-functional and cross-organizational activities and provide macro views of a process landscape. 
 + 
 +The value stream mapping capabilities that have been introduced in previous Stages releases are now available in each installation. To enable modeling value streams, select the "Unified Configuration (Value Streams)" metamodel under ''Management > Settings''.
  
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=cee097&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-valuestreams.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-valuestreams.png?direct&800x219  }}]] [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=cee097&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-valuestreams.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-valuestreams.png?direct&800x219  }}]]
Line 63: Line 65:
 If you have a customized metamodel version, please contact your respective product consultants for more info. If you have a customized metamodel version, please contact your respective product consultants for more info.
  
-===== Compliance overview report =====+===== Compliance Overview Report =====
  
 A new report has been added that can be run from a reference model workspace to provide an overview of all mappings and coverage across all workspaces where that reference model has been mapped. A new report has been added that can be run from a reference model workspace to provide an overview of all mappings and coverage across all workspaces where that reference model has been mapped.
Line 71: Line 73:
 As the report shows both the coverage and the number of mappings for a particular standard requirement, it is also useful to detect mappings that have been created, but not rated for a specific coverage yet. As the report shows both the coverage and the number of mappings for a particular standard requirement, it is also useful to detect mappings that have been created, but not rated for a specific coverage yet.
  
-If you are upgrading from a previous version, you can download the report here.+If you are upgrading from a previous version, you can [[:reports:start#compliance-overview|download the report here]].
  
 ===== Process Feedback in Codebeamer ===== ===== Process Feedback in Codebeamer =====
Line 111: Line 113:
 </code> </code>
  
-===== Support for feedback issue collectors =====+===== Support for Feedback Issue Collectors =====
  
 We added the new [[:77:process_feedback_link|feedback system link]]. A stages user who wants to give feedback will be directed to a issue collector page of the specific feedback system. The user will see a form with some fields filled out beforehand by Stages. We added the new [[:77:process_feedback_link|feedback system link]]. A stages user who wants to give feedback will be directed to a issue collector page of the specific feedback system. The user will see a form with some fields filled out beforehand by Stages.
Line 127: Line 129:
   * The access to PDF exports can now be controlled via its own security domain. While upgrading to version 7.7, all users with process read permissions are automatically given this new permission.   * The access to PDF exports can now be controlled via its own security domain. While upgrading to version 7.7, all users with process read permissions are automatically given this new permission.
   * The Y scales in the user activity statistics under ''Administration''  have been switched for better readability.   * The Y scales in the user activity statistics under ''Administration''  have been switched for better readability.
 +  * The "Phases" switch in the Flow visualization has been disabled by default. As most clients are using multiple lifecycles (= phase models), it has lost its usefulness and showed incorrect information. If you would like the switch to be re-enabled, please contact your consultant.
 +
 +===== End of Life for CMMI in Stages =====
 +
 +CMMI (Capability Maturity Model Integration) has been one of the first quality models for software development. For over 30 years, numerous organizations matured their software development practices with the help of CMMI and many other standards and quality models have been inspired by it. Starting with CMMI V1.2, the standard has been available as a reference model in Stages, culminating with the release of CMMI V2.0 a few years ago.
 +
 +In recent years, the relevance of CMMI in the industry has diminished and other standards like Automotive SPICE have taken its place. Therefore, we have decided to not support CMMI model versions beyond the current version 2.0. CMMI V2.0 will be the last version available as a reference model for Stages. Consequently, the CMMI reference model will be excluded from future maintenance contracts.
 +
 +Method Park has been a proud supporter of CMMI for over 15 years and we thank everyone in the CMMI community for their inspiration, contributions, and support.
 +
 +===== How to Upgrade to Version 7.7 =====
 +
 +Please [[stages-support@methodpark.com?subject=Upgrade to V7.7|contact our customer care team]] to request the installer downloads if you run Stages on-premise or request an upgrade of your managed Stages Cloud instance. Alternatively, you can talk to your dedicated product consultant for more info.
  
 ===== Notes ===== ===== Notes =====