Sean Whitton writes:
> Let's definitely reconsider those 'must' requirements in response to
> this work, but let's not commit ourselves to the idea that it's always a
> bug for the Release Team's conception of an RC bug, and Policy 'must'
> requirements, to disagree.
> The Release Team's
Hello,
On Sun 29 Dec 2019 at 11:20am -08, Russ Allbery wrote:
> Paul Gevers writes:
>> On 21-11-2019 13:59, Paul Gevers wrote:
>
>>> [Disclaimer: the words below are as a member of the release team, but
>>> not necessarily those of the team. We haven't discussed this yet.]
>
>> We have had a
Paul Gevers writes:
> On 21-11-2019 13:59, Paul Gevers wrote:
>> [Disclaimer: the words below are as a member of the release team, but
>> not necessarily those of the team. We haven't discussed this yet.]
> We have had a discussion, and there were no objections against my vision
> below.
>> I
Dear Policy Editors,
On 21-11-2019 13:59, Paul Gevers wrote:
> [Disclaimer: the words below are as a member of the release team, but
> not necessarily those of the team. We haven't discussed this yet.]
We have had a discussion, and there were no objections against my vision
below.
> I can
Dear Russ,
[Disclaimer: the words below are as a member of the release team, but
not necessarily those of the team. We haven't discussed this yet.]
On 17-11-2019 20:47, Russ Allbery wrote:
> Let me copy the release team. How would you all prefer to handle the
> relationship between
Bastian Blank writes:
> On Sun, Nov 17, 2019 at 10:10:11AM -0800, Russ Allbery wrote:
>> +The Release Team may, at their discretion, downgrade a Policy requirement
>> +to a Policy recommendation for a given release of the Debian distribution.
>> +This may be done for only a specific package or
6 matches
Mail list logo
