On Sat, 3 Jun 2017 13:48:31 -0400 Jeremy Bicha <[email protected]> wrote:
> On Sat, Jun 3, 2017 at 12:26 PM, Petr Kovar <[email protected]> wrote: > > Assuming that we don't want to block bug fixes to docs because of > > translations (which are, arguably, also wrong and need fixing), I'd propose > > making more bug fix releases than just .1 and .2. Rolling a new tarball is > > pretty cheap on the upstream side and we could, for example, release a > > 3.26.3 (or, 3.26.1.1, 3.26.2.1, etc.), which would follow some formal > > process of string freeze period. This would only apply to docs packages, of > > course. > > > > I think that would be a good compromise. Thoughts? > > Yes, absolutely. I tried coming up with a simple, easily > understandable proposal but I think my initial proposal was *too* > simple. Adding a procedure for thawing and refreezing for bugfix > updates sounds very appropriate. > > As a translator, how long would you suggest we wait after re-freezing > before releasing the new tarball? So, considering the number of translation updates we usually get and the schedule at https://wiki.gnome.org/ThreePointTwentyfive, what about something like this: September 11, 3.26.0, string freeze starts September 25, 3.26.0.1, string freeze ends October 2, 3.26.1, string freeze starts October 16, 3.26.1.1, string freeze ends October 23, 3.26.2, string freeze starts November 6, 3.26.2.1, string freeze ends Not sure how many string freeze releases we really want to make. We could just drop 3.26.2.1, for example, as it might come too late in the release schedule. Cheers, pk _______________________________________________ gnome-doc-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-doc-list
