Merge lp:~james-w/libdep-service-python/make-release into lp:libdep-service-python
Proposed by
James Westby
Status: | Merged |
---|---|
Approved by: | Jonathan Lange |
Approved revision: | 12 |
Merged at revision: | 16 |
Proposed branch: | lp:~james-w/libdep-service-python/make-release |
Merge into: | lp:libdep-service-python |
Diff against target: |
26 lines (+19/-0) 1 file modified
Makefile (+19/-0) |
To merge this branch: | bzr merge lp:~james-w/libdep-service-python/make-release |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jonathan Lange (community) | Approve | ||
Review via email: mp+130428@code.launchpad.net |
Commit message
Add some release automation.
Description of the change
Hi,
Here's a stab at automating the second part of the release process.
We might want to automate the first part too, but I think trying to do all
of it in one operation is a mistake because of the multiple moving parts.
I welcome ideas for other approaches, this was just the easiest way I could
see to fold the steps on the wiki page in to a script.
Thanks,
James
To post a comment you must log in.
On 18 October 2012 21:42, James Westby <email address hidden> wrote: ca-hackers) /code.launchpad .net/~james- w/libdep- service- python/ make-release/ +merge/ 130428
> James Westby has proposed merging lp:~james-w/libdep-service-python/make-release into lp:libdep-service-python.
>
> Commit message:
> Add some release automation.
>
> Requested reviews:
> Canonical Consumer Applications Hackers (canonical-
>
> For more details, see:
> https:/
>
> Hi,
>
> Here's a stab at automating the second part of the release process.
>
> We might want to automate the first part too, but I think trying to do all
> of it in one operation is a mistake because of the multiple moving parts.
>
+1
> I welcome ideas for other approaches, this was just the easiest way I could
> see to fold the steps on the wiki page in to a script.
>
I think this is a good approach. I think it might be better to read
the version number out of the NEWS file (or similar), rather than
require it to be specified, since if everything has gone correctly
with the previous step, it has already been specified.
cheers,
jml