Sorry for not getting back to you sooner. I was on vacation.
it is something we prepared
https://lists.apache.org/thread/07p1xyz210755qsl5gt466nyp3tdzmrs
I don't know why it did not happen in this migration
@Benjamin any idea?
The PR linking did work because the step “importing issues” failed
No, sorry, no idea. I will ask Sandra about it.
Am Do., 6. Feb. 2025 um 08:25 Uhr schrieb Herve Boutemy :
>
>
>
> On 2025/02/05 08:16:44 Guillaume Nodet wrote:
> > Searching for infos in old issues often involves switching between github
> > (for commits / PRs) and JIRAs.
> > If history can be rew
On Thu, 6 Feb 2025 at 08:15, Hervé Boutemy wrote:
>
> Le mercredi 5 février 2025, 07:48:53 CET Guillaume Nodet a écrit :
> > Le mer. 5 févr. 2025 à 07:36, Slawomir Jaranowski
> >
> > a écrit :
> > > I'm still not convitient if we really need copy all issues from jira
> > > to github - as I wrote
On 2025/02/05 08:16:44 Guillaume Nodet wrote:
> Searching for infos in old issues often involves switching between github
> (for commits / PRs) and JIRAs.
> If history can be rewritten, it would clearly be a benefit.
> An example:
> * https://github.com/apache/maven-jlink-plugin/issues/499
> * h
Le mercredi 5 février 2025, 07:48:53 CET Guillaume Nodet a écrit :
> Le mer. 5 févr. 2025 à 07:36, Slawomir Jaranowski
>
> a écrit :
> > I'm still not convitient if we really need copy all issues from jira
> > to github - as I wrote many times
> >
> > - jira will be exist with us
> > - I don't b
In json, you need an empty list or object ([] or {}).
As of the duplicates:
I'll send GitHub support the list of duplicates today. They were willing to
help us clean up.
As of why the first created issues where pending, they are still
investigating that. Lessons learned: next time wait and don't
On Wed, 5 Feb 2025 at 09:55, Benjamin Marwell wrote:
>
> It should have been. You're right.
> I'll talk to infra about this.
> We also disabled jira comments to the ML for migration.
>
maybe we can put an empty value in notification ...
notifications:
...
issues:
...
https://github.com/apache
It should have been. You're right.
I'll talk to infra about this.
We also disabled jira comments to the ML for migration.
On Wed, 5 Feb 2025, 09:29 Slawomir Jaranowski,
wrote:
> One more issue ... we have many notifications on ML, like:
> https://lists.apache.org/list?iss...@maven.apache.org:l
One more issue ... we have many notifications on ML, like:
https://lists.apache.org/list?iss...@maven.apache.org:lte=1M:jira-importer
Maybe it can be possible to disable notifications during migration time.
On Tue, 4 Feb 2025 at 23:42, Elliotte Rusty Harold wrote:
>
> If you look at https://gith
Searching for infos in old issues often involves switching between github
(for commits / PRs) and JIRAs.
If history can be rewritten, it would clearly be a benefit.
An example:
* https://github.com/apache/maven-jlink-plugin/issues/499
* https://github.com/apache/maven-jlink-plugin/pull/229
It would
if we don't copy, we can't search in one place: I'm often searching in issues
to get why we did something in the past (that years later looks strange, but
history helps understand)
I'd love to let some time to try before admitting we can't keep it simple in
one single place once migrated
Regar
Le mer. 5 févr. 2025 à 07:36, Slawomir Jaranowski
a écrit :
> I'm still not convitient if we really need copy all issues from jira
> to github - as I wrote many times
>
> - jira will be exist with us
> - I don't believe that users before creating new issue look for old -
> if yes they have a link
I'm still not convitient if we really need copy all issues from jira
to github - as I wrote many times
- jira will be exist with us
- I don't believe that users before creating new issue look for old -
if yes they have a link to old issues
- many issues should be triaged again - it is manually wor
We are on contact with GitHub support. Please refrain from manually closing
them for now.
Before that, some were not displayed, were in status pending, which
effectively made them missing.
I'll keep you posted.
On Tue, 4 Feb 2025, 23:44 Elliotte Rusty Harold, wrote:
> If you look at https://
If you look at https://github.com/apache/maven-jlink-plugin/issues
you'll notice that all the issues from the Jira have been copied into
github multiple times.
--
Elliotte Rusty Harold
elh...@ibiblio.org
-
To unsubscribe, e-mail
15 matches
Mail list logo
