Versioning and Package Management
aah framework release versions as per Semantic Versioning.
aah commitment to provide stable release of framework and it’s libraries. aah 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.
High Level Info
aah framework codebase is hosted on Github and Development happens on branch
vX-unstable for example:
v1-unstable, etc. and branch
master is tidy codebase of each release. Github
tags are stable and production ready.
aah highly recommends you to use your choice of package management tool and vendorize your application dependencies. Beside that aah framework also provides versioned release too, if you’re just using
Just to make sure, I have tested aah application with
govendor package management tools. It is doing alright.
How do I use it?
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