Archives
Archives
| From: | Jeroen Roovers <jer@g.o> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-libs/confuse: confuse-2.7.ebuild ChangeLog | ||
| Date: | Sun, 10 Mar 2013 18:04:30 | ||
| Message-Id: | 20130310190418.40e7c3aa@marga.jer-c2.orkz.net | ||
| In Reply to: | Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-libs/confuse: confuse-2.7.ebuild ChangeLog by "Tomáš Chvátal" |
||
| 1 | On Sun, 3 Mar 2013 12:44:18 +0100 |
| 2 | Tomáš Chvátal <tomas.chvatal@×××××.com> wrote: |
| 3 | |
| 4 | > If I remember correctly the damn rule is to put it for 30 days into |
| 5 | > testing, and as you said there was no previous version on arm so users |
| 6 | > could've reported some issues, i agree that sometimes you have to |
| 7 | > ignore the rules to really fix stable, but was this such case for |
| 8 | > sure? |
| 9 | |
| 10 | I've done straight to stable keywording _many_ times. The rationale is |
| 11 | that with no previous version stable for a particular architecture, |
| 12 | there really are no users who could see _regressions_, hence waiting |
| 13 | the nominal thirty days is meaningless in this case. |
| 14 | |
| 15 | |
| 16 | jer |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-libs/confuse: confuse-2.7.ebuild ChangeLog | hasufell <hasufell@g.o> |
| Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-libs/confuse: confuse-2.7.ebuild ChangeLog | Samuli Suominen <ssuominen@g.o> |