docker in 14.04

[Nathan McCauley]

Thanks James for putting this proposal forward.

This proposal makes a lot of sense, especially due to the rapid rate
of feature development on Docker. We're happy to support this proposal
and would like to work with the package maintainer of Ubuntu to make
this happen.

Thanks,
Nathan

On Thu, Apr 9, 2015 at 4:57 AM, James Page <james.page at ubuntu.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi All
>
> After review and some further discussion within the team, with some
> members of the Technical Board and with docker upstream it would
> appear there are two options for Docker updates.
>
> 1) Drop docker from the Ubuntu archives and tell people to use
> upstream packages.
>
> 2) Keep docker up-to-date in the archive, with some rigour around
> upgrade and regression testing.
>
> Ubuntu is by far-and-away the most popular docker container base and
> operating system for running docker on; I think we need to recognise
> this as a community and embrace the docker ecosystem as part of the
> Ubuntu distribution.
>
> The majority of docker users want the latest 'stable' release, they
> are used to working this way (for now - see last part of policy
> proposed below) and at this point in time, we should be supporting
> this, not hindering it, without wasting multiple man-years of effort
> trying to back port invasive security fixes and bug fixes to something
> that people are realistically not going to use that much.
>
> So I'm proposing the following stable update policy for docker in Ubuntu
> :
>
> 1) The package maintainer of docker will work in-conjunction with
> docker upstream to identify at any given point in time what the best
> stable release is for Ubuntu.  This allows us to deal with the 'new'
> releases of docker alongside the previous 'stable' release and switch
> things at the right time.
>
> 2) This release of docker will be packaged for the development release
> and as a back port for all released versions of Ubuntu still under
> support back to 14.04.
>
> 3) As part of the SRU testing process, we'll perform automated upgrade
> testing of docker to ensure that a cross section of popular
> application containers work both before and post upgrade, as part of
> the upgrade AND being rebuilt pre and post upgrade.
>
> We should operate this policy until 16.04 release, at which point we
> need to review whether its still appropriate or whether docker
> development velocity is now shelving off, and we can seriously
> consider a true stable docker maintenance approach for 16.04.
>
> I've CC'ed Eric and Nathan from docker upstream so they can both
> comment on this proposal as well.
>
> I hope that this approach can be endorsed by the Technical Board and I
> look forward to your responses!
>
> Regards
>
> James
> - --
> James Page
> Ubuntu and Debian Developer
> james.page at ubuntu.com
> jamespage at debian.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJVJmkTAAoJEL/srsug59jD9FAP/iyS6Rd87wbNw87H6aZjUsn+
> /fNcpnqb2A4H4COxeExQtaAKBssSMldBIOkkvnz1qP0yf8YJG+DJYqpR9e+XCQFT
> +ypGeRiAUVhmm6Ry62UPVlJdxrKIjJsqX1I/oVWl3aDQ7C7zNbf5CpDKGprhVokA
> c6eqOfqNpXgWDhfrP/93CiYP9IALl3O8ALYAAwrLR2s7Hqi9T5Sc3Hbcwug74pSE
> vNEi9HVwIyH68y5SRkypdlYlEED4y+Geh7x3mHd2DhrOXa+HluLk1/Ls6HZn5x9C
> UkkDtDK2rBmADa/D5NrA7l3VljcbWsfAT6n5iOFo/RSB6npK/rjR3KSzAiuZSeR1
> cWIabPddBDmKmnra6pwTyAe0Jc1UKDzCiGupo+R3vTxtUPuf7eyzo8SDAYGHKW1M
> U931z0q6uy+LZ7V0UQDTszqwldRsFPB0QepQ5asQ994snLIFpZUVhOggp8DuXymr
> xlN1kpvVWMFFh9NNaFQdqaOSQ9r6rk+4zKkI8E3e7t/iD9mDLzi/wqeNi92Xceqf
> fG6vTlXROgUQFG6cBBJl8baGCy9eSWcB1JQ90hpHorPLLwlGDdBwpwa3xZ2KRU24
> VDjYZBZ0iIxgC2By1505KyGKps3+dsDQS9McitERcj7AsZ3PIPxuGrODgV715zSp
> Yh1p9bnrlbX5r0BN6/Kh
> =Nt9p
> -----END PGP SIGNATURE-----