Denis Yuen
> There's variant of users just deleting GitHub releases/tags. If we snapshot the tag after it's created, the tag will be around forever in Dockstore. Which sometimes you might want...
> * Is it worth it to add a trigger? Does not seem like it, we can schedule a 1.16.1 ticket for example to delete the old columns
Could use more views from users, needs back-end changes as well so assigning to 1.14 for now
> Do we snapshot a version before assigning the DOI? I would argue no. I think no too. I think I'm leaning toward @svonworl 's (?) idea to have more...
> Perhaps we can set up some type of AWS queue that has these tags that need to be checked and we can have a scheduled lambda that pulls from...
Hi, I haven't looked at this in a while, but it sounds like resolving the `extends` references would still result in a valid avro schema so that should be fine....
FYI, I was able to compile with this following trivial change to the cwl-avro.yml. ``` $ git diff diff --git a/draft-3/cwl-avro.yml b/draft-3/cwl-avro.yml index b3ae433..c6310e1 100644 --- a/draft-3/cwl-avro.yml +++ b/draft-3/cwl-avro.yml @@...
Hi, Not exactly. We use the workaround noted above which works for generating cwlavro. However, I think there is still value in schema-salad generating a valid avro schema. Not only...
@tetron that sounds reasonable as well
> use a `hotfix-` branch and create a new "patch" tag (e.g., `v0.1.1`) but that still seems excessive. This is what we've normally done, although sometimes we also commit directly...