[Pulp-dev] plugin release checklist templates

David Davis daviddavis at redhat.com
Tue Jan 5 15:07:01 UTC 2021

+1 to a global plugin release checklist template.

I imagine that pulpcore will have its own set of templates though? I think
there are some steps (eg release the plugin_template and installer) that
plugins don't do.


On Tue, Dec 15, 2020 at 11:19 AM Tanya Tereshchenko <ttereshc at redhat.com>

> We started using redmine checklists in pulpcore and in some plugins.
> Here [0] is an example of a plugin checklist in use.
> Currently any plugin which has a checklist template has their own
> checklist template.
> It's quite inconvenient to update those if there any changes introduced to
> the release process and with time they divert.
> Any objections to have one plugin release template (one for each release
> type) shared with all the redmine projects?
> One downside is that links and paths specified in the template won't be
> plugin specific but will be mentioned in a more generic way, like:
>    - Create a release https://github.com/pulp/<your_plugin>/releases/new
>    - Regenerate the .github files on the stable branch with
>    plugin_template (./plugin-template --github <your_plugin>)
> Any other suggestion to keep plugin release steps up to date across all
> plugins are welcome.
> Thank you,
> Tanya
> [0] https://pulp.plan.io/issues/7920
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20210105/9544593a/attachment.htm>

More information about the Pulp-dev mailing list