On 22/3/19 19:54, Javier Hernandez wrote:


On Fri, Mar 22, 2019 at 7:40 PM Samuel Thibault <sthiba...@debian.org <mailto:sthiba...@debian.org>> wrote:

    Samuel Thibault, le ven. 22 mars 2019 14:21:43 +0100, a ecrit:
    > Javier Hernandez via gnome-accessibility-list, le mer. 20 mars
    2019 11:56:36 +0100, a ecrit:
    > > There is the Maintainers Corner [1], where you can find all
    the information you
    > > need to know in order to maintain a module.
    >
    > Thanks! I won't have time do spend on it in the coming days, but
    I can
    > have a look a bit later.

    jhbuild setup went smoothlier than I expected, so I'm ready to make a
    release.


Sweet!

    > > On Wed, Mar 20, 2019 at 11:28 AM apinheiro
    <[2]apinhe...@igalia.com <mailto:apinhe...@igalia.com>> wrote:
    > > > (I could check that the current git master does work fine here)
    > >
    > > First: take into account that I'm not sure if at this point
    you can add
    > > more functionality to a 3.31.X/3.32.X Accerciser release, due the
    > > freezes.
    >
    > Sure. But what was already in 3.31.4 is fine for 3.32, right?
    > The only notable commit I can see since then is "Stop using
    intltool",
    > which is a build fix, not source code change, so it should be fine.

    Actually, AIUI, the freeze is only for uncommitted code, so what is
    already in master can be just uploaded?


Right, there's no problem, the code is already there. ;)


No. That's wrong. I have just sent a detailed email to Samuel, but again, the freezes are about releases, and what a release (that is a tarball) include compared with the next one. It doesn't matter if the code is already on master or on any other branch.


You can check anytime about the ongoing freezes here: https://wiki.gnome.org/Schedule


Cheers,
Javi

    Samuel

_______________________________________________
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list

Reply via email to