Oh yeah!
Great work guys 👍👍👍
Le dim. 26 mai 2019 à 00:55, Richard Duivenvoorde a
écrit :
> Update from migration team:
>
> Migration of all Redmine issue is DONE !
>
> https://github.com/qgis/QGIS/issues/
>
> The interaction limitation has ended and you can start working on (your)
> issues on GitHub.
>
> Go, fix, enjoy and happy QGISsing on github!
>
> Regards,
>
> Richard Duivenvoorde
>
> ps according to Jorge (aka 'migration team'), there is some minor
> housekeeping to be done, but users and dev can... GO :-)
>
>
>
> On 25/05/2019 14.56, Richard Duivenvoorde wrote:
> > Update from mirgration team:
> >
> > Hi @all,
> >
> > The issue migration from Redmine to GitHub is going on smoothly (but
> slow).
> >
> > The first phase (moving the issues) is finished. All 19845 issues are
> > now on GitHub :-)
> >
> > Since the issue ids have changed, we started a second run to replace
> > old ids with the new ones. This second phase is faster than the
> > first one. It will take about 9 to 10 hours (we are able to update
> > +-2200 issues per hour and we have almost 20k issues).
> >
> > To prevent people for changing or comment issues, we will keep the
> > interaction limited to developers with push access, until the migration
> > is complete. Developers with push access can do PR and MR (but can also
> > enjoy the weekend ;-).
> >
> > So, we expected to have the migration finished today by 22:00 (GMT+1)
> > (London time).
> >
> > Thanks for your comprehension!
> >
> >
> > On 22/05/2019 14.06, Richard Duivenvoorde wrote:
> >> Hi All (lists),
> >>
> >> We propose to do the Redmine -> Github migration next friday 24th of may
> >> at 8:00 CET (+2).
> >>
> >> More or less following this Migration plan:
> >>
> >>
> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/141#issuecomment-478296818
> >>
> >> To be clear: this means http://issues.qgis.org cannot be used on
> friday,
> >> untill the migration is finished and checked.
> >>
> >> If anybody has knowledge of an easy way to make Redmine readonly, please
> >> let us know. Some googling to me only revealed changing the database
> >> user or fiddling with the users in the db itself.
> >>
> >> Jorge will be in the lead for the Migration team
> >> I (among others) will be around for QGIS Infra
> >> Any help or encouragement is appreciated :-)
> >>
> >> Let's meet on IRC on friday morning, we can further decide on
> >> communication if needed/wanted.
> >>
> >> If I miss something, please let us know.
> >>
> >> Regards,
> >>
> >> Richard Duivenvoorde
> >> ___
> >> QGIS-Developer mailing list
> >> qgis-develo...@lists.osgeo.org
> >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >>
> >
> > ___
> > Qgis-user mailing list
> > Qgis-user@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
> >
>
> ___
> Qgis-community-team mailing list for organizing community resources such
> as documentation, translation etc..
> qgis-community-t...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-community-team
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
