Create a release

[benjifisher]

Although I can push to this repo, I do not seem to have permission to create releases. (I do not see a settings option in the sidebar.)

I do not have any immediate plans for this project, so I think this is a good time to declare v1.0.

[chase]

I'll look into how I can get you permission but in the meantime I'll put out the release.

[chase]

Do you want to merge #27 first?

[benjifisher]

I do not think we want to merge #27. We closed that with good reason, right? Looking at it again, I see that I owe you answers to some questions, so I just posted another comment there.

[chase]

Oops, I meant to type #28. Writing issue replies on a phone during a long bus ride can be dangerous.

[chase]

Thanks for your answers, though!

[benjifisher]

Oh, #28. It is a big enough change that I would like someone else to test before merging it. If you or someone else gives it a positive review, then I will merge it. Of course, you can review and merge if you like.

If no one is interested in reviewing #28, then I would still like to make a release.

[chase]

Regarding creating a release, did you go through this step by step guide?https://help.github.com/articles/creating-releases/

As a collaborator, you should have the ability to create releases, at least according to: https://help.github.com/articles/permission-levels-for-a-user-account-repository/

[benjifisher]

Yes, that seems to work. Funny, whatever page I was reading said to start with the Settings link in the sidebar, not the Releases link at the top of the page. Or maybe I was just dreaming it.

OK, I can handle the release myself. But now it is time for bed.

[chase]

Dreaming of pushing a release? That's dedication, my friend!

[chase]

I updated some of the meta data for the upcoming release with #30.

[benjifisher]

Thanks for the metadata updates. I merged #30 and released v1.0. Just in time for the holidays!