My impression seems similar to the others in the thread, that the bulk of the bug-fixes have been done in the trunk rather than on the 1.1 maintenance. So, I've made a first pass at identifying which issues are addressed in the trunk and are not addressed in the maintenance branch.
I pulled the log messages from revision 2156(where the maintenance branch was made) to head from the trunk and the 1.1 maintenance branch. I grabbed the issue numbers out of these logs with grep, so I'm not claiming that this list entirely comprehensive. Here's the list of (revision: message) issues I found that were fixed in the trunk and were not fixed in 1.1 maintenance (according to log messages): 2459: Issue 418: Added float division in win32 mousewheel event 2458: Issue 424: fix typo in documentation 2457: Issue 416: infinite loop in resource.reindex with win32 paths. 2456: Issue 422: document the requirement for '/' in resource.path entries. 2455: Issue 414: multiple mouse buttons during drag on OSX (applied patch from swiftcoder) 2454: Issue 409: putting back pyglet.media.have_avbin 2453: Issue 423: glMultiDrawElements was being given garbage data when draw an IndexedVertexDomain 2452: Issue 381: migrating sprites lose VertexDomain attributes 2451: Fix for issue 413. 2450: Fix memory leak when loading images using QuickTime, issue 436. 2447: clean up better as per issue 408 2434: code cleanup for app and input, issue #393 2433: code cleanup for font and text, issue #392 2432: apply image cleanup patch for issue #391 2430: Issue 390: various typos addressed 2428: Issue 382: evdev name may be utf-8 encoded. 2425: Issue 368: Remove saved_by_zero font from astraea demo. 2424: Issue 368: fix executable bits of various files, remove shebangs from non-exec files, fix line-endings on NOTICE. 2423: Issue 379: setup.py package list out of date 2422: Issue 380: OS X input typo 2421: Issue 376, add 2.6 to supported python versions in readmes 2420: Issue 377, scroll wheel broken on win32. 2402: PA driver: hold off on telling time until after write callback following seek. Fixes backward seek issue. 2344: Issue 294: Clarify Texture.create(rectangle) parameter, add force_rectangle parameter. 2339: Issue 357: Workaround ATI driver reporting GL 1.5 but not exporting glGenBuffers. 2338: Issue 353: xlib key symbol mismatch when shift key held. 2337: Issue 361: mouse dx/dy incorrect when window freshly mapped 2326: Issue 355: hex and octal constants parsed by wraptypes. 2325: Issue 358: spelling fix. 2237: Fix double flip problem when manually running event loop on win32 (e.g. WINDOW_INTIAL_FULLSCREEN test). Possibly fixes issue 335. 2227: Issue 334: check no modifiers present for ESC close window shortcut 2170: Issue 328: always clean build dir before creating mpkg dist. 2169: Issue 319: unschedule leaving dummy funcs in schedule list behind 2158: Issue 275: return True from EventDispatcher.dispatch_event if the event was handled. These are the issues I've found fixed in both trunk and 1.1 maintenance: 2364: Issue 362: fix generic attributes 2352: Issue 363: fix resource indexing of second level dirs. 2264: Issue 347: text is split into grapheme clusters before rendering glyphs to texture. Tested on win32. 2262: Issue 345: mouse platform visible after window recreate 2239: Issue 336: WGL error checking requires initial context 2217: Issue 304, fix fix. 2215: Revert previous documentation commit and fix issue 331 as described And these are noted from log messages as fixed in maintenance but not necessarily released: 2168: Issue 329: unschedule leaving dummy funcs in schedule list. 2446: Issue 410: typo fix -b On Aug 15, 12:09 pm, Tristam MacDonald <[email protected]> wrote: > On Sat, Aug 15, 2009 at 2:32 PM, Bruce Smith <[email protected]> wrote: > > On Sat, Aug 15, 2009 at 4:22 AM, Tristam MacDonald > > <[email protected]>wrote: > > >> .... > >> It sounds to me as if we should focus our efforts on bringing trunk up to > >> a full release, and put 1.2dev on hold for the immediate future. > > > Alex: thanks very much for your status description, that's just what we > > need. > > > Tristam: To clarify a possible misunderstanding: AFAIK, trunk and 1.2dev > > are the same thing, in the svn repository. That is, the most recent releases > > have been made from > > >http://pyglet.googlecode.com/svn/branches/pyglet-1.1-maintenance/ > > > but new features and refactoring intended for "development towards 1.2" (as > > well as many bugfixes) have been done only in the trunk, i.e. in > > >http://pyglet.googlecode.com/svn/trunk/ > > > since there is no separate (non-trunk) branch corresponding to 1.2dev. This > > means that "bring trunk to a full release, but put 1.2dev on hold" is not so > > simple, since trunk and 1.2dev are two names for the same "branch". > > My understanding is that the 1.2 development is in one of two places: > > http://code.google.com/p/pyglet/source/browse/trunk/experimental/ > > http://code.google.com/p/pyglet/source/browse/branches/enhancements_1_2/ > > And that the trunk itself (with the exception of trunk/experimental) > contains solely patches to the 1.1 development. > > -- > Tristam MacDonaldhttp://swiftcoder.wordpress.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
