LarryK wrote: > My first proposal is that we have a new release of Timeline. > ==>> I suggest that we immediately have a new tag, call it 2.1.0 per > Nicolas' message > http://groups.google.com/group/simile-widgets/msg/36ccd27838932dbc > I think tagging the code as-is is a good thing.
In parallel to that, we need to think about where to serve that version. The Simile group as it is right now does not have dedicated human resources to manage releases of these APIs on http://static.simile.mit.edu/. It has been suggested that we go ask Google or some other parties to host these APIs. > By creating the new tag, the latest tag will reflect a rev later than > any of the previous tags. > (I figured this out by running the "Revision Graph" tool that comes > with TortoiseSVN.) > > Several reasons: > 1) Currently, the later tag for the Timeline svn tree refers to an > *earlier* version of the software than an earlier tag (see below) > I think that's because the version on static.simile.mit.edu is actually earlier. Changes were made to the code but they weren't updated on static.simile.mit.edu. > 2) The current tag refers to sw version 1287 on March 13th. It is now > September, and the sw is up to 1539, with a number of changes. > > My second proposed change is here: > http://groups.google.com/group/simile-widgets/browse_thread/thread/c0... > -- rather minor, I'm happy to wait until after you've seen my more > substantive proposals. > The link got cut off... Could you post it again? > Is anyone acting as a check-in coordinator? > With no tests, I'd prefer to have someone looking at changes and > commenting (before or after the commit). On the other hand "commiters > rule" according to David. > > ==>>> In lieu of tests, is anyone keeping up with the Trunk and trying > out the new commits as they occur? > No-one that I'm aware of. I've been swamped more than expected. Nicolas and Axel are knowledgeable about testing and have suggested some alternatives before. I'd gladly defer to their judgment. Frankly, right now I'd prefer to see more commits than serious testing in place. I think the code base is quite small to really mess it up, so I'm not worried about bad commits. Having no commit seems like a more worrisome thing, since the project appears stale. David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" 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/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
