Hello all.
Besides whether the migration of existing issues should be done or not
(we still do not reach an agreement on it), I started to play around
with GitHub issue metadata with a test repository.
The current migration plan in my mind:
* Issue Type -> Supported with labels (e.g. "type:bug"); it also can
be attached when opening issues with issue templates.
* Issue Priority -> Not supported.
* Affects Versions -> Not supported.
* Components -> Supported with labels (e.g.: "module:core").
* Resolution -> Not supported.
* Fix Version(s) -> Partially supported with Milestone; an issue can
have only one milestone - I'm fine with it.
As you may see I'm going to drop the most of metadata that is
supported in Jira for the sake of brevity. If you have objections or
other perspectives, could you please speak up.
Tomoko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Besides whether the migration of existing issues should be done or not
(we still do not reach an agreement on it), I started to play around
with GitHub issue metadata with a test repository.
The current migration plan in my mind:
* Issue Type -> Supported with labels (e.g. "type:bug"); it also can
be attached when opening issues with issue templates.
* Issue Priority -> Not supported.
* Affects Versions -> Not supported.
* Components -> Supported with labels (e.g.: "module:core").
* Resolution -> Not supported.
* Fix Version(s) -> Partially supported with Milestone; an issue can
have only one milestone - I'm fine with it.
As you may see I'm going to drop the most of metadata that is
supported in Jira for the sake of brevity. If you have objections or
other perspectives, could you please speak up.
Tomoko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org