On Fri, Jan 23, 2015 at 2:59 PM, Rob <[email protected]> wrote:
> As Cocos already started using Pyglet 1.2, and most people with issues are
> also directed to download the development version, maybe it would be a good
> idea to release 1.2 officially. Any opinions on what needs to finish before
> a release can be made?
>
> Rob
>
>
I suggest *now* it is a good time to release, in the current status.
Reasons:
The current codebase will serve better than the last released, because
py3 support, 64bits support, Cocoa support on mac, many small fixes.
The last released version is effectively unsupported.
No crashes in common usage.
Integrating the patches in the issue tracker, forks, proposed changes
in this and other threads will take a long time and probably produce some
temporal instabilities. It would be good to have a known good, easy to
find, default option (pip) available.
Adding to the last point, pyweek usually comes in March or April, some
newcomers will look at the library before that time to get to speed. Is not
unusual to prefer the last released version (stability) or the one
available on pypi (convenience). So why not make easier the live of that
people ?
Packages that depends on pyglet cannot be pip friendly, because pip
will pull pyglet 1.1.4
As a signal to the community:
Why use a library with no releases in four years ?
Why wasting time building patches and PRs if they are never released
?
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.
