Title: Versioning and Package Management Desc: aah framework release versions according to Semantic Versioning. aah commitment to provide stable versioned release of framework and it's libraries. Keywords: versioning, package management, stable version, release version
aah framework release versions according to Semantic Versioning.
aah commitment to provide stable release of framework and it's libraries. aah framework internally uses gopkg.in
service codebase to provide versioning.
aahframework.org/<library-name>.vX
points to appropriate tag versions; X
denotes version number and it's a stable release for production use.
It's recommended to use this way:
import "aahframework.org/aah.v0"
aah framework codebase is hosted on Github and Development happens on branch vX-unstable
for example: v0-unstable
, v1-unstable
, etc. and branch master
is tidy codebase of each release. Github tags
are stable and production ready.
aah framework doesn't provide explicit package management tool. Feel free to use your choice of tool.
Just to make sure, aah application is tested with glide and govendor package management tools. It is doing alright.
It is simple, go to your 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