Activity Team: Difference between revisions
| Line 95: | Line 95: | ||
===A typical update cycle=== | ===A typical update cycle=== | ||
Anyone can contribute a patch to a Sugar Activity. The typical work cycle involves an interaction with the activity maintainer as follows: | |||
# make a clone (anyone) | # make a clone (anyone) | ||
# make your changes (anyone) | # make your changes (anyone) | ||
# mail your patch to sugar_devel (anyone) | # mail your patch to sugar_devel (anyone) | ||
# | # make changes as per suggestions by the project maintainer and developer community | ||
# push your changes (anyone) | # push your changes (anyone) | ||
# request a merge (anyone) | # request a merge (anyone) | ||
# tag the new version in git (maintainer) | # write release notes (anyone) | ||
# create the .xo and .tar files (maintainer) | # tag the new version in git (project maintainer) | ||
# upload .tar to download.sugarlabs.org (maintainer) | # create the .xo and .tar files (project maintainer) | ||
# upload .xo to activities.sugarlabs.org (maintainer) | # upload .tar to download.sugarlabs.org (project maintainer) | ||
# upload .xo to activities.sugarlabs.org (project maintainer) | |||
# update wiki documentation (anyone) | # update wiki documentation (anyone) | ||