[Project_owners] Should mozdev.org generate an updates.rdf file for our projects?

[Douglas E. Warner]

On Thursday 06 December 2007, Douglas E. Warner wrote:
> I'm thinking the next step is to generate an updates.rdf feed; we would
> only need to know how to group certain files together and what type of
> files they are (extension, theme, etc).

After gaining some more understanding of what goes into an updates.rdf file 
and what is available from an install.rdf file, I think the workflow for 
releasing a new update would go like this:

1) PO uploads their XPI file to their downloads/ folder
2) PO logs into mozdev.org and sees the new file in a grouped under their 
em:id (named using em:name)
3) PO chooses "release" beside the file and is asked to provide the following 
information:
  a) file hash (md5/sha1) to verify the file was uploaded properly
  b) update info url

Mozdev would be responsible for pulling the following information from the 
install.rdf:
* id
* name
* type
* version
* supported applications

This would allow us to provide the following features:
1) generation of updates.rdf files
2) search projects by supported applications
3) secure installations through InstallTrigger()

Thoughs/comments on this process?

Question: would we need to be able to provide some way to "age out" updates, 
or should only the most recent release show up in an updates.rdf?

-Doug
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://www.mozdev.org/pipermail/project_owners/attachments/20071207/1c3ad530/attachment.bin