appcast-brainstorming: Difference between revisions
(initial summary) |
No edit summary |
||
| Line 1: | Line 1: | ||
<h1>Appcast Brainstorming </h1> | |||
The purpose of this page is to capture software updates practices in the wild, as one effort to codify practices currently used in the automatic update system called Sparkle. | |||
__TOC__ | |||
== Authors == | |||
* [http://factoryjoe.com/ Chris Messina] | |||
== Context == | |||
Sites like iusethis.com, versiontracker.com, macupdate.com and download.com among others should be investigated and documented for object names and attributes. | Sites like iusethis.com, versiontracker.com, macupdate.com and download.com among others should be investigated and documented for object names and attributes. | ||
| Line 6: | Line 14: | ||
Lastly, this work should be seen as compatible with hAtom, possibly as a prelude to a format that could be embedded as the payload of an hfeed object. | Lastly, this work should be seen as compatible with hAtom, possibly as a prelude to a format that could be embedded as the payload of an hfeed object. | ||
Work should be carried out on the [[appcast-examples | Appcast Examples]] page. | |||
Revision as of 19:07, 27 July 2007
Appcast Brainstorming
The purpose of this page is to capture software updates practices in the wild, as one effort to codify practices currently used in the automatic update system called Sparkle.
Authors
Context
Sites like iusethis.com, versiontracker.com, macupdate.com and download.com among others should be investigated and documented for object names and attributes.
Among common data in a software update changelog are changes or fixes, completed bugs, new features or modified behavior, and known issues. A version number is also typically supplied, but takes on many forms and is not always numeric.
Lastly, this work should be seen as compatible with hAtom, possibly as a prelude to a format that could be embedded as the payload of an hfeed object.
Work should be carried out on the Appcast Examples page.