Initial release 🎉

[diazona]

I'm making this as a convenient place for any miscellaneous discussions that come up during the process of creating an initial release. It may wind up being totally unnecessary, but if we do need to coordinate or discuss anything about the procedure we can do it here. FYI @sjlongland

[diazona]

I'm thinking we can actually make an alpha test release without the changelog being ready. It'll be just a test run of the real initial release which will come out once we've got the changelog finalized, so the alpha release won't cause us to close the milestone. If you don't mind @sjlongland how about I do that today? Then if any problems show up in the release procedure we can fix them before publishing the real initial release.

[diazona]

actually I had not noticed you already pushed the changelog updates to #93 before I posted this... my bad, I think I somehow missed a chunk of notifications.

Anyway I'll go ahead and make that alpha release to see if anything breaks, but let's wait to make a full release for a day or two just so we have a chance to do quick sanity checks.

[sjlongland]

No biggie, the changes to the CHANGELOG.rst should not make any difference to the code base. Looks like we've got some fun and games to troubleshoot regarding pushing to pypi anyway.

I've given it a poke with debugging enabled.

[diazona]

Time to make the final release? Or should we do another trial run? (v0.1a1 perhaps... though it occurs to me that these are more properly "release candidates" so I guess we should have used v0.1rc0 and `, but it's not a big deal)

[diazona]

Ah, darn, I forgot about that: it looks like you only have collaborator access to the repo, whereas we have a tag protection rule that requires maintainer access or some kind of special permission to create tags. I'll try to figure out how to make you a maintainer, but I seem to remember trying to do that before and it being difficult, so for now I'll just delete the tag protection rule. That will allow any collaborator to create tags (and releases), but it's fine as long as it's just the two of us who are collaborators.

Give it another try now that the protection rule is deleted.

[diazona]

After a quick documentation search, it looks like I actually can't add maintainers to a personal project.

I do actually have an organization which I never really meant to use for much, but I could transfer the repo to that and that would give us more flexibility to hand out permissions. What do you think? (I believe this can wait until after the release - we'll need to update some URLs and stuff to account for the switch but it shouldn't be too much of a problem otherwise.)

[sjlongland]

Yep, well that could be an option, we transfer it to an organisation… whether it be the one you mentioned, or whether we create a dedicated one for the project.

But, first… let's see if we can get v0.1.0 out the door. :-)

[sjlongland]

Ahh, this looks a lot better…

[diazona]

Hooray!

[diazona]

Now that the release is out, shall we share the news on Mastodon? It seems fitting to start there since that's where the idea for this project hatched 😄

At some point I think it'd make sense to email the python-announce list as well, but I was thinking we could get some early feedback from a smaller audience first and address any glaring issues.

[sjlongland]

I think so, get a wider audience out there.

[diazona]

You know what, maybe I'll wait until tomorrow my time to post on Mastodon because North American users will be more active then. But you can post something now to catch the Aus/NZ/East Asian crowd, or later, or whatever you like (there's no real need for us to coordinate).