To break this down more into stages of implementation: 1. .jar version requirements in the manifest
2. Channel manifests to decouple USK edition from build number and allow different build identifiers in the upgrade notification. 3. Partial channel definition support with name/description/USK/revocation SSK. This includes UI for adding channels and enabling / disabling them. I'm assuming it's sufficient to update to whichever channel has an update discovered most recently? Or does this need some kind of precedence, perhaps based on build strings? Like setuptools. [0] 4. Support for plugins querying artifacts to allow things like serving Fred packages - or maybe plugin-only update channels? 5. Signing requirements and verification. [0] http://pythonhosted.org/setuptools/setuptools.html#specifying-your-project-s-version
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
