This was discussed during the maintainers meeting:
As we have milestones for the versions, implementers and developers expect to see the PRs related to that milestone. Currently we're doing it manually (as in when merging a PR we add it to the milestone), but we're not consistent and not doing this 100% of the times.
We should automate this, by adding a parameter to ChangeLogGenerator, so when it's running trough the script exe/decidim-changelog-generator then the PR isn't added to the GH milestone, but when it is run through the decidim-releaser process, then it is added.
The reasoning is that:
- when it is run through
exe/decidim-changelog-generator, it is done before a release (i.e. when @decidim/product is working on checking out what will enter in a future release).
- when it is run through
decidim-releaser, it is done during a release
This was discussed during the maintainers meeting:
As we have milestones for the versions, implementers and developers expect to see the PRs related to that milestone. Currently we're doing it manually (as in when merging a PR we add it to the milestone), but we're not consistent and not doing this 100% of the times.
We should automate this, by adding a parameter to
ChangeLogGenerator, so when it's running trough the scriptexe/decidim-changelog-generatorthen the PR isn't added to the GH milestone, but when it is run through the decidim-releaser process, then it is added.The reasoning is that:
exe/decidim-changelog-generator, it is done before a release (i.e. when @decidim/product is working on checking out what will enter in a future release).decidim-releaser, it is done during a release