Re: [GitLab] Updated to 11.1

2018-07-24 Thread Jordan petridis via desktop-devel-list
Including in this release is a bugfix which would allow Maintainers to be able to edit and push changes to Merge Requests branches directly. Feature docs: https://docs.gitlab.com/ee/user/project/merge_requests/allow_collaboration.html Upstream issue:

Re: No app menu changes for GNOME 3.30, please!

2018-07-24 Thread mcatanzaro
On Tue, Jul 24, 2018 at 8:53 AM, Allan Day wrote: I'd expected there to be some discussion about the timeline and a decision by the Release Team. As it is, we're less than a week away from UI freeze and most apps haven't changed their app menus. For consistency's sake, it would be better to

Re: No app menu changes for GNOME 3.30, please!

2018-07-24 Thread Allan Day
Isaque Galdino wrote: > > Humm, from [1], I understood we could start the migration. > "Summer 2018 > (...) > Apps can start migrating during the 3.30 cycle > Fall 2018 > (...) > 3.30 ships with app menu support in the shell, but most apps don't use it > anymore " I know that's what

Re: No app menu changes for GNOME 3.30, please!

2018-07-24 Thread Isaque Galdino via desktop-devel-list
Humm, from [1], I understood we could start the migration. "Summer 2018 (...) Apps can start migrating during the 3.30 cycle Fall 2018 (...) 3.30 ships with app menu support in the shell, but most apps don't use it anymore " I've already changed Notes [2] & [3] and build new stuff on that

No app menu changes for GNOME 3.30, please!

2018-07-24 Thread Allan Day
Hi everyone, I've noticed some apps have started removing their app menus, or copying their app menu items elsewhere. Please, don't make any changes to your menus yet! Unless we have a mass migration over a single cycle, we'll end up with a complete mess. The plan that I previously sent to this

Re: [GitLab] Group runners: And why CI is slow in forks

2018-07-24 Thread Carlos Soriano
Just a short heads up for people following the mail, you can easily set up your own hardware/laptop or cloud as a runner for projects . On the GUADEC's GitLab workshop we did in 5 minutes. However, what we want is to have a consistent and good experience

Re: [GitLab] Group runners: And why CI is slow in forks

2018-07-24 Thread Carlos Soriano
That sounds great! Seems you know how to set up this which is wonderufl so we can get this going. Sure, we can make a call, I will follow up off-list. Cheers On Tue, 24 Jul 2018 at 09:15, Walter Vargas wrote: > Hi Carlos, > > Thank you for your concerns regarding the costs associated with CI

Re: [GitLab] Group runners: And why CI is slow in forks

2018-07-24 Thread Walter Vargas
Hi Carlos, Thank you for your concerns regarding the costs associated with CI infrastructure; the last week I was talking to Emmanuel that I would like to donate CPU capacity of one of my cloud accounts for the runners. Please let me know if we can schedule a quick call this week to discuss