Closed jstrachan closed 3 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Provide feedback via https://jenkins-x.io/community.
/close
@jenkins-x-bot: Closing this issue.
right now we are continuously upgrading Jenkins X 2.x and the new 3.x version streams which can move too fast for some folks.
It might be nice to introduce alternative channels of consumption - so an
LTS
kind of channel could be created?Each channel could run at a different cadence such that:
Its easy for folks to upgrade daily/weekly/monthly already using an upgrade schedule; but it might be nice to upgrade more frequently to a more stable channel.
If we had a more stable channel (e.g. monthly) - we could create better documentation on whats changed in that month?