Hi,
Noticed a question about a way to automate, GitLab CI could automate beta and
stable releases for us, did some digging and found this Python package that
could help with that. Don’t know it this will help any, but here is a link to
that scrip.
On Sun, Feb 28, 2021 at 11:35 am, Michael Catanzaro
wrote:
And it turned that bad plumbing was at fault
(Turns out bad things happen when drain pipes slope upwards instead of
downwards)
___
desktop-devel-list mailing list
On Sat, Feb 27, 2021 at 7:42 pm, Bastien Nocera
wrote:
It's like giving your mate a key to your place so they can do laundry
while you're away. You don't expect them to have flooded the place
when
you get back.
In fairness, the one time I flooded a laundry room, I caught it pretty
quickly
On Sat, 2021-02-27 at 10:26 -0800, Philip Chimento via desktop-devel-
list wrote:
> On Tue, Feb 23, 2021 at 5:54 AM Emmanuele Bassi via desktop-devel-list
> wrote:
> > The release team can do "non maintainer" releases, of course; the
> > problem is, of course, that maintainers can be *very*
On Tue, Feb 23, 2021 at 5:54 AM Emmanuele Bassi via desktop-devel-list <
desktop-devel-list@gnome.org> wrote:
> The release team can do "non maintainer" releases, of course; the problem
> is, of course, that maintainers can be *very* protective of their fiefdoms,
> so the release team has to wait
Hi all, and long time no see, hope everyone is doing well...
On Tue, 2021-02-23 at 08:37 -0600, Michael Catanzaro wrote:
[...]
> On Tue, Feb 23, 2021 at 1:53 pm, Emmanuele Bassi via desktop-devel-list
> wrote:
> > In the end, though, releases are manual labour; only the maintainer
> > can say:
FWIW I agree that freeze should apply to tarballs, i.e. any features or
UI changes not in a tarball release by the beta tarball deadline ought
to be delayed until the next release cycle. Dropping major changes a
week later isn't fair to Shaun and anyone else working on
documentation. But
On Mon, 22 Feb 2021 at 00:20, Shaun McCance wrote:
> What I want is a discussion on how we can ensure beta releases happen in
> the future. For example, can we do more to automate releases? Or (again,
> for example), could we have an automated script that emails this list with
> modules missing
On Sun, Feb 21, 2021 at 4:20 PM Shaun McCance wrote:
> Hi Georges,
>
>
> What I want is a discussion on how we can ensure beta releases happen in
> the future. For example, can we do more to automate releases? Or (again,
> for example), could we have an automated script that emails this list
Hi Georges,
I appreciate that, and I'm sorry my email was perhaps abrasive and that
it upset you. I'll try to choose my words more carefully in the future.
It really wasn't my intention to assign blame. I'm also struggling to
keep plates spinning, and sometimes I drop them as well.
What I want
On Sun, 2021-02-21 at 15:47 -0500, Matthias Clasen via desktop-devel-
list wrote:
>
>
> On Sun, Feb 21, 2021 at 3:18 PM Shaun McCance
> wrote:
> > The freeze is pointless without beta releases, so what can we do to
> > enforce that beta releases happen?
> >
>
>
> Help out with the modules
Hi Shaun,
I appreciate how frustrating it is to have someone else negatively
impacting your
day work, and I'm sincerely sorry about that. I'm usually responsible for
doing
the Settings unstable releases, and Robert usually takes care of stable
releases.
I should have asked Robert to do this
On Sun, Feb 21, 2021 at 3:18 PM Shaun McCance wrote:
> Hi all,
>
> I just wasted a whole lot of time trying to figure out why I wasn't
> seeing GNOME 40 settings in both Rawhide and Tumbleweed, only to
> discover that gnome-control-center didn't get an upstream 40.beta
> release until a few
Hi all,
I just wasted a whole lot of time trying to figure out why I wasn't
seeing GNOME 40 settings in both Rawhide and Tumbleweed, only to
discover that gnome-control-center didn't get an upstream 40.beta
release until a few hours ago today.
This is extremely frustrating. For all practical
14 matches
Mail list logo
