Repository navigation
Alpine Transition - Plan Proposal #406
Description
Activity
Is it necessary to make a separate branch? That would complicate keeping it up to date with master until it has been merged. I mean; concider this:
We branch to
alpine-3.5 branch, we submit the PR to Docker to create thev6-alpine3.5tag, some days later a new version of Node is released, we update master submit PR to Docker and then we have to go through the same process for tov6-alpine3.5.While I agree that using git branches for this can of this is the correct approach, I am afraid that the current process of getting tags updated on Docker Hub makes this impractical.
I very much support a strategy to managing and maintaining Alpine Linux versions in an organised fashion!
@Starefossen the automated build can do all of this for us though. All we would need is manage the list of automated build. We can merge everything from master to the alpine-3.5 branch too.
I did not consider automated builds. Under what image name would you set up an automated build?
Well for this plan to work I was hoping that we have access to automated builds for the node project on Docker Hub.
Here is what I propose to handle the updating of alpine.
Any feedback on this?