No objection.
Thanks for taking care of the release.

Nicolas

On 9 Oct, 2009, at 20:14 , Ben Smith wrote:

>
> Howdy - I'm considering throwing together a release candidate in the
> next week or so, unless I get a reason not to.
>
> -b
>
> On Oct 7, 9:36 pm, PaweÅ‚ Sobkowiak <[email protected]> wrote:
>> I browsed through SVN logs and it seems that backports were completed
>> at the end of August.
>>
>> When will 1.1.4 be released?
>>
>> On Sep 10, 8:44 pm, claudio canepa <[email protected]> wrote:
>>
>>
>>
>>> On Thu, Sep 10, 2009 at 12:56 PM, Ben Smith
>>> <[email protected]>wrote:
>>
>>>> Hello,
>>
>>>> With pyweek over, I'd like to do what I can to make a pyglet 1.1.4
>>>> maintenance release from all the trunk backports done before  
>>>> pyweek.
>>>> I'm just testing the waters here, is anyone else interested in a  
>>>> new
>>>> maintenance release?  If so, which (if any) open issues should be
>>>> addressed?  How has the release process typically worked, and  
>>>> what can
>>>> I do to help it along?
>>
>>>> Thanks,
>>>> -b
>>
>>> I think it is a good idea: the current release will crash in at  
>>> least two
>>> situations, those are fixed in maintenance.
>>> And, it would be good that the recent bugfixes get tested in the  
>>> wild, which
>>> only would happen if released.
>>> While anyone can be tempted to say 'wait, let fix this or that', I  
>>> would say
>>> 'lets offer a better pyglet now, there always be time to do another
>>> release'.
>>
>>> The only tempting additions atm are:
>>> Two linux issues, with patches: 452 , 387
>>
>>> but maybe linux people can chime in about how good looking are the  
>>> patches ?
>>
>>> --
>>> claudio
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to