Re: geary string freeze and upcoming release

[Michael Gratton <mike vee net>]

On Tue, 12 Feb, 2019 at 5:55 AM, Alexandre Franke <afranke gnome org> 
wrote:
> >  So hat's the best thing to do here? There's at least 8 languages 
> > that
> >  are basically fully translated, and a number of others may have 
> > these
> >  translated already, since the strings have been around for at least 
> > one
> >  release. Is it better to keep the existing forms intact and fix this
> >  after branching for the release, or should I land the fix now?
>
> Apologies if this is explained somewhere, but since you’re not
> following the GNOME release cycle can you clarify what your intentions
> for the next releases are? Depending on how the next minor and micro
> releases land, we might have a couple options.

Sure thing. Per the original email in this thread, the plan is to 
release 0.13 later this week. This is a feature release and will become 
the new stable release, replacing 0.12 as such.

Going forward, I plan to then quickly do a "UI refresh" release and 
switch over to the GNOME release numbering, around the same time or 
shortly after GNOME 3.32 comes out next month. This will have an 
updated icon and app menu moved into the main window so as to match 
GNOME 3.32 apps, and might be enhanced with libhandy so as to work 
better on narrow, portrait displays, if that isn't too disruptive.

I view this UI refresh release effectively as a point release (i.e. 
0.13.1), since I don't really plan on adding new features aside from 
the above), but am bumping the version since its a noticeable change 
from the perspective of a person using it, and it seems like a good 
excuse as any to switch to GNOME's numbering. There will be a series 
for point releases after that, too (i.e. 3.32.1, ...), for bug fix and 
translation updates.

After that I'd like to start following the GNOME release schedule 
proper.

Does that help?

//Mike

--
⊨ Michael Gratton, Percept Wrangler.
⚙ <http://mjog.vee.net/>