Versioning and Package Management

aah releases per Semantic Versioning. aah commitment to provide stable release version of framework and it’s libraries. aah internally uses gopkg.in service codebase to provide versioning support on top of package management tools.

aahframework.org/<library-name>.vX points to appropriate tag versions; X denotes version number and it’s a stable release for production use.

import "aahframework.org/aah.v0"

High Level Info

aah codebase is hosted on Github and Development happens on branch vX-edge for example: v0-edge, v1-edge, etc. and branch master is tidy codebase of each release. Github tags are stable and production ready.

Learn more about aah release and development process

Package Management

aah HIGHLY RECOMMENDS you to use your choice of package management tool to lock libraries version for your application. Beside that aah also provides versioned release too, if you're just using go get.

To ensure aah have been tested with glide, dep and govendor package management tools.

How do I use it?

It is simple, go to aah application base directory and execute the commands from respective tool which you’re using.

For example: aahframework.org website codebase uses glide package management tool.

# as an example, application base directory
# refer respective tool documentation for the usage.
cd $GOPATH/src/aah-first-app

# glide tool
glide init
glide update

# govendor tool
govendor init
govendor add +external