schristoff

We should document a compat or contract with users on what versions of kubernetes we support

Update Mixin Documentation and Skeletor with a "How To"

3

A tutorial that shows the user how to write a mixin would be great. We should leverage existing documentation https://porter.sh/docs/how-to-guides/work-with-mixins/ , https://porter.sh/docs/development/dev-a-mixin/

- [ ] Create AWS bundle example with documentation on the site - [ ] AWS Storage Plugin (leverage https://aws.amazon.com/documentdb/) - [ ] AWS Secret Store (AWS Secrets Manager?)

# Porter Incubation Application v1.5 This template provides the project with a framework to inform the TOC of their conformance to the Incubation Level Criteria. Project Repo(s): [GetPorter/Porter](https://github.com/getporter/porter) Project Site:...

Currently it takes an hour+ to cut a release, and that doesn't include if we are waiting for a PR to merge and go through the merge queue. We should...

Linter for error wrapping

1

In the effort to return better errors we need to make sure that we are wrapping errors properly. One part of it is that we wrap errors properly. This means...

remove `retry.Attempts(0)`

1

We should not put ourselves in an infinite loop. Going forward we can set a sane number of retries so we do not block.

**Purpose:** As part of schema work it has been identified that `src/packager` intertwines "deploy time" and "package create time" logic. This makes it burdensome, or possibly impossible, to implement versioned...

Spinner is inefficient and could have end user impacts. We should remove it and see if there is a better functionality that could be implemented. Relates to #2576