... | ... | @@ -34,15 +34,17 @@ by using the Eclipse multi-file search and replace function. |
|
|
“OK”
|
|
|
- Replace: “a.b.c”
|
|
|
- With: “d.e.f”
|
|
|
6. Run a local build by selecting “Run As >Build All” and observe
|
|
|
6. Use the file search again to find the containing text *a.b* (Current major version number, e.g.,
|
|
|
2.14). Manually replace the few search results which indeed use the old version number (attention: Not all results will need to be replaced - the search will likely also find false positives!).
|
|
|
7. Run a local build by selecting “Run As >Build All” and observe
|
|
|
if any error occurs.
|
|
|
7. If the build succeeds, commit the changes. **NOTE:** You must commit
|
|
|
8. If the build succeeds, commit the changes. **NOTE:** You must commit
|
|
|
to multiple repositories. Since these are submodules, you may need
|
|
|
to specify the remote branch: The issue number from the previously
|
|
|
created ticket shall be used.
|
|
|
8. Issue a MR for the plugin `org.fortiss.af3.root` and each of the
|
|
|
9. Issue a MR for the plugin `org.fortiss.af3.root` and each of the
|
|
|
submodules where there has been a version update.
|
|
|
9. After merging, ensure that the AF3 version is configured correctly. (Check maven releng repository for correct commit messages)
|
|
|
10. After merging, ensure that the AF3 version is configured correctly. (Check maven releng repository for correct commit messages)
|
|
|
|
|
|
### Update “What’s new” Page
|
|
|
|
... | ... | |