# Associating plugin versions with Discourse versions

**URL:** <https://meta.discourse.org/t/associating-plugin-versions-with-discourse-versions/59841>\
**Category:** Development\
**Created:** [Mars 24, 2017, 1:34 UTC](https://meta.discourse.org/t/associating-plugin-versions-with-discourse-versions/59841 "2017-03-24T13:34:00Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [Mars 24, 2017, 6:51 UTC](https://meta.discourse.org/t/associating-plugin-versions-with-discourse-versions/59841/4 "2017-03-24T18:51:28Z")

</div>

Sounds like a good approach to me. To be clear

- a tag is _not_ a branch
- a new tag is not needed for each commit

In other words, a tag is like a “pointer” to particular place in the sequence of commits.  
Any “notes” regarding compatibility can be put into the readme / plugin.rb file prior to tagging.

I notice this one has 0.2.1 and 0.3.0  
[https://github.com/cpradio/discourse-plugin-checklist](https://github.com/cpradio/discourse-plugin-checklist)  
Which suggests the numbers used can be arbitrary. Yes?

---

_[View the full topic](https://meta.discourse.org/t/associating-plugin-versions-with-discourse-versions/59841)._