Skip to content
This repository was archived by the owner on Nov 20, 2020. It is now read-only.

Dev: Guidelines

Jump to bottom
mkottman edited this page Mar 19, 2011 · 15 revisions

Repositories

All LuaDist repositories should follow these simple rules.

  • If original source is available on Git/GitHub, fork it.
  • Tags should always follow the version in dist.info.
    • If tag already exists for add an incremental "-1" "-2" .. "-n" suffix to the version tag.
    • No "v" prefix.
    • Question: what if the upstream repo already contains version tags? Should they be replaced by LuaDist tags?
  • Master branch should always point to most recent package version.
  • All new modifications should be developed in branches other than master.
    • Recommended branch names are "packagename-version" or "feature name"
    • Do not tag development versions.

LuaDist/Repository

Primary repository that aggregates all module sub-repositories in the distribution. The purpose of this repository is to ease development and generate dist.manifest file for the deployment utility. While working with this repository keep the following in mind:

  • ! All Development issues go here.
    • Issues in other repositories are discouraged.
  • Submodules DO NOT point to master.
    • When working with a repository always check your branch, you may loose your changes.
    • Make sure the repository is up to date.
  • If you update master branch of any module make sure LuaDist/Repository points to it.
Clone this wiki locally