Proceedings of the 2018 ESPResSo meetings

2018-09-11

Git and Bug Fix Organisation

• We need a way to track bug fix PRs and where they should go
• Maybe consider git flow https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow

:arrow_right: Use github tags to track PRs :arrow_right: Look into enforcing tagging

Documentation of the CI

• We have custom CI infrastructure
• Its critical and needs to be documented
• Should be kept under version control and if possible do reviews/4 eyes

:arrow_right: Jean-Noël is looking into this

Log and for the Espresso meetings

• We may consider making a short results log and publish it somewhere for people who can not be present
• Maybe have an low-tech agenda somewhere that people can add items to be discussed at the next meeting.

:arrow_right: Inform Rudolf

MegaMOL visusalization

• Visus people said they are working on something
• Ready for paper?
• Ready for 4.0.1

:arrow_right: Contact Tobias Rau/Visus

Release paper

:arrow_right: Discussed elsewhere

Release debriefing

• Final steps were too chaotic

  • We need a checklist/process description for the future
  • Key parts were not tested (installation, version number, building from tarball, ...)

  :arrow_right: Open Issues

• We need a quick bug fix release (aim for Nov)

:arrow_right: Fix date and what should go in

• Over all took too long. Maybe consider a fixed roadmap with hard freezes. Only delay on show stopper.

:arrow_right: Make release candidate to identify issues before the release.

Release process

:arrow_right: Make checklist, see #2269.