[Biojava-dev] release process

[Peter Cock]

For what its worth, we've documented the Biopython process here:

http://biopython.org/wiki/Building_a_release

I confess I've done this often enough that I tend to do things out of
order (Linux and Windows checks in parallel on different machines
etc), but we have rotated the release process round between us so
that multiple people have successfully followed the recipe to do a
release - and in the process clarified the instructions.

I would like to have automated more of this, but it has worked quite well.

Regards,

Peter

On Fri, Apr 1, 2016 at 4:30 PM, Michael Heuer <heuermh at gmail.com> wrote:
> As far as I know we've never had a formal release process, given that
> cutting a release was so complicated very few people were willing to go
> through it and as such releases didn't happen very often.
>
> A few version 5 alpha releases were pushed to Maven Central without much
> public discussion.  That's not too big of a deal, but perhaps we should
> codify a release process in a document before things get carried away.  It
> might address
>
>  - when to cut a release
>  - how to test for binary compliance
>  - confirm we're following semantic versioning correctly
>  - branching policy
>  - voting on release candidates
>  - code signing keys/web of trust
>  - hosting javadoc, cookbook docs
>  - wiki updates
>
>    michael
>
> _______________________________________________
> biojava-dev mailing list
> biojava-dev at mailman.open-bio.org
> http://mailman.open-bio.org/mailman/listinfo/biojava-dev