Skip to content
This repository has been archived by the owner on Jul 24, 2018. It is now read-only.

feat: Strategy for coping with large numbers of tiller releases #147

Open
gardlt opened this issue Aug 7, 2017 · 1 comment
Open

feat: Strategy for coping with large numbers of tiller releases #147

gardlt opened this issue Aug 7, 2017 · 1 comment
Labels
enhancement
Milestone
Nice to have

Comments

@gardlt
Copy link
Contributor

gardlt commented Aug 7, 2017

Is this a bug report or feature request? (choose one): feat

Python Version (output of python --version): 2.7

Expected Behavior:
In cases of multiple tiller releases, we want to be able to handle the scenario in case we reach the maximum number of releases.
@gardlt gardlt added this to the 0.9.0 milestone Aug 7, 2017
@gardlt
Copy link
Contributor Author

gardlt commented Nov 2, 2017

This one can be moved to a nice to have since it seems that there is no real limit on the releases.

@gardlt gardlt modified the milestones: 0.9.0, Nice to have Nov 2, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
Nice to have
Development

No branches or pull requests
1 participant
@gardlt