| | 138 | |
|---|
| | 139 | Add the release name together with linked explanation to: |
|---|
| | 140 | http://www.midgard-project.org/midcom-permalink-d528f84c55ef2299a96c8e9e3ccb5252 |
|---|
| | 141 | |
|---|
| | 142 | Major releases |
|---|
| | 143 | -------------- |
|---|
| | 144 | |
|---|
| | 145 | When making a major Midgard release (i.e. 2.0 or 1.7.0), the following |
|---|
| | 146 | additional actions must be done: |
|---|
| | 147 | |
|---|
| | 148 | * Create a release information sub-site to http://www.m-p.org/midgard/<version> |
|---|
| | 149 | - It should contain at least screenshots, feature list, architecture |
|---|
| | 150 | diagram, and a more verbose and nicely formatted version of the |
|---|
| | 151 | announcement |
|---|
| | 152 | - This sub-site can be created already early on in the release cycle |
|---|
| | 153 | and kept up-to-date, as the final feature set of the release is clarified |
|---|
| | 154 | - It is important to note both developer-oriented and end-user features |
|---|
| | 155 | |
|---|
| | 156 | * When the major release has been done, the midcom-template configuration |
|---|
| | 157 | snippet on the Midgard site must be altered to affect redirects: |
|---|
| | 158 | - /sitegroup-config/midcom-template/config: |
|---|
| | 159 | $GLOBALS['midcom_site']['midgard_version']='1.7'; |
|---|
