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 MacDonald http://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 -~----------~----~----~----~------~----~------~--~---
