Are import and versioning dependent or just lumped together under C since both need to be done.
I'd vote for B). Export and Import are often migration processes, so there is great value in having either. Thanks, Nick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luke Melia Sent: November 6, 2007 12:12 AM To: track-discuss Subject: [Tracks-discuss] Import/Export features: in or out for 1.5 release? Hi Tracks folks, The current status of the import/export features in the trunk is this: Export to YAML, XML, & CSV is implemented. Import is not implemented. Versioning has not been considered (AFAIK) So, in order to move speedily to a 1.5 release, we need to consider how this feature should ship. Our options, for your input: A) Remove "Import/Export" from the UI. B) Rename "Import/Export" to "Export" and adjust language accordingly. C) Someone volunteers to implement Import and come up with a plan for dealing with versioning of data as Tracks evolves. Thoughts? Cheers from New Orleans, Luke _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
