When to release a new version?

Question

When to release a new version?

Closed this issue 13 years ago · 6 comments

At some point it is probably worth tagging a new release and putting up a new download file.

Answer 1 · 2012-02-21T21:38:03.000Z

Good idea - I'll bump the version # and upload the latest code tomorrow.

Answer 2 · 2012-02-21T21:51:44.000Z

It might be worth fixing the -creators method first, just to avoid putting crud into the initial Spotlight index. (Fixable afterwards, but...)

I'd suggest tagging the repo using "git tag commit-hash" for each release, and then pushing that tag to github using something like "git push --tags origin ". It makes it easier to work out what went into a release later on :-)

Answer 3 · 2012-02-22T15:49:44.000Z

I've put v1.4 of the qlgenerator in the download section (code as 030ecd7). The tags I've entered via git tag don't seem to be making their way to github (syncing with the GitHub.app) though, not sure what I'm missing…

Answer 4 · 2012-02-22T15:59:59.000Z

Cool! WRT the tags you might have to use git from the command line. A normal "git push" doesn't push tags, and that might be what GitHub.app is doing.

Answer 5 · 2012-02-22T16:10:58.000Z

Aha - a git push —tags did the job - wish I'd noticed this before overwriting all my local tags a while ago though.

Answer 6 · 2012-02-22T16:43:16.000Z

Excellent. Might be worth asking for GitHub.app to do the right thing :-)