Re: Could we release new Accerciser version ?

Samuel Thibault <[email protected]> Fri, 22 Mar 2019 14:21:43 +0100
Newsgroups gmane.comp.gnome.accessibility.devel,gmane.comp.gnome.accessibility.general
Organization I am not organized
Message-ID <20190322132143.li562pva2ux3l7iy@function>
Hello,

Javier Hernandez via gnome-accessibility-list, le mer. 20 mars 2019 11:56:36 +0100, a ecrit:
> Samuel, yes, as co-maintainer you should be responsible for creating the
> releases.

Ok, I wasn't 100% sure so preferred to ask before doing anything that
would have unwanted consequences :)

> 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.

> In terms of producing a release, bear in mind that you need to produce a build
> against the current GNOME modulesets. I don't know how it works these days, in
> my case I used to have an up-to-date GNOME jhbuild environment to test
> accerciser and produce releases.

Ok.

> On Wed, Mar 20, 2019 at 11:28 AM apinheiro <[2][email protected]> 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.

> Second: there is another reason to do a 3.32 release. Current last
> Accerciser release is 3.31.4. That numbering points to a unstable
> release. There are some distros that doesn't include the latest release
> of a program/library, but the latest stable release.

That's what Alex told me, that prompted me to raise the question :)

I will have a look then.

Samuel