It sure would be nice if all Simile Widgets had coincident releases, with the latest stable version of Exhibit pointing to the latest stable versions of the others (Timeline, Timeplot, Painter, possibly eventually Runway.) I don't have a feel for the independence or development process for each project. Can this be done? You can easily see some confusion if not.
Does it make sense to have a wiki page explaining the social development process? Anybody want to take a stab at it? Regarding the documentation wiki, should we be documenting the latest stable or trunk versions? For now, I would recommend documenting the latest trunk versions (as many changes have already been made and announced) and move to stable when released. For future versions, we'll need to have some disclaimers which version the docs pertain to. Just a thought... In each development cycle, once significant chnages are made or warranted, a wiki page could be created listing what needs to be done for the release to happen (beta, then stable.) That page could point to existing issues or feature requests (in the Google Code issue queue.) The issues need to be tested, enhancements need to be documented, etc.... The primary developers would need to lead the charge here. - John ************************************************** John Callahan, Geospatial Application Developer Delaware Geological Survey, University of Delaware Email: [email protected] ************************************************** Ryan Lee wrote: > David Huynh wrote: > >>> Seems like it would be almost as much work to add a 2.3.2 timeline >>> containing the patches and point exhibit at that, as it would to just >>> upgrade exhibit to use the (already existing) "trunk" timeline. What >>> is the status of moving Exhibit to the "trunk" timeline? Also, what is >>> the process for re-generating and uploading the "bundle" and >>> "bundle-debug" versions of timeline and exhibit once changes are made >>> to the source? >>> >> Exhibit shouldn't point to trunk Timeline, as then Exhibit would break >> when trunk Timeline is in the midst of development. >> >> The process for releasing Timeline involves >> - running ant in the timeline directory to generate bundle files >> - updating RELEASE_NOTES.txt and CHANGES.txt in the timeline directory >> - testing and committing timeline >> - within the hour, trunk.simile-widgets.org/timeline/ should get updated >> with the trunk version. test it, too. >> - tagging timeline (into timeline/tags) >> - svn co the api-site project >> - updating svn:externals in the timeline directory to link to the new tag >> - I think we have a cron job that should update api.simile-widgets.org >> within the hour. If not, log onto simile-widgets.org and update it >> manually. >> > > If we're going to push a new Timeline version, we should push a new > version of Exhibit to make use of it, as well as incorporate the latest > in the map and timeplot extensions in a more stable branch. > > David's described the mechanical process of pushing out a new Timeline > version; do we have a social process for it? > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
