Issue #147 open

versioning / releasing / tagging inconsistencies, missing/forgotten things

Thomas Waldmann avatarThomas Waldmann created an issue

just pulled whoosh from pypi via pip. whoosh.__version__ says it is 1.8.4.

Looked at docs, no release notes about 1.8.4. There, it looks like 1.8.3 is latest release.

Looked at repo, no release 1.8.4 tagged. In fact, no tags for any recent release, since 1.2. After some searching, one finds a commit comment talking about 1.8.4 (but that is a rather fuzzy element, far better is to use tags for that. tags are also easier to adjust in case you forgot something).

Bitbucket download page, offers whoosh 1.2 (and "tip") - which seems to correspond to the tags you have made.

OK, so what I suggest is that you have a wiki page (for example), with "how to release" and just follow that step by step for any release you make.

Just have a look there, that's mine for moin:

Comments (6)

  1. Thomas Waldmann

    can we please work on solving/closing this issue?

    i just discovered that there is 2.5.1 on pypi (great!), but:

    • no changelog for 2.5.1
    • not even a tag in the repo for 2.5.1

    I think a documentation / checklist would really help so that such things won't be forgotten accidentally (I also read my own checklist when doing a release).

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.