Hi,
I would like to create a new release of Axiom, because trunk has some
cool
features that the current release on PyPI does not.
However, the current release process doesn't really work anymore. As
exarkun warned:
11:55 < exarkun> keep in mind that the last release was almost 4 years
ago,
and the release procedure was written for a time when Divmod was still
an
actual company with actual infrastructure available
11:55 < exarkun> so it may not actually be possible to follow the
procedure
anymore
The current release procedure refers to:
- a buildbot that is no longer operational
- a version control system that is no longer used (SVN)
- a project management tool that is no longer used (Trac)
In addition, it appears to suggest setup.py register as a way to upload
the
new release, which isn't what that command does AFAIK.
I would like to amend (by which I mean obliterate and replace) the
current
release procedure for Divmod projects.
Here are the differences:
- Exporting and uploading the tarball is gone. Just use PyPI.
- The bogus PyPI publishing command has been replaced with the right
thing.
- The upload is now signed. I'm willing to use my own GPG key, or
create a
specific Divmod signing key, if that'd make you happier :)
- All SVN commands have been replaced with their bzr equivalent.
- "Enbloggen it" is gone.
- "Freshmeat release" is gone.
- Run unit tests locally is gone.
- We currently don't have any kind of continuous integration. I'd
happily
donate machine time, but I don't really feel like adopting all of Axiom
and
maintaining a buildbot, so I would suggest one of two options:
1. travis
2. all three of us just run the tests already ;)
Jokes aside, I wrote my suggested amended procedure based on the idea
that
we use Travis.
Without further ado, here is my suggested amended release procedure:
https://gist.github.com/lvh/5999588
If we can all agree on this procedure, I will:
- Make it work with Travis, if possible and required
- Create a signing key, if requested
- Create a release for Axiom
To do this, I need:
1. Consensus and possibly feedback ("+1 do it" counts)
2. PyPI access for the Axiom project.
cheers
Laurens Van Houtven <_@xxxxxx>
6:40 PM (4 minutes ago)
to divmod-users
Hi,
(My apologies if you're receiving this again; it is my understanding
that
the original mail never made it to this list.)
I would like to create a new release of Axiom, because trunk has some
cool
features that the current release on PyPI does not.
However, the current release process doesn't really work anymore. As
exarkun warned:
11:55 < exarkun> keep in mind that the last release was almost 4 years
ago,
and the release procedure was written for a time when Divmod was still
an
actual company with actual infrastructure available
11:55 < exarkun> so it may not actually be possible to follow the
procedure
anymore
The current release procedure refers to:
- a buildbot that is no longer operational
- a version control system that is no longer used (SVN)
- a project management tool that is no longer used (Trac)
In addition, it appears to suggest setup.py register as a way to upload
the
new release, which isn't what that command does AFAIK.
I would like to amend (by which I mean obliterate and replace) the
current
release procedure for Divmod projects.
Here are the differences:
- Exporting and uploading the tarball is gone. Just use PyPI.
- The bogus PyPI publishing command has been replaced with the right
thing.
- The upload is now signed. I'm willing to use my own GPG key, or
create a
specific Divmod signing key, if that'd make you happier :)
- All SVN commands have been replaced with their bzr equivalent.
- "Enbloggen it" is gone.
- "Freshmeat release" is gone.
- Run unit tests locally is gone.
- We currently don't have any kind of continuous integration. I'd
happily
donate machine time, but I don't really feel like adopting all of Axiom
and
maintaining a buildbot, so I would suggest one of two options:
1. travis
2. all three of us just run the tests already ;)
Jokes aside, I wrote my suggested amended procedure based on the idea
that
we use Travis.
Without further ado, here is my suggested amended release procedure:
https://gist.github.com/lvh/5999588
If we can all agree on this procedure, I will:
- Make it work with Travis, if possible and required
- Create a signing key, if requested
- Create a release for Axiom
To do this, I need:
1. Consensus and possibly feedback ("+1 do it" counts)
2. PyPI access for the Axiom project.
cheers
lvh
