Page Comparison

...

• Revisit/document development workflow (from feature to pull request)
  • older branches need a Jenkinsfile to get a Jenkins pipeline
• Avoid API breaks and architecture-critic/breaking changes; How to avoid major architecture degradation? (see, e.g., trend in nightly benchmarks)
  
  • Reviews for architecture-critic changes that cannot be analyzed automatically
    • We cannot enforce it due to a missing integration between Jira and GitHub.
    • We could add a field to tickets "requires-review" and modify the workflow
    • Reviewers can be assigned for a pull request.
      • That's what we will do now
      • Potentially in combination with a Jira comment pointing to the pull request and an assignment of the ticket
  • Christian Wulf (Unlicensed)'s Dazzle tool to monitor API changes from a baseline version to the current one

    Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1662

• Presentation of workflows for issue types
• Definition of epics (improve release creation, improve usability, ...)
  • We see an epic as a long-term activity/goal
  • Everybody agrees that it makes sense; let's do it
• Automation of release creation

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1634

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1616

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1615

• Performance degradation
• How to avoid major architecture degradation? (see, handle API changes
  • Important part as the correct procedure to first deprecate and then remove (e.g.
  , trend in nightly benchmarks
  • )
• Performance degradation
• How to handle
  • a method
  • Dazzle would help here to monitor violations
  • TODO: document process of API changes
•   Docker Containers (Build Process)
  • Automated Build vs. Custom Pipeline
  • Repository Structure

...