flow::Triage label is used on issues that need product/prioritization triage by the Product Manager (Danielle), or engineering/assignment triage by the Engineering Lead (Douwe).
After they've been triaged, they'll have a milestone (other than
Backlog), an assignee, and the
flow::To Do label.
If you come across something that needs fixing:
Create an issue describing the problem.
If it's not obvious, justify how it relates to our persona and how it contributes to MAUI.
If it's more urgent (has a higher impact on MAUI) than other things you've been assigned, assign it to yourself to work on later the same week:
/milestone %<current milestone> /label ~"flow::To Do" /reassign @<yourself> /cc @DouweM
If it's urgent, but you're not sure who should work on it, assign it to Douwe to triage:
/milestone %<current milestone> /label ~"flow::Triage" /reassign @DouweM
If it's not urgent or you're unsure whether it's something we should do at all, assign it to Danielle to triage:
/milestone %“Backlog" or %<next milestone> /label ~"flow::Triage" /reassign @dmor
flow::label. Don't forget to filter by milestone, and/or assignee!
flow::label and each team member.
flow::label and each team member.
Every Monday, we do a minor release (1.x) that is accompanied by a blog post.
Additionally, we do a patch (1.x.y) or minor release every Thursday, to not leave users waiting to see improvements longer than necessary.
Meltano uses semver as its version number scheme.
Ensure you have the latest
master branch locally before continuing.
git fetch origin
Meltano uses tags to create its artifacts. Pushing a new tag to the repository will publish it as docker images and a PyPI package.
Meltano has a number of dependencies for the release toolchain that are required when performing a release. If you haven't already, please navigate to your meltano installation and run the following command to install all development dependencies:
# activate your virtualenv source ./venv/bin/activate # pip3 install all the development dependencies pip3 install .[dev]
Execute the commands below:
# create and checkout the `release-next` branch from `origin/master` git checkout -B release-next origin/master # view changelog (verify changes made match changes logged) changelog view # after the changelog has been validated, tag the release make release # ensure the tag once the tag has been created, check the version we just bumped to: e.g. `0.22.0` => `0.23.0`. git describe --tags --abbrev=0 # push the tag upstream to trigger the release pipeline git push origin $(git describe --tags --abbrev=0) # push the release branch to merge the new version, then create a merge request git push origin release-next
Tip: Releasing a hotfix? You can use
make type=patch release to force a patch release. This is useful when we need to release hotfixes.
masterand use the
delete the source branch when the changes are merged.
For each demo day, we need to ensure that the following process is followed:
Meltano is deployed and available as a DigitalOcean Marketplace 1-Click install.
Tip: The digitalocean_marketplace job is only available on pipelines running off
meltano-<timestamp>on DigitalOcean, which you will find at the bottom of the digitalocean_marketplace job. Take note of this snapshot string as you'll use it in the next step.
Then, head to the DigitalOcean vendor portal at https://marketplace.digitalocean.com/vendorportal to edit the Meltano listing.
Tip: Don't see the Meltano listing? You'll have to be granted access to the DigitalOcean vendor portal. Please ask your manager for access.
Both https://www.meltano.com and https://meltano.meltanodata.com are automatically monitored using Pingdom, with notifications of downtime posted to:
hello@email address, and
*.meltanodata.com instances are not currently monitored.
When any instance managed by us is reported to be down, through Pingdom or any other means, resolving this becomes the team's top priority.