Re: [GitLab] IMPORTANT: Mass migration plan

--===============6165765050632954601==
Content-Type: multipart/alternative; boundary="0000000000002921cb0567df4601"

--0000000000002921cb0567df4601
Content-Type: text/plain; charset="UTF-8"

By request, cc'ing this list.

On 20 March 2018 at 18:01, Carlos Soriano <[email protected]> wrote:

> Hello community,
>
> After a few months of manually migrating projects we have moved already
> over 60, most of them were core modules to make sure the most important
> projects were migrated before the mass migration happens. We are now at the
> point where a mass migration makes more sense than continuing handling
> migrations one by one, in part also because of the increasing amount of
> requests.
>
> *Proposed plan and timeline for mass migration*
>
> - Projects that want their bugs migrated will create an issue in our
> infrastructure similar to this
> <https://gitlab.gnome.org/Infrastructure/GitLab/issues/172> over the next
> two months. These project bugs will be migrated to GitLab issues between
> June 1st and June 15th 2018. [0]
> - Individual projects that it's important for them to move to GitLab
> sooner (i.e. GSoC projects, core modules, etc.) can still do so with the
> same procedure as before. Feel free to ping me regularly about those.
> - Projects that doesn't create an issue for bug migration will migrate
> only the repository, also by June 1st 2018.
> - Projects that didn't opt in to migrating bugs can still do so while
> Bugzilla is not phased out, however timing will be different and the issues
> will be migrated in batches once every two months or so.
> - Bugzilla will only allow comments by June 1st 2018. Reporting new bugs
> on Bugzilla will be disabled. New issues will be reported and managed in
> GNOME's GitLab.
> - Bugzilla will be phased out and much likely converted into a static
> website by February 2020 (the proposed date may vary as we're still
> evaluating all the possible solutions to make sure all the bugs will remain
> available in read-only mode after Bugzilla's service decommission). We'll
> still evaluating possible ways of keeping old bugs available for historical
> reasons.
> - Cgit will be phased out and removed by June 1st 2018.
>
> The goal is to have all GNOME projects moved to GitLab by GUADEC 2018; I
> left some time for eventual issues between 15th June and 6th July.
>
> If you are a maintainer and you consider some issue in the migration
> process or GitLab itself a big problem for your project, please take a look
> if we are tracking it already in the upstream priorities for GNOME
> <https://gitlab.com/gitlab-org/gitlab-ce/issues/43566>. If we do so,
> consider those are ongoing effort items and hopefully there will be some
> progress in the upcoming months. If we don't track it, either create an
> issue in our infrastructure (preferred, so others can comment too) with the
> link to the upstream report or contact me in IRC or email and we can
> discuss if it should be considered part of our GNOME priorities.
>
> Feel free to share your thoughts and comments about the proposal and I
> hope the timeline fits well with your activities.
>
> *General update*
>
> - GitLab worked upstream
> <https://gitlab.com/gitlab-org/gitlab-ce/issues/22292> on *being able to
> rebase and modify non-dev* (from forks) MR/branches as we requested
> recently and the feature will be available on the 22nd of this month. Let
> me share our thanks to them for taking quick action.
> - Issues with *login/register raising 500 errors *due to Google's
> ReCAPTCHA are now fixed.
> - Amazon AWS for *CI on-demand* is set up and available to use, CI should
> be fast and scalable. This is being possible thanks to the help of
> sponsors, stay tuned for the actual announcements.
>
> [0] This is because it's not feasible to migrate all the issues from
> Bugzilla for several technical details, and from what we experienced with
> other projects the migration of bugs don't achieve as much as was thought.
> Projects can take this as an opportunity to start using new features of
> GitLab to be more efficient towards issue management.
>

--0000000000002921cb0567df4601
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">By request, cc&#39;ing this list.<div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On 20 March 2018 at 18:01, Carlos Soriano =
<span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_blan=
k">[email protected]</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div dir=3D"ltr"><div id=3D"m_4990684714882814619gmail-magicdomid2" clas=
s=3D"m_4990684714882814619gmail-"><span class=3D"m_4990684714882814619gmail=
-">Hello community,</span></div><div id=3D"m_4990684714882814619gmail-magic=
domid3" class=3D"m_4990684714882814619gmail-"><br></div><div id=3D"m_499068=
4714882814619gmail-magicdomid4" class=3D"m_4990684714882814619gmail-"><span=
 class=3D"m_4990684714882814619gmail-">After a few months of manually migra=
ting projects we have moved already over 60, most of them were core modules=
 to make sure the most important projects were migrated before the mass mig=
ration happens. We are now at the point where a mass migration makes more s=
ense than continuing handling migrations one by one, in part also because o=
f the increasing amount of requests.</span></div><div id=3D"m_4990684714882=
814619gmail-magicdomid5" class=3D"m_4990684714882814619gmail-"><br></div><d=
iv id=3D"m_4990684714882814619gmail-magicdomid6" class=3D"m_499068471488281=
4619gmail-"><span class=3D"m_4990684714882814619gmail-b"><b>Proposed plan a=
nd timeline for mass migration</b></span></div><div id=3D"m_499068471488281=
4619gmail-magicdomid7" class=3D"m_4990684714882814619gmail-"><br></div><div=
 id=3D"m_4990684714882814619gmail-magicdomid8" class=3D"m_49906847148828146=
19gmail-"><span class=3D"m_4990684714882814619gmail-">- Projects that want =
their bugs migrated will create an issue in our infrastructure similar to <=
/span><span class=3D"m_4990684714882814619gmail-url"><a href=3D"https://git=
lab.gnome.org/Infrastructure/GitLab/issues/172" target=3D"_blank">this</a><=
/span><span class=3D"m_4990684714882814619gmail-"> over the next two months=
. These project bugs will be migrated to GitLab issues between June 1st and=
 June 15th 2018. [0]</span></div><div id=3D"m_4990684714882814619gmail-magi=
cdomid9" class=3D"m_4990684714882814619gmail-"><span class=3D"m_49906847148=
82814619gmail-">- Individual projects that it&#39;s important for them to m=
ove to GitLab sooner (i.e. GSoC projects, core modules, etc.) can still do =
so with the same procedure as before. Feel free to ping me regularly about =
those.</span></div><div id=3D"m_4990684714882814619gmail-magicdomid10" clas=
s=3D"m_4990684714882814619gmail-"><span class=3D"m_4990684714882814619gmail=
-">- Projects that doesn&#39;t create an issue for bug migration will migra=
te only the repository, also by June 1st 2018.</span></div><div id=3D"m_499=
0684714882814619gmail-magicdomid11" class=3D"m_4990684714882814619gmail-"><=
span class=3D"m_4990684714882814619gmail-">- Projects that didn&#39;t opt i=
n to migrating bugs can still do so while Bugzilla is not phased out, howev=
er timing will be different and the issues will be migrated in batches once=
 every two months or so.</span></div><div id=3D"m_4990684714882814619gmail-=
magicdomid12" class=3D"m_4990684714882814619gmail-"><span class=3D"m_499068=
4714882814619gmail-">- Bugzilla will only allow comments by June 1st 2018. =
Reporting new bugs on Bugzilla will be disabled. New issues will be reporte=
d and managed in GNOME&#39;s GitLab.</span></div><div id=3D"m_4990684714882=
814619gmail-magicdomid13" class=3D"m_4990684714882814619gmail-"><span class=
=3D"m_4990684714882814619gmail-">- Bugzilla will be phased out and much lik=
ely converted into a static website by February 2020 (the proposed date may=
 vary as we&#39;re still evaluating all the possible solutions to make sure=
 all the bugs will remain available in read-only mode after Bugzilla&#39;s =
service decommission). We&#39;ll still evaluating possible ways of keeping =
old bugs available for historical reasons.<br></span></div><div id=3D"m_499=
0684714882814619gmail-magicdomid14" class=3D"m_4990684714882814619gmail-"><=
span class=3D"m_4990684714882814619gmail-">- Cgit will be phased out and re=
moved by June 1st 2018.</span></div><div id=3D"m_4990684714882814619gmail-m=
agicdomid15" class=3D"m_4990684714882814619gmail-"><br></div><div id=3D"m_4=
990684714882814619gmail-magicdomid16" class=3D"m_4990684714882814619gmail-"=
><span class=3D"m_4990684714882814619gmail-">The goal is to have all GNOME =
projects moved to GitLab by GUADEC 2018; I left some time for eventual issu=
es between 15th June and 6th July.</span></div><div id=3D"m_499068471488281=
4619gmail-magicdomid17" class=3D"m_4990684714882814619gmail-"><br></div><di=
v id=3D"m_4990684714882814619gmail-magicdomid18" class=3D"m_499068471488281=
4619gmail-"><span class=3D"m_4990684714882814619gmail-">If you are a mainta=
iner and you consider some issue in the migration process or GitLab itself =
a big problem for your project, please take a look if we are tracking it al=
ready in </span><span class=3D"m_4990684714882814619gmail-url"><a href=3D"h=
ttps://gitlab.com/gitlab-org/gitlab-ce/issues/43566" target=3D"_blank">the =
upstream priorities for GNOME</a></span><span class=3D"m_499068471488281461=
9gmail-">. If we do so, consider those are ongoing effort items and hopeful=
ly there will be some progress in the upcoming months. If we don&#39;t trac=
k it, either create an issue in our infrastructure (preferred, so others ca=
n comment too) with the link to the upstream report or contact me in IRC or=
 email and we can discuss if it should be considered part of our GNOME prio=
rities.</span></div><div id=3D"m_4990684714882814619gmail-magicdomid19" cla=
ss=3D"m_4990684714882814619gmail-"><br></div><div id=3D"m_49906847148828146=
19gmail-magicdomid20" class=3D"m_4990684714882814619gmail-"><span class=3D"=
m_4990684714882814619gmail-">Feel free to share your thoughts and comments =
about the proposal and I hope the timeline fits well with your activities.<=
/span></div><div id=3D"m_4990684714882814619gmail-magicdomid21" class=3D"m_=
4990684714882814619gmail-"><br></div><div id=3D"m_4990684714882814619gmail-=
magicdomid22" class=3D"m_4990684714882814619gmail-"><span class=3D"m_499068=
4714882814619gmail-b"><b>General update</b></span></div><div id=3D"m_499068=
4714882814619gmail-magicdomid23" class=3D"m_4990684714882814619gmail-"><br>=
</div><div id=3D"m_4990684714882814619gmail-magicdomid24" class=3D"m_499068=
4714882814619gmail-"><span class=3D"m_4990684714882814619gmail-">- GitLab <=
a href=3D"https://gitlab.com/gitlab-org/gitlab-ce/issues/22292" target=3D"_=
blank">worked upstream</a> on </span><span class=3D"m_4990684714882814619gm=
ail-b"><b>being able to rebase and modify non-dev</b></span><span class=3D"=
m_4990684714882814619gmail-"> (from forks) MR/branches as we requested rece=
ntly and the feature will be available on the 22nd of this month. Let me sh=
are our thanks to them for taking quick action.<br></span></div><div id=3D"=
m_4990684714882814619gmail-magicdomid25" class=3D"m_4990684714882814619gmai=
l-"><span class=3D"m_4990684714882814619gmail-">- Issues with </span><span =
class=3D"m_4990684714882814619gmail-b"><b>login/register raising 500 errors=
 </b></span><span class=3D"m_4990684714882814619gmail-">due to Google&#39;s=
 ReCAPTCHA</span><span class=3D"m_4990684714882814619gmail-b"><b> </b></spa=
n><span class=3D"m_4990684714882814619gmail-">are now fixed.</span></div><d=
iv id=3D"m_4990684714882814619gmail-magicdomid26" class=3D"m_49906847148828=
14619gmail-"><span class=3D"m_4990684714882814619gmail-">- Amazon AWS for <=
/span><span class=3D"m_4990684714882814619gmail-b"><b>CI on-demand</b></spa=
n><span class=3D"m_4990684714882814619gmail-"> is set up and available to u=
se, CI should be fast and scalable. This is being possible thanks to the he=
lp of sponsors, stay tuned for the actual announcements.</span></div><div i=
d=3D"m_4990684714882814619gmail-magicdomid27" class=3D"m_499068471488281461=
9gmail-"><br></div><div id=3D"m_4990684714882814619gmail-magicdomid28" clas=
s=3D"m_4990684714882814619gmail-"><span class=3D"m_4990684714882814619gmail=
-">[0] This is because it&#39;s not feasible to migrate all the issues from=
 Bugzilla for several technical details, and from what we experienced with =
other projects the migration of bugs don&#39;t achieve as much as was thoug=
ht. Projects can take this as an opportunity to start using new features of=
 GitLab to be more efficient towards issue management.</span></div></div>
</blockquote></div><br></div></div>

--0000000000002921cb0567df4601--

--===============6165765050632954601==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
devel-announce-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/devel-announce-list

--===============6165765050632954601==--