Release a new version to PyPi

[Cinc-th]

Hi Ryan,

I think the current code may be published to PyPi to give people easier access to a working version for Trac 1.4/Trac 1.6.

I reverted the recent version change (see [18204], [18215]) so feel free to pick some reasonable number.

I may tag the current tree (as 0.2.0 I assume?) to help you with that.

---

As a sidenote.

I believe there should be some writeup regarding release management.

comment:5:ticket:13935 is a fine example how confusing my random version number picking was. That should be more consistent (esp. on my side).

[Ryan J Ollos]

In 18216:

FullBlogPlugin: Bump version after release

Version 0.2.0 has been published to PyPI.

Refs #13999.

[Ryan J Ollos]

Published ​pypi:TracFullBlog/0.2.0.

[Ryan J Ollos]

Replying to Cinc-th:

I may tag the current tree (as 0.2.0 I assume?) to help you with that.

Sound good.

As a sidenote.

I believe there should be some writeup regarding release management.

Yeah, there is no consistency. A write-up on DevGuide would be great. One suggestion that got some traction is to use the oldest supported Trac version as the release number, and add an additional number at the end: 1.0.0.1 for the first dot release for a plugin supporting 1.0.0 and later. I need to check that the 4 digit id is allowed per ​pep:0440.

[Cinc-th]

Created #14000 for creating a versioning documentation.