You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@chorrell my thought is that the LTS tag would point to the latest LTS release. For overlapping LTS releases, the LTS tag would point to the release with the highest major version.
Another option may be to tag the different LTS versions with their code word. Similar to how the Debian Docker Image gets tagged :wheezy etc. The reason why I think this is a good idea is that people who want to be on an LTS version want to be on a specific LTS version until they are ready to jump to the next. Just tagging :lts will not be as beneficial as this will automatically become the next LTS version once a new one gets released. Also, there are some overlap between LTS versions.
Would also get you the latest 4.2.* lts release. I like that because it's more controlled. I agree with @Starefossen someone who wants and LTS image more often than not care about a specific major/minor version.
The code word is a pretty cool idea! I'm +1, and interested in what the @nodejs/lts team thinks of this.
So at any one time we could be maintaining at most 5 images? One LTS release (4.2.*), two stable releases (v5 and v6), and .12? If I'm looking at the right chart, that would be in April of 2016.
Then .10 and .12 sunset and we will be maintaining 3 images from then on: Two LTS releases, and one stable.
@wblankenship ... yep, you're correct. Up until the point where v0.10 and v.12 fall off, we'll have up to five releases being maintained. v0.10, v0.12 and v4.2.x are all LTS lines. v5.x will cut this week hopefully, and then master of course. v0.10 will fall off October 2016 and v0.12 will fall off December 2016. After that things become a bit more sane and regular.
Activity
Starefossen commentedon Oct 13, 2015
I'm +1 for this.
chorrell commentedon Oct 13, 2015
How would this work? Would LTS just point to whatever the latest LTS release is?
retrohacker commentedon Oct 14, 2015
@chorrell my thought is that the
LTStag would point to the latest LTS release. For overlapping LTS releases, theLTStag would point to the release with the highest major version.Starefossen commentedon Oct 14, 2015
Another option may be to tag the different LTS versions with their code word. Similar to how the Debian Docker Image gets tagged
:wheezyetc. The reason why I think this is a good idea is that people who want to be on an LTS version want to be on a specific LTS version until they are ready to jump to the next. Just tagging:ltswill not be as beneficial as this will automatically become the next LTS version once a new one gets released. Also, there are some overlap between LTS versions.chorrell commentedon Oct 14, 2015
I'm +1 on using the LTS code word. So:
Would also get you the latest 4.2.* lts release. I like that because it's more controlled. I agree with @Starefossen someone who wants and LTS image more often than not care about a specific major/minor version.
retrohacker commentedon Oct 14, 2015
The code word is a pretty cool idea! I'm +1, and interested in what the @nodejs/lts team thinks of this.
So at any one time we could be maintaining at most 5 images? One LTS release (4.2.*), two stable releases (v5 and v6), and .12? If I'm looking at the right chart, that would be in April of 2016.
Then .10 and .12 sunset and we will be maintaining 3 images from then on: Two LTS releases, and one stable.
jasnell commentedon Oct 14, 2015
@wblankenship ... yep, you're correct. Up until the point where v0.10 and v.12 fall off, we'll have up to five releases being maintained. v0.10, v0.12 and v4.2.x are all LTS lines. v5.x will cut this week hopefully, and then master of course. v0.10 will fall off October 2016 and v0.12 will fall off December 2016. After that things become a bit more sane and regular.
hmalphettes commentedon Oct 30, 2015
I am +1 for argon and lts.
Here is how it looks like: hmalphettes@9f3ae6a
Let me know if I missed something.
Add node-v5.0.0 - Tag node-v4.2.1 as `lts` and `argon`
hmalphettes commentedon Oct 30, 2015
Here is what the PR to docker's official images would look like:
hmalphettes/official-images@48e76fe
I granted all of you collaborators rights on my repo if that makes it easier to tweak something.
Let me know if we are happy with this and ready to turn this into a PR.
hmalphettes commentedon Oct 30, 2015
Sorry having re-read all this: i understand we agreed to not have the tag
lts.So only tagging v4 with
argonthen:hmalphettes/official-images@5bfa1e5
Add node-v5.0.0 - Tag node-v4.2.1 as `argon`
retrohacker commentedon Oct 30, 2015
Looks good @hmalphettes! I think we can ship this.
Starefossen commentedon Oct 30, 2015
PR is up at docker-library/official-images#1151
hmalphettes commentedon Oct 31, 2015
Thanks everyone!