[prev in list] [next in list] [prev in thread] [next in thread]
List: gtk-devel
Subject: Re: migrating gtk
From: Emmanuele Bassi <ebassi () gmail ! com>
Date: 2018-04-16 18:32:20
Message-ID: CALnHYQGWP=E7uwT2bWpNeLYXjMiD5J-2WbBzBWS76qPc0jHykw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi all;
it's time for an update.
On 2 February 2018 at 14:04, Matthias Clasen <matthias.clasen@gmail.com>
wrote:
> Hey Carlos,
>
> we discussed gitlab migration for gtk here at the hackfest. Our
> conclusions were as follows:
>
> * We want to migrate the git repository as soon as possible
>
The repository was migrated successfully, and we've been using it for the
past two months. There is a redirect in place for git.gnome.org URLs that
will automatically take you to gitlab.gnome.org for GTK; the only thing
that changed is the Git push URL for people that have the commit bit set
and a GNOME Git account.
Switching to GitLab allowed us to benefit from things like automated CI
(build and tests) for branches and merge requests; we're also building
Flatpak versions of gtk-demo and gtk-widget-factory on master, so you can
ask other people to immediately test your changes without having to rebuild
GTK and deal with its dependencies. Also on the CI side, we have a Windows
CI runner, which means that master is currently build tested using MSYS2.
It would be stellar if we could get a MSVC and a macOS runners as well.
* For bugs:
> * Do a sweep now, close all >5 year old bugs, needinfo all >1 old ones
>
This has been done.
> * Wait a few weeks, then close the needinfoed bugs that didn't get a
> response
>
* Triage the rest
>
We waited 2 months, and now all the bugs left in NEEDINFO state have been
closed.
Additionally, we've set up redirections so that going to Bugzilla to file a
new issue will automatically send you to the Issues page on GitLab.
* Migrate what's left at the end
>
We're in the process of migrating:
https://gitlab.gnome.org/Infrastructure/GitLab/issues/228
This will take a while once it starts; I'll send another email to the list
to notify when the process starts and ends.
Ciao,
Emmanuele.
--
https://www.bassi.io
[@] ebassi [@gmail.com]
[Attachment #5 (text/html)]
<div dir="ltr">Hi all;<br><div><div class="gmail_extra"><br></div><div \
class="gmail_extra">it's time for an update.<br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On 2 February 2018 at 14:04, \
Matthias Clasen <span dir="ltr"><<a href="mailto:matthias.clasen@gmail.com" \
target="_blank">matthias.clasen@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div><div><div><div><div><div><div><div>Hey Carlos,<br><br></div>we \
discussed gitlab migration for gtk here at the hackfest. Our conclusions were as \
follows:<br><br></div>* We want to migrate the git repository as soon as \
possible<br></div></div></div></div></div></div></div></blockquote><div><br></div><div>The \
repository was migrated successfully, and we've been using it for the past two \
months. There is a redirect in place for <a \
href="http://git.gnome.org">git.gnome.org</a> URLs that will automatically take you \
to <a href="http://gitlab.gnome.org">gitlab.gnome.org</a> for GTK; the only thing \
that changed is the Git push URL for people that have the commit bit set and a GNOME \
Git account.<br><br></div><div>Switching to GitLab allowed us to benefit from things \
like automated CI (build and tests) for branches and merge requests; we're also \
building Flatpak versions of gtk-demo and gtk-widget-factory on master, so you can \
ask other people to immediately test your changes without having to rebuild GTK and \
deal with its dependencies. Also on the CI side, we have a Windows CI runner, which \
means that master is currently build tested using MSYS2. It would be stellar if we \
could get a MSVC and a macOS runners as well.<br><br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div><div><div><div><div><div></div>* For bugs:<br></div> * Do a sweep \
now, close all >5 year old bugs, needinfo all >1 old \
ones<br></div></div></div></div></div></blockquote><div><br></div><div>This has been \
done.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div><div><div><div></div> * Wait a few weeks, then close the needinfoed \
bugs that didn't get a \
response<br></div></div></div></div></blockquote><div><div></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div></div> * Triage \
the rest</div></div></div></blockquote><br></div><div>We waited 2 months, and now all \
the bugs left in NEEDINFO state have been \
closed.<br></div><div><br></div><div>Additionally, we've set up redirections so \
that going to Bugzilla to file a new issue will automatically send you to the Issues \
page on GitLab.<br></div><div><br><blockquote class="gmail_quote" style="margin:0px \
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> * Migrate \
what's left at the end<br></blockquote><br></div></div>We're in the process \
of migrating: <a href="https://gitlab.gnome.org/Infrastructure/GitLab/issues/228">https://gitlab.gnome.org/Infrastructure/GitLab/issues/228</a><br></div><div \
class="gmail_extra"><br></div><div class="gmail_extra">This will take a while once it \
starts; I'll send another email to the list to notify when the process starts and \
ends.<br></div><div class="gmail_extra"><br></div><div \
class="gmail_extra">Ciao,<br></div><div class="gmail_extra"> Emmanuele.<br \
clear="all"></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature"><a \
href="https://www.bassi.io" target="_blank">https://www.bassi.io</a><br>[@] ebassi \
[@<a href="http://gmail.com" target="_blank">gmail.com</a>]</div> </div></div></div>
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic