| 1 |
On Sat, 8 Feb 2014 10:03:15 +0100 |
| 2 |
Fabian Groffen <grobian@g.o> wrote: |
| 3 |
|
| 4 |
> Hey all, |
| 5 |
|
| 6 |
Hey Fabian, let's see what I can address to give you an idea, as I've |
| 7 |
been busy in other areas than Portage and Gentoo lately note that I |
| 8 |
don't necessarily speak for decisions of the team. |
| 9 |
|
| 10 |
> I'm sorry if this has been discussed previously. I admit not having |
| 11 |
> read all of the mails on this list recently. |
| 12 |
|
| 13 |
There's also impromptu chatter on IRC, but I haven't heard of it; greps |
| 14 |
on a case-insensitive release, version, 2.2.9, 2.3 or 3.0 yield nothing. |
| 15 |
|
| 16 |
> Long story short: what are the plans on releasing 2.2.9? |
| 17 |
|
| 18 |
Under my impression the current way we work is to release when there is |
| 19 |
a need to it; either a lot of fixes, a severe bug, a long time, ... At |
| 20 |
least that's how we got to release 2.2.8. |
| 21 |
|
| 22 |
<aside idea> |
| 23 |
Though there have been some months between 2.2.7 and 2.2.8; so, maybe I |
| 24 |
think we should try to release on a monthly basis if that's possible. |
| 25 |
Just to ensure we do releases and don't forget about doing them. It |
| 26 |
would be nice if there's like a maximum waiting time from the moment a |
| 27 |
bug is set IN_PROGRESS; furthermore, this could allow us to say to the |
| 28 |
user "This will be part of the next release this/next month.". |
| 29 |
</aside idea> |
| 30 |
|
| 31 |
> Longer version: for Prefix I likely need a new release soon to get |
| 32 |
> some fixes out of the door. Since I like to stay on par with mainline |
| 33 |
> portage's versioning here, I've been going along with mainline |
| 34 |
> portage's releases for a while, which worked fine. Now we haven't |
| 35 |
> got a release for a long while, ... |
| 36 |
|
| 37 |
When you say "long while" here, do you mean the time between 2.2.7 and |
| 38 |
2.2.8 or the time after 2.2.8? The previous version 2.2.7 was released |
| 39 |
on 23 Sep 2013 and the current version 2.2.8 on 06 Jan 2014, there was |
| 40 |
a huge time between both lasting several months; however, the time |
| 41 |
after 2.2.8 is only slightly over a month. |
| 42 |
|
| 43 |
> ..., what's the plans here? Is there anyone at all who can/dares to |
| 44 |
> spin a release? |
| 45 |
|
| 46 |
Since we've managed to release 2.2.8; I guess that if the Portage team |
| 47 |
agrees, we can/dare to spin a new release. But that would depend on if |
| 48 |
we have enough / important fixes [1], what we still want to add to this |
| 49 |
release (no idea, but people are busy on all some patches), ... |
| 50 |
|
| 51 |
[1]: https://bugs.gentoo.org/show_bug.cgi?id=484436 |
| 52 |
|
| 53 |
> Apologies in advance if this has been discussed recently. |
| 54 |
> |
| 55 |
> Thanks, |
| 56 |
> Fabian |
| 57 |
|
| 58 |
Thanks for bringing this up, given it has been a month it is certainly |
| 59 |
an interesting matter to come up for discussion again; I guess we can |
| 60 |
discuss this at the end of the Portage meeting that happens later today. |
| 61 |
|
| 62 |
-- |
| 63 |
With kind regards, |
| 64 |
|
| 65 |
Tom Wijsman (TomWij) |
| 66 |
Gentoo Developer |
| 67 |
|
| 68 |
E-mail address : TomWij@g.o |
| 69 |
GPG Public Key : 6D34E57D |
| 70 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives