VirtualSatellite4-Core icon indicating copy to clipboard operation
VirtualSatellite4-Core copied to clipboard

Release Version 4.17.0

Open PhilMFischer opened this issue 1 year ago • 0 comments

Virtual Satellite Release Version 4.17.0

This ticket captures all release related work of the VirtualSatellite4-Core release

  1. Perform version update:
  • [X] Checkout/Update the Development branch
  • [ ] Remove current integration branch (Make sure no one else is integrating at the moment)
  • [ ] Create new integration branch from development branch
  • [x] Run ant script to update version numbers (open build.xml and start the updateVersions task)
  • [x] Check if the server APIs had changes and update the version numbers in the servlets if necessary
  • [x] Check if there are unreleased changes on the Ecore data model (open dvlm.ecore, check if History > Release (not yet released is empty))
    • [x] Create a Edapt release of new changes (Open the DVLM-Ecore model; open the view "Operation Browser", click "Release" with "not yet released" selected, set the next version)
    • [x] Generate model and edit code from Ecore (Open dvlm.genmodel, right click on the context menu)
    • [x] Adjust DVLM version number in factory overwrite: in the plugin.xml of the de.dlr.sc.virsat.model project. (Extension point: org.eclipse.emf.ecore.factory_override)
    • [x] Adjust DVLM version number in ConceptLanguage.xtext and run GenerateConceptLanguage.mwe2
    • [x] Adjust DVLM version number in EquationDSL.xtext and run GenerateEquationDSL.mwe2
    • [x] Regenerate concept.xmi of all relevant projects (launch "VirSat Core Concept IDE", import projects (with nested), build all)
  • [ ] Check that Java API Doc is working in our Concept-IDE - If not update the Java API Doc being registered in the Java doc plugin
    • To check if it works, create a VirSat App and test if the Java API and Model APi from VirSat is backed by JavaDoc
  • [x] Make sure application launches without errors from the product launcher
  • [ ] Merge integration branch into development branch (Pull Request named "Integration 4.x.x - Remerge Versions")
  1. Perform integration on integration branch:
  • [x] Apply all needed fixes
  • [x] Update the release notes
  1. Update master/release branch:
  • [x] Merge integration branch into master branch (Pull Request named "Release 4.x.x")
  • [x] Create Release Tag
  1. Merge back integration branch:
  • [x] Merge integration branch into development branch (Pull Request named "Integration 4.x.x - Remerge Fixes")

Well Done!! You should have a new Virtual Satellite Release :rocket:

PhilMFischer avatar Aug 05 '24 13:08 PhilMFischer