Certbot 1.10.0 Release Imminent?

I saw this today...

2 Likes

That's actually normal. The dev0 suffix indicates it's the current development version for the upcoming release, in this case 1.10.0. It's the current internal version used in the current Github master version code.

By the way, shouldn't master be renamed to main anyway?

3 Likes

Wonder why they would put a development version and suffix on the official release documentation? Really confusing to users looking for the current documentation.

Probably. So... many... branches... :crazy_face:

1 Like

As far as I know, the official documentation is that of the development version. I think any commit to the documentation tree will be published within a reasonable time but not just until there's a new release.

One might argue this isn't the correct way to publish the documentation: it might contain features not included in the latest stable release.

Personally I think there needs to be separate documentation for all releases. Not unlike the different versions on for example https://docs.python.org or https://www.openssl.org/docs/ Not everybody runs the latest release. Also, some people might run the latest development version, so that should be included too :wink:

There actually is some kind of version pull down menu, but it only contains downloadable files for the current version.

2 Likes

Amen.

In the words of Juergen:
That's... not helpful. Fix that.

There's actually an open issue for this @griffin: https://github.com/certbot/certbot/issues/6554

1 Like

Perhaps I should add to / update / supersede it. My GitHub account is LetsEncryptCommunity in case anyone ever wants to post there accordingly.