On Nov 6, 2007, at 1:16 PM, Nicholas Van Weerdenburg wrote:
I'm still not clear. Are you thinking about export/import where
someone tries to import a file exported from an older version- in
which case, simply tagging exports with a version number and
rejecting imports with old versions may suffice. Or do have other
scenarios in mind?
Hi Nick,
I don't think this is an acceptable scenario -- if I want to change
Tracks hosting providers or restore to a backup, getting my data flat
out rejected because the versions are different is a pretty bad
experience, IMO.
Cheers from New Orleans,
Luke
Thanks,
Nick
-----Original Message-----
From: Luke Melia [mailto:[EMAIL PROTECTED]
Sent: November 6, 2007 10:14 AM
To: Nicholas Van Weerdenburg
Cc: track-discuss
Subject: Re: [Tracks-discuss] Import/Export features: in or out for
1.5 release?
On Nov 6, 2007, at 9:31 AM, Nicholas Van Weerdenburg wrote:
> Are import and versioning dependent or just lumped together under C
> since both need to be done.
My thoughts are that we need to think about versioning if we offer an
import option, because otherwise we have a big problem the first time
we want to introduce a feature that needs a schema change.
Cheers from NYC,
Luke
> 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
