The regular work flow after increasing version/stability in ''service.info'' file, is invoking one of ''dist*'' command to change local feed in ''dist/'' and place there tarballs, then invoke ''push'' command to rsync changed files to the server.
+
Work flow for services that don't require compilation stage:
+
+
* increase/change version/stability field in ''service.info'' file
+
* ''0sugar-publish dist'' to change local feed in ''dist/'' and place there tarball
+
* ''0sugar-publish push'' to rsync changed files from ''dist/'' to the server
+
+
Work flow for services that require compilation stage:
+
+
* increase/change version/stability field in ''service.info'' file
+
* ''0sugar-publish dist'' to add sources tarball to ''dist/'' and change local feed correspondingly
+
* on every platform, you are trying to support, run ''0sugar-publish dist-bin'' to build and add to local field, binaries for this particular platform
+
* ''0sugar-publish push'' to rsync changed files from ''dist/'' to the server