* Re: [gentoo-project] EAPI bump should require revbump
@ 2012-10-25 19:15 99% ` Petteri Räty
0 siblings, 0 replies; 1+ results
From: Petteri Räty @ 2012-10-25 19:15 UTC (permalink / raw
To: gentoo-project
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
On 25.10.2012 16:16, Ian Stakenvicius wrote:
>
>
> Also please post these things
>> to gentoo-dev mailing list next time. This mailing list is for
>> project wide non technical issues.
>
>
> It was suggested to me to post here because #1) it's a policy
> discussion rather than a technical one, and #2) it reaches a bigger
> audience as many devs have tuned out to gentoo-dev@ ..
>
My educated guess is that most of those who are tuned out of gentoo-dev
don't follow this mailing list either. Last time we looked at
subscription numbers gentoo-project had less people than gentoo-dev.
Those who suggested you to post here didn't know our mailing list
policies. Granted it's not always easy to know where to post. Discussing
technical policies belongs to gentoo-dev. Especially in matters like
these that concern the Portage tree.
>
> As for your previous statement -- I was not aware of a policy that
> excludes EAPI bumps from occurring on stable packages. This would
> certainly suffice to alleviate the original concerns and probably be
> more effective as a policy than always requiring revbump on EAPI change.
>
There's a general policy that one should refrain from changing the logic
for ebuilds marked stable. EAPIs so far haven't introduced features that
would require being urgently but to stable.
regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2012-10-19 13:52 [gentoo-project] EAPI bump should require revbump Ian Stakenvicius
2012-10-25 12:41 ` Petteri Räty
2012-10-25 13:16 ` Ian Stakenvicius
2012-10-25 19:15 99% ` Petteri Räty
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox