> I see you already have a start at the migration plan, yay!  (The comment on 
> LUCENE-10557)
> Could we maybe pull that out into a wiki page so we can more easily 
> collaborate on the steps?

There would not be so many topics that are controversial except for
the current discussion about existing Jira issues, and I think we are
close to reaching a conclusion.
I re-summarized the migration steps and tasks to be done in the issue
description and I will update it when there is progress. (Most of the
remaining work is an administrative job.)

Tomoko

2022年6月16日(木) 17:13 Dawid Weiss <dawid.we...@gmail.com>:
>
>
> Hi Tomoko,
>
>>
>> * All new issues should be opened on GitHub. Opening new Jira issues
>> is discouraged unless there is a good reason.
>
>
> I'm fine with this. New issues from contributors who are not aware of the 
> migration can be immediately
> cloned to github and closed in Jira as well (vide Adrien's previous 
> suggestion to make an explicit template in
> Jira to point people in the right direction). The "discouragement" would then 
> probably apply only to those folks who
> expressed their negative sentiments against github (and don't have an account 
> there, for example).
>
>>
>> * All existing issues should be resolved in Jira. Copying or moving
>> Jira issues to GitHub is discouraged unless there is a good reason.
>
>
> I'm also fine with this. Again - allows for a gradual transition without 
> extra effort for you. My experience tells me such
> transition will be a pretty rapid process anyway. If you take a look at how 
> fast it was to switch to pull requests vs.
> patch-in-jira, it's likely to follow the same kind of pattern.
>
> Dawid

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to