From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] portage-2.3.2 stable request?
Date: Fri, 4 Nov 2016 13:19:39 -0700 [thread overview]
Message-ID: <f3aa5716-db42-5bab-6d44-7569063f62f3@gentoo.org> (raw)
In-Reply-To: <20161104131422.585a1e73.dolsen@gentoo.org>
On 11/04/2016 01:14 PM, Brian Dolbec wrote:
> On Thu, 3 Nov 2016 15:55:23 -0700
> Zac Medico <zmedico@gentoo.org> wrote:
>
>> In about a week, portage-2.3.2 will be eligible for a stable request.
>>
>> The only potential problem that I've noticed is the complaint about
>> changes from bug 552814 causing issues for people using git sync with
>> overlay filesystems, but setting sync-depth = 0 gives those users a
>> workaround. There's also bug 597838, about the sync-depth setting
>> being ineffective, but I only know of a couple of people that have
>> been able to reproduce that.
>>
>> So, do we want to do a stable request portage-2.3.2 when the time
>> comes?
>
> I'm not sure. Do we -r1 it adding a patch or two and ask it be stabled?
>
There are just 4 commits since 2.3.2, and they all look good. Maybe we
should just cut a 2.3.3 release and wait another 30 days (we also need
to stabilize app-crypt/gkeys since it's needed by emerge-webrsync now).
--
Thanks,
Zac
next prev parent reply other threads:[~2016-11-04 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 22:55 [gentoo-portage-dev] portage-2.3.2 stable request? Zac Medico
2016-11-04 20:14 ` Brian Dolbec
2016-11-04 20:19 ` Zac Medico [this message]
2016-11-04 20:43 ` Michał Górny
2016-11-04 20:53 ` Zac Medico
2016-11-04 22:47 ` Brian Dolbec
2016-11-04 22:55 ` Zac Medico
2016-11-04 23:15 ` Zac Medico
2016-11-05 12:56 ` Manuel Rüger
2016-11-06 17:34 ` Brian Dolbec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3aa5716-db42-5bab-6d44-7569063f62f3@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox