Re: Issue tracking

Hi, Justin. I do know what you mean, the previous project that spawned these libraries really wasn't able to take advantage of clear versioned JIRA releases in general, so it was less of a concern there. I'm happy to track issues in the repository's GitHub issues and talk about it if the other si

Re: Issue tracking

Hi Tony, Thanks for the feedback. Personally I find that it can be confusing, at least in the context of Infusion, because we have JIRA components related to Infusion components that are included in an Infusion release and others that aren’t (e.g. website). That makes using JIRA’s versioning se

Re: Issue tracking

Hi, Justin. When working on the GPII JIRA instance I simply set up a component for each repository and tracked things in the main GPII project. We might do something similar, handle them as components within the FLUID project on issues.fluidproject.org. Particularly for the plugins used in linti

Re: Issue tracking

I’ve added the recently migrated repos to the Google Sheet . I assume that at least some of these were being tracked in the GPII Jira instance. It