Mutter awt fix.
Andrew Haley
aph at redhat.com
Fri May 20 07:11:33 PDT 2011
On 05/20/2011 03:00 PM, Dr Andrew John Hughes wrote:
> On 15:15 Tue 17 May , Andrew Haley wrote:
>> On 05/17/2011 03:04 PM, Dr Andrew John Hughes wrote:
>>> On 10:39 Tue 17 May , Andrew Haley wrote:
>>>> On 17/05/11 01:41, Dr Andrew John Hughes wrote:
>>>>> On 16:42 Mon 16 May , Pavel Tisnovsky wrote:
>>>>>>
>>>>>> AFAIK you still did not received the rights to push this change to
>>>>>> OpenJDK right (because the repos is in frozen state)? Or do you have bug
>>>>>> ID for this fix at least?
>>>>>>
>>>>>
>>>>> Denis' patch was reviewed and accepted. It hasn't been pushed because
>>>>> Oracle seem to have decided to make up some new rules, limiting pushes
>>>>> to the repositories without any prior notice.
>>>>
>>>> This is presumably the OpenJDK 7 schedule, which was posted some time ago.
>>>> Only higher-priority bug fixes are allowed.
>>>>
>>>> http://openjdk.java.net/projects/jdk7/
>>>
>>> And what it doesn't say is how 'higher-priority bug fixes' are
>>> determined. We've only ever been submitting bug fixes for the most
>>> part, so I would have assumed that we could go on doing so for some
>>> time. However, the reality seems to be that we now can't submit
>>> anything for the next three months to OpenJDK7, but Oracle can.
>>
>> I don't see how that follows.
>
> It's just an observation, based on current activity. Oracle are still
> committing stuff, yet our patches are being refused.
There seems to be a lack of transparency, certainly. I'm trying to
find out exactly what is going on.
>>> I wouldn't be happy releasing IcedTea7 to our users with known
>>> issues, so we will continue making the changes we need, but locally.
>>
>> That depends on the severity of the bug, surely. Sometimes you have
>> to make the judgement call that something will not be fixed because it
>> would potentially invalidate the test cycle and might break something
>> else. This is all perfectly normal: there has to be a freeze window.
>
> I don't have a problem with a freeze; we have them with IcedTea. But
> this only seems to be a freeze on external contributions, and not one
> that has been discussed, but imposed.
I don't think that it is a freeze on external contributions only.
AFAIAA, the freeze only allows show-stopping bugs to be fixed. With
regard to the schedule, it was announced a long time ago, and from
what I remember the comments were along the lines of "bring it on."
I think the real situation is probably better than it appears.
Andrew.
More information about the distro-pkg-dev
mailing list