> By "hard to link", are you basically saying pasting URLs is hard
Both JIRA and GH give nice visual indicators to the state of an issue when
it is linked from another issue. When you manually create links, you lose
that. That's all I was saying.
I like JIRA because everything is in JIRA and I
> then I'll start putting together individual proposals for a few repos to
> exercise the process and get more contributions going
solr-operator is a great example of PMC-maintained code that makes
sense to have in a separate repository. It's written primarily in a
different language, it's an
Let each sub project decide for themselves. PYLUCENE has its own svn repo and
its own Jira space.
Solr-operator should be allowed to continue with GH issues and PRs i.m.o. No
need to force them into JIRA as long as the ASF allows projects to choose.
Jan
> 24. nov. 2020 kl. 20:59 skrev David
>
> > Q: Should we create a separate JIRA for these contribs... or ditch JIRA
> entirely for them, relying on GitHub alone?
>
> I'd start with same JIRA, with a separate component or label. I don't
> think GH issues would be good because it becomes harder to link between
> core and contrib issues
Thank you for the replies so far.
I think that each contrib would necessarily have to have their own release
schedule and release vote. I suspect that there might be frequent releases
at first, and then these will smooth out into basically once per major
release. I also think that contribs having
Thanks for sending this email, Mike and thanks for the follow up, David.
The idea of having multiple repos under the project seems like the
reasonable way to go for our project. This allows us to support more
features/tooling/etc. without having to link them to Solr or Lucene
releases.
An
Thanks for shining a spotlight on this Mike.
I have some questions to consider. I'll call these additional repos,
"external contribs", or just contribs for short here; perhaps our internal
contribs would migrate.
Q: Would each contrib be released at its own cadence unrelated to Solr? I
suppose
Solr Devs,
We've slowly been moving into a multi-repository model, and I wanted to
bring some more attention to it and have a more focused discussion. We've
recently embarked upon the acceptance of solr-operator as a distinct
repo[1] under the care of the Lucene (soon to be Solr) PMC. I expect
