From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] New Portage release
Date: Sat, 8 Feb 2014 10:26:42 -0800 [thread overview]
Message-ID: <20140208102642.0935767d@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <20140208090315.GP70664@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
On Sat, 8 Feb 2014 10:03:15 +0100
Fabian Groffen <grobian@gentoo.org> wrote:
> Hey all,
>
> I'm sorry if this has been discussed previously. I admit not having
> read all of the mails on this list recently.
>
> Long story short: what are the plans on releasing 2.2.9?
>
> Longer version: for Prefix I likely need a new release soon to get
> some fixes out of the door. Since I like to stay on par with mainline
> portage's versioning here, I've been going along with mainline
> portage's releases for a while, which worked fine. Now we haven't
> got a release for a long while, what's the plans here? Is there
> anyone at all who can/dares to spin a release?
>
> Apologies in advance if this has been discussed recently.
>
> Thanks,
> Fabian
>
I hadn't thought about 2.2.9 just yet. We are having a meeting
tomorrow at Feb. 9, 19:00 UTC in #gentoo-meetings, join us and we can
discuss it more with the others. There have been a few bug fixes, but
I don't know if there is some others that should be dealt with before a
2.2.9 release.
If you can't attend the meeting, at least I will have a better idea of
when we will be able to do a release.
--
Brian Dolbec <dolsen>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2014-02-08 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 9:03 [gentoo-portage-dev] New Portage release Fabian Groffen
2014-02-08 14:58 ` Tom Wijsman
2014-02-08 18:26 ` Brian Dolbec [this message]
2014-02-09 18:12 ` Sebastian Luther
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=20140208102642.0935767d@big_daddy.dol-sen.ca \
--to=dolsen@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