[Qgis-developer] Freeze on release-2_8 branch

[Sandro Santilli]

On Wed, Jul 22, 2015 at 08:09:49PM +1000, Nyall Dawson wrote:
> On 14 July 2015 at 00:04, Matthias Kuhn <matthias at opengis.ch> wrote:
> > Hi
> >
> >> On Mon, Jul 13, 2015 at 03:44:28PM +0200, Sandro Santilli wrote:
> >>> On Mon, Jul 13, 2015 at 03:30:38PM +0200, Matthias Kuhn wrote:
> >>>> Regarding this, I would propose to put the freeze in place as of
> >>>>
> >>>> Tue, Jul 14, 12:00 UTC
> >>>> And - presuming there are no regressions found - 2.8.3 will be tagged on
> >>>> Tue, Jul, 28.
> >>> +1, but I'd avoid the word "freeze" as it may be confusing.
> >>>
> >>> We're basically asking all developers to refrain from pushing more
> >>> backports in that branch until 2.8.3 is released.
> >> Oh, forgot to mention, we're also asking developers to _test_
> >> the branch, or it would make no sense to wait another week, right ?
> >> It might actually help to make an official call for testing on the
> >> users list too. I'm sure many will be happy to test the next stable
> >> release before it comes out (either from snapshot or directly from
> >> git). I've submitted by "make Experimental" already.
> >>
> >> --strk;
> > +1 I planned to send a tweet tomorrow but any widespread call for
> > testing will be good (but mainly by power users and organizations who
> > actually use it. We cannot put that also on the developers back)
> 
> I'd really like to backport c8dcf97 (critical for 2.8.3 IMO) and
> a1a8d1b (nice to have for 2.8.3), but don't want to reset the
> countdown now. Is there anyway around this?

I noticed 2.8.3 was tagged on July 28, as anticipated,
but did not see any announcement mail.
Is that waiting for some form of packaging ?

Also, were those two commits backported ?
There's no trace of those hashes in the history of 2.8 branch.

--strk;