On Wed, Sep 11, 2019 at 8:01 AM, Shaun McCance wrote:
It is true that the documentation team is currently unable to keep up
with our release cycle. But removing freezes would create yet another
barrier to us getting things back on track.
I don't understand the difficulty. Maintainers have to
On Mon, 2019-09-09 at 08:57 -0500, mcatanz...@gnome.org wrote:
> On Fri, Sep 6, 2019 at 3:47 PM, mcatanz...@gnome.org wrote:
> > If there are any recent examples of a documentation change being
> > committed within the freeze window in response to a freeze break
> > notification, please let me
On Fri, Sep 6, 2019 at 3:47 PM, mcatanz...@gnome.org wrote:
If there are any recent examples of a documentation change being
committed within the freeze window in response to a freeze break
notification, please let me know; otherwise, I don't think this
change should be controversial.
Does
On Fri, 2019-09-06 at 15:47 -0500, mcatanz...@gnome.org wrote:
> Hi,
>
> Historically, our rules for freezes have required notifying
> gnome-doc-list@ of any freeze breaks. This rule has not always been
> followed (I'm a flagrant violator myself). Since nowadays
> documentation
> operates on a
