1.10 release: plans

[David Cheney]

Please don't consider me crucial to the process.

* The build recipe is discoverable from juju-core build page
* The version number is controled by version/version.go
* The scripts to upload tools to s3 are in scripts/release-public-tools,
the script should be invoked three times, once for each build artifact
of a series.

On 18/04/13 20:06, William Reade wrote:
> Hi all
> 
> Our current plan is as follows:
> 
>   * merge 3 minor changes related to status/logging/output
>   * set the current version number to 1.10
>   * stop changing trunk
>   * notify martin and daviey that 1.10 is ready, and ask nicely
>     that it be packaged
>   * wait for confirmation that it's packaged
>   * worry about replicating the built jujud to the juju-dist bucket
> 
> The thinking is that the release is time-critical, and the contents of
> the bucket can afford to wait 12 hours or so until davecheney is
> available to ensure we do the right thing with them.
> 
> Does anyone forsee any problems with this?
> 
> Cheers
> William
>