[sugar] Activity versioning schema
Jameson "Chema" Quinn
Tue Jul 15 15:34:46 EDT 2008
On Tue, Jul 15, 2008 at 12:57 PM, C. Scott Ananian <cscott at laptop.org>
> 2008/7/15 Jameson Chema Quinn <jquinn at cs.oberlin.edu>:
> > If you have a better idea of how Glucose should handle these issues,
> > share it. Simplifying assumptions are good, even if they're not 100%
> Versions in activity.info files are either plain integers, or
> RPM-standard version strings, with no pretense that these correspond
> in any way to sugar major releases or anything at all, except that
> they are ordered: if the activity updater sees that you have version
> N, and there is a version M announced[*] as compatible with your build
> where M > N, then it will suggest that you upgrade to M. All other
> meanings are encoded with other mechanisms.
> I meant the UI issues, since that is what Mikus objected to. I.e., can
multiple versions of the same activity coexist on same xo? What about
journal instances from multiple versions of an activity? What can we do
concretely to try to avoid/deal with this situation?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel