Closed osis closed 5 years ago
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
Also part of #16
The Notifications service looks like it's been depending on the Notifications Release for keeping track of releases that have gone through CI. I would like to propose that we move to a semver model for Notifications in order to keep track of the impact of ongoing changes.
I think something this example would be beneficial in order to make sure a user is making a conscious and intentional choice about the next semver version based on the changes in the pipeline.
The only problem I see is that there is a release for 1.0 from 2014 already in the repo and I'm unsure about the changes that have happened since then. I don't want to alarm anymore in the community by starting fresh at 2.0, so maybe 1.1 is a good middle ground.