MeltanoLabs / MeltanoLabs/Singer-Working-Group
Standardization of `ACTIVATE_VERSION` message
Open
@dmosorast is already working on this.
Since Feb 22, 2022.
Applies To::Taps
Applies To::Targets
Issue Type::Proposal
Proposal Type::New Capability
- Dominant language
- No language data
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
This is something that's been frequently buzzing about the community. The "activate version" message has been used by taps in the past to track the "version" of some data. The semantics of this message haven't been formalized, so I'd like to track that conversation here, and provide my historical knowledge on the subject.
I don't have a clear picture pulled together just yet, but just getting this topic pinned for now.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.