Skip to content
Mingye Wang edited this page Jul 21, 2015 · 31 revisions

For an efficient AOSC OS development experience, it is strongly advised that you finish reading this page, on the work-flow model of abbs tree.

Rationale

AOSC OS had been using the "Autobuild" tool for system building/development since summer 2013, when :Next project first started. However, simply by using autobuild will not provide developers with advanced capability for developers to collaborate on package updating, issue reporting, multiple branch development, etc.

abbs tree is an utilization of the abbs tool kit - abbs is a service manager for Autobuild. An "abbs tree" provides a tree-like organization for the abbs specs+autobuild-manifest system. By using Git, it is now possible for developers to provide testing branch that includes cutting edge packages that (obviously) needs testing, and for users to report issues in their AOSC OS experience.

Basic knowledge

Basic knowledge you would need to know before you even attempt to start getting your tools, if you have never known anything about the "abbs tree", or have never used Git, please read carefully.

  • Structure - Tells you how to look at this weird mixture.

Please be aware that some abbs features are built on git, and most abbs repos are also git-managed one. Learning Git well can help you accelerate your process a lot. Pro Git and GitHub Help are always your good friends.

Our Workflow also involves a lot of Gitting, and this would be mentioned later.

Developers

Specifications

Clone this wiki locally