Missing release tags

[Tohnmeister]

Not really an issue with Moq functionality, but more with this repository. In my company we're using the latest stable release of Moq. One of the things we're doing to guarantee contingency, is to have source code of third party binaries also in our versioning system. With that in mind I was looking for the source code belonging to the latest stable release of Moq (4.2.1510.2205). But the releases tab on this project's Github page only shows one old release and tag.

Is there a way to get the source code of a specific release?

[stakx]

See also #320.

[stakx]

@Tohnmeister: I've added release tags for all published NuGet packages all the way back to version 4.5.0. For those, you can now download the source code via the releases page.

Release tags for the older 4.1.x and 4.2.x versions are a difficult matter. It appears that these version numbers are date-based: 4.x.yymm.ddnn, where yy = year, mm = month, dd = day (can also be a single digit, since leading zeroes are dropped), and nn = some two-digit number. My guess is that this date denotes the day on which the NuGet package was built, and nn is the build number on that day. Sometimes, the dates correlate to a commit date (but not always). Sometimes, it's possible to isolate one specific commit for such a version, and yet the version numbers in the published binaries differ from those in the source code.

I have tagged a very few of those where I was reasonably sure of a good-enough match, but it is a lot of puzzle work. I've come to the conclusion that it might be better to not create tags for these old versions, because it is very easy to get them wrong.

From my point of view, all that can be done in a reasonable amount of time has been done, so I am closing this issue for now. If anyone has a great idea how to proceed with tagging the old versions, we can reopen.

[stakx]

I figured out a way to add the missing release tags for versions <4.5.0. Using tools such as JustAssembly, ILSpy, git log -S (pickaxe) and gitk I can identify differences between versions and track down the commits responsible for them. It's quite a bit of work, but I'm close to getting this done completely.

Tags will be greatly helpful in creating more precise release notes (see #320) and those in turn will aid in tracking down regressions.

[stakx]

@Tohnmeister: All release tags for Moq v4 are now added to the repository.

[Tohnmeister]

Awesome! Exactly what we needed. Thanks.