Open praveenrewar opened 1 year ago
Creation of the vanity URLs for this task is done in the PR #695
Created PR in ytt https://github.com/carvel-dev/ytt/pull/878
Created PR on imgpkg https://github.com/carvel-dev/imgpkg/pull/597
This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.
Context
vmware-tanzu
org to thecarvel-dev
org.As a Developer using one or more Carvel tools as a module dependency I want to know about the module rename ahead of time And be clear about what I need to do to accommodate it So that smoothly continue to enjoy using these tools instead of wasting time (and frustration) associated with discovering the source of a problem I didn't expect.
Acceptance Criteria
📘 Documentation
When I review the developer notes (e.g.
docs/dev.md
) for ${tool} Then I see a note about the module rename. And I'm more like to understand what changed.__
📣 Advanced Notice
Given I'm on a team known to use ${tool} as a module dependency When The module rename occurs Then I am aware of it, shortly after it occurs And I'm clear what I need to do to proactively accommodate the rename.
__
🌟 New Dependency
Given I am not yet using a Carvel tool as a module When I name it as a new dependency in my project and use it
Then I successfully get that dependency (i.e. I see it in my
go.mod
) And I can import packages from that module__
🏚 → 🏠 Migrating/Upgrading
Given I am already using a Carvel tool as a module When I follow the instructions "upgrade" to the next version (which contains the module rename) Then I successfully get the new dependency (i.e. I see it updated in my
go.mod
) And I can continue to import packages from that module in my own codeResources