public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: grobian@gentoo.org
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] New Portage release
Date: Sat, 8 Feb 2014 15:58:11 +0100	[thread overview]
Message-ID: <20140208155811.22b91ea3@TOMWIJ-GENTOO> (raw)
In-Reply-To: <20140208090315.GP70664@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2858 bytes --]

On Sat, 8 Feb 2014 10:03:15 +0100
Fabian Groffen <grobian@gentoo.org> wrote:

> Hey all,

Hey Fabian, let's see what I can address to give you an idea, as I've
been busy in other areas than Portage and Gentoo lately note that I
don't necessarily speak for decisions of the team.

> I'm sorry if this has been discussed previously.  I admit not having
> read all of the mails on this list recently.

There's also impromptu chatter on IRC, but I haven't heard of it; greps
on a case-insensitive release, version, 2.2.9, 2.3 or 3.0 yield nothing.

> Long story short: what are the plans on releasing 2.2.9?

Under my impression the current way we work is to release when there is
a need to it; either a lot of fixes, a severe bug, a long time, ... At
least that's how we got to release 2.2.8.

<aside idea>
Though there have been some months between 2.2.7 and 2.2.8; so, maybe I
think we should try to release on a monthly basis if that's possible.
Just to ensure we do releases and don't forget about doing them. It
would be nice if there's like a maximum waiting time from the moment a
bug is set IN_PROGRESS; furthermore, this could allow us to say to the
user "This will be part of the next release this/next month.".
</aside idea>

> 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, ...

When you say "long while" here, do you mean the time between 2.2.7 and
2.2.8 or the time after 2.2.8? The previous version 2.2.7 was released
on 23 Sep 2013 and the current version 2.2.8 on 06 Jan 2014, there was
a huge time between both lasting several months; however, the time
after 2.2.8 is only slightly over a month.

> ..., what's the plans here? Is there anyone at all who can/dares to
> spin a release?

Since we've managed to release 2.2.8; I guess that if the Portage team
agrees, we can/dare to spin a new release. But that would depend on if
we have enough / important fixes [1], what we still want to add to this
release (no idea, but people are busy on all some patches), ...

 [1]: https://bugs.gentoo.org/show_bug.cgi?id=484436

> Apologies in advance if this has been discussed recently.
> 
> Thanks,
> Fabian

Thanks for bringing this up, given it has been a month it is certainly
an interesting matter to come up for discussion again; I guess we can
discuss this at the end of the Portage meeting that happens later today.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2014-02-08 14:59 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 [this message]
2014-02-08 18:26 ` Brian Dolbec
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=20140208155811.22b91ea3@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=grobian@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