2.7 tag should point to 2.7.3 about dockerfiles

[svenevs]

That's true, but not how the pandoc versions work. First is 2.7, then 2.7.1, ..., 2.7.3.

You can use the latest tag right now, but the next pandoc release is 2.8.

Unfortunately, I don't see a good way to support what you want given how the pandoc versioning scheme works.

[scolytus]

So the problem is the missing 2.7.0 tag because pandoc doesn't use the full A.B.C scheme? Then 2.7 would specify the latest MAJOR release and 2.7.0 the actual pandoc release 2.7

OK, then I'll just have to specify a particular version.

[svenevs]

Yes, currently we're mirroring the official tags on the pandoc repo. To adopt what you're suggesting would mean breaking anybody who is currently relying on 2.7 tag being "2.7.0".

• Is it ok to break them? Does it matter?
• We could create like a X.Y-latest tag (not as pretty, but would suit your needs without breaking anybody)?

I'm curious, what benefit do you get / use case do you have for wanting this tag? Genuine question...I help maintain this repo because it's really the only way I can contribute meaningfully to pandoc, I don't actually know it well enough to develop it or develop applications that link against it. I don't know Haskell...

I'm asking because if we add this tag, it might be nice to document why it exists / why a user should consider using it over pinning an exact version.

[scolytus]

The benefit is (and why people are using it) that you can get non-breaking updates without need to maintain/adapt it in their scripts/configs. In this case it's not that critical, but if you have some server application permanently running in docker this would be a way to get for example security fixes in an automated manner.

It's an additional convenience feature. And it's a trade-off. If you really rely on an image/application to work you will always specify an exact version, monitor upstream releases and meticulously test any upgrade before putting it to production. If you don't have the time or accept the risk of breaking something you could just say: "give me the latest 2.7.Whatever".

Release 2.7 is the Major and whatever the current Minor release is, just give it to me. But if 2.8 is released I don't want to have it because something must have changed that bumped the Major. If I accept that risk I would use latest anyway.

In my special case: I always write scripts that automate my tasks. And usually I put a docker pull step in there somewhere, which automatically updates the images to the latest version for the tag. Also in general I really try to avoid using the latest tag.

So I totally understand if this would be too much effort, I just initially missed the fact that pandoc does not stick to the A.B.C and there simply is no 2.7.0.

Thanks for your work anyway, the pandoc image is very useful to me.

[tarleb]

Rolling release tags have been implemented.