PCM Development/Palladio Coding Session/20221107 Developer Meeting
Organisational
- Date: 07.11.2022, 10.30-18.00
- Location: Room H0.124a, Holderäckerstraße 36, 70499 Stuttgart
Agenda
- 10.30-11.00: Opening, Stand-Up: How does Palladio relate to your research? What feature of Palladio did you use in the last 6 months?
- 11.00-12.30: Developement Teams Get-Together (Build / Performance / Vertraulichkeit / Extraktion) - 45min discussion / 45min presentation + discussion in plenum
- Create roadmap for the next 6 months; What are long-term goals?
- What happened in the last 6 months?
- Github Topics + document your topics in the wiki
- Lunch 12.30-14.00
- 14.00-14.30: Ticketing-System, Jira: Opinions + Alternatives
- 14.30-15.15: Quality assurance
- Problems with Testing
- Lightweight possible improvements
- 15.15-16.00: Coffee break
- 16.00-17.00: Release Planning
- Change to Java 17
- Update Tycho version 2.5 to 3.0
- Testing Day
- 17.00-18.00: Feedback + Closing Notes
Minutes
Slides: Datei:Palladio Dev Meeting 2022.pdf
- Release Process
- 6.12.22: Compile your projects with Java17
- 13.12.22: Report your problems
- days after that: Testing Day. Create Doodle for that.
- Ticketing System
- have the same process for every team
- Keep 1-month-sprints and see how it turns out with new ticket assignment (better related to research area).
- Create Groups in Jira for the teams. They can create their own dashboards with tickets and assign them
- Project structure in Jira?
- Clean-up Jira: How?
- Next Sprints: Every team tries out what they want, and then they can report on it and we can decide what we want to do.
- decide in a break-out group next spring
- report on it every concall until then
- Quality Assurance
- Problems regarding manual tests:
- Manual tests in Jira contain old projects - old stuff that is not up to data and new stuff does not have tests
- Enrich Palladio-ExampleModels with models used for testing (e.g., for data flow analysis); Teams will think about which models they want to add until next concall (e.g., one example model per analysis).
- Problems regarding Unit tests:
- Integrate Quality Metrics into build process?
- Improvements:
- Framework for loading models?
- Problems regarding manual tests:
- Feedback
- Discuss co-location with SSP next year
- Instead co-locate with research retreat (On the monday)
- Also have concalls "in-presence"? Stuttgart and Karlsruhe in one room, respectively?