- docker does not provide a way to define an image as development only
- it requires to follow on day to day the dependencies of the development
- we do not guarantee migration on development version
- what happens during the transition between two series?
On 25/9/18 15:26, Cédric Krier wrote:
> - docker does not provide a way to define an image as development only
I don't see any problem, just tag the image as development and do not mark them with the latest label. It won't be downloaded unless told explicity
> - it requires to follow on day to day the dependencies of the development
Then we can know in advance which dependencies may break the future release, which sound good for me.
> - we do not guarantee migration on development version
That's exactly the same when running from source code or installing the development packages from sources.
> - what happens during the transition between two series?
Not sure to understand which issue you see here. For me there is no issue between the transition, as the image is freezed (like the repository) and it can be used to test the future release.
As I do not want to spend my time on this. I think anyone is free to show that he can manage such development image by publishing it. Once he shows dedication on this tasks, we can consider include it in standard.