Hi all,
It's time to focus on getting 14.0 released, so the master branch will
be frozen on Sunday, December 22. Only release blocker bug fixes and
translation updates will be accepted after that date. It's possible to
convince the maintainers to accept also things that don't fall into
those two
Hello,
According to the usual release schedule, master should have been frozen
already in December, but I've been postponing that (for no good
reason). Now finally, if there are no objections, I declare master
frozen so that we can soon release 12.0. There won't be a release
candidate published
On Thu, 2017-04-27 at 14:12 +0200, Georg Chini wrote:
> On 24.04.2017 15:58, Tanu Kaskinen wrote:
> > On Sat, 2017-04-22 at 20:37 +0200, Georg Chini wrote:
> > > On 21.04.2017 15:32, Tanu Kaskinen wrote:
> > > > Hi all,
> > > >
> > > > It's been three months since the last release, which means
On 24.04.2017 15:58, Tanu Kaskinen wrote:
On Sat, 2017-04-22 at 20:37 +0200, Georg Chini wrote:
On 21.04.2017 15:32, Tanu Kaskinen wrote:
Hi all,
It's been three months since the last release, which means that it's
time to freeze the master branch in preparation for the next release.
Here's
On Sat, 2017-04-22 at 20:37 +0200, Georg Chini wrote:
> On 21.04.2017 15:32, Tanu Kaskinen wrote:
> > Hi all,
> >
> > It's been three months since the last release, which means that it's
> > time to freeze the master branch in preparation for the next release.
> >
> >
> > Here's a review of the
On 21.04.2017 15:32, Tanu Kaskinen wrote:
Hi all,
It's been three months since the last release, which means that it's
time to freeze the master branch in preparation for the next release.
Here's a review of the current blockers:
frequent crash in pa_alsa_path_set_volume
Hi all,
It's been three months since the last release, which means that it's
time to freeze the master branch in preparation for the next release.
Only release blocker bug fixes and translation updates should be pushed
to master. Other patches should go to the "next" branch. If you think
