Thanks, Juan, for everything!
And I agree, Claudio, I should just push a damn release out with the
current (good) state of things!! I will look at doing that ASAP.
Does anyone dissent?
Richard
On 28 September 2014 01:31, claudio canepa <[email protected]> wrote:
>
>
> On Sat, Sep 27, 2014 at 4:59 AM, "Juan J. Martínez" <[email protected]>
> wrote:
>
>> Hello,
>>
>> I haven't worked in anything pyglet related since July, although I keep
>> an eye on the bugtrack, it is very difficult to me to find time and the
>> right mood to work in the "1.2 release blockers".
>>
>
> [...]
>
>
>> It's been over a year since my fist commits back in July 2013; I'm happy
>> to see that I've helped to improve pyglet a little bit ;)
>>
>> Regards,
>>
>> Juan
>>
>>
> First, let me thank you for all the work you put
> - triaging the issue tracker
> - working with people on issues to help investigating the problems
> - integrating patches
> - taking bug reports, investigating and fixing them
> - care also for this list
>
> Lots of hours and brain invested there, and yes, I think pyglet is
> noticeable better because of that work.
> Thank you.
>
> Second, and that directed to all pyglet users, devs and owners:
>
> I think most of us would concur that
> - we need a pyglet release
> - the actual codebase is good enough to release
> - not releasing discourages people to contribute to pyglet
>
> We need a pyglet release
> -------------------------------------
>
> - actual code supports the current Mac OS gui Cocoa, last released not
>
> - actual code supports much better 64 bits OS' architectures
>
> - people hear about pyglet, goes to pypi, get an old unmantained
> version, falls on issues fixed in current code base.
> Lots of brain cycles and goodwill lost.
> We have seen this on this list, the bug tracker, the pyweek forum and the
> issue tracker for software that depends on pyglet
>
> - software that depends on pyglet cannot handle the pyglet dependency
> in a standard way, because the codebase is not on pypi
>
>
> The actual code is good enough to release
> -------------------------------------------------------------
>
> - Documentation builds
> - Distribution .tar.gz builds and installs correctly
> - No showstopper issues, ie most common uses don't find crashes or
> incorrect behavior
>
> Not releasing discourages people to contribute to pyglet
>
>
> ---------------------------------------------------------------------------------
>
> - Being in perpetual 'theres a release near' discourages anything that
> is not minor fixes, because nobody wants to rock the boat near a release.
>
> - Why put much work if it will never be released ?
>
> - The sensation that there's something unspoken about the 'non
> releasing' thing.
> There were at least four times when releasing a new version would have
> been natural, and it did not happen:
> - after the Phillip Nguyen integration of Cocoa support
> - a previous issue tracker thinning done by Andreas Schiefer, Adam
> Bark, Winston W, Anatoly Techtonik and other people, including py3
> support
> - After integration of the sphinx based documentation (Txema Vicente,
> others)
> - Any time from March 2014 to today, ie at an advanced stage of Juan
> thinning of the issue tracker.
> That does not inspire confidence.
>
> So, what can be done now ?
> =====================
>
> Please, please, active devs and gatekeepers (Richard ? Alex ?) please talk
> and decide to make it happen.
>
> After that, all is needed is someone with the credentials push the
> buttons to make the release. It is all nearly automated now.
> - package building works
> - documentation building works
> - documentation site is uptodate (or will need refresh with last
> documentation build, and should not be hard, Juan done that sometimes and
> it did not mention problems from that side)
> - upload to pypi is a nonissue
> - codebase state is reasonable
>
> Sorry for my bad english, cheers all
>
> claudio
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "pyglet-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/pyglet-users.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
