-
Notifications
You must be signed in to change notification settings - Fork 38
dev meeting 20211006
Present at the meeting:
- Sonja Heinze (@pitag-ha)
- Marek Kubica (@Leonidas-from-XIV)
- Guillaume Petiot (@gpetiot)
- Nathan Rebours (@NathanReb)
- Marek works on a quick fix for the broken test
- Marek releases 1.5.1
- Every member of the dune-release team contribute to the 2.0.0 roadmap
Dune-release dev meetings are back! They will be held every two weeks again, starting today.
Marek has been working on bug fixes for 1.5.0 and we're almost ready to release them. The last blocker is a test that randomly fails because of a limitation of the mdx stanza v0.1 in dune. We'll work on a quick fix for this because we don't want to delay the release but the follow up should be a serious refactoring of the integration tests. Guillaume already worked on porting them to dune cram test so we'll likely revive that work.
We're going to start working on 2.0.0 but before doing so we'd like to make sure it's easy to contribute, be it for people in the different teams at Tarides or for external contributors.
From now on, we'll keep a clear Roadmap and maintain milestones for the next releases, breaking down every roadmap item into issues with clear priorities and dependencies. People present on the slack should make sure to get invited to the dune-release dev channel first so we can easily synchronized. External contributors will simply communicate on the issues directly.
We've been discussing plans for 2.0.0 for a while and now is the time to write it all down so we can identify features and changes that are breaking and need to be part of the 2.0.0 release and those that can eventually be delayed.
We'll start collaborating on a document and for our next meeting we'll work out time estimates and priorities and will select the set of features for 2.0.0 so that we can aim at a release Q1 2022.
Once that's been decided we'll create an issue for each 2.0 roadmap item and add them to the 2.0 milestone.
The main focus for that release being that thanks to the removal of delegates we'll be able to fix the default behaviour of dune-release, greatly improving the experience for github users. We'll also work on improving it further by making better use of the github API, eventually completely getting rid of any configuration except for the Github token. Our goal moving forward will remain making using dune-release as seemless as possible for the supported usecases while making sure advanced users can still configure it for their custom needs.