I have merged issue-#13 into master.
Folks, this is a historic moment.
We have agreed on the first bug fix that will go into the next release.
The bug fix has been merged into master and the build engine has
built a new unstable release.
"A small step for a build engine but a giant leap for BlackBox."
The build engine has created the new release available under
http://blackboxframework.org/unstable/m ... a1.006.zip.
Why did the build engine create a new release?
Because there was a commit to one of the branches, it was master in this example.
Merging a pull request in Git is also a commit, i.e. a new revision is created.
Why did the build engine output the new release in folder .../unstable/master?
Because it is not a final release as indicated by the current value of the file
appbuild/AppVersion.txt. This is set to '1.7-a1', which means alpha 1, or in other
words: the first round of working on the 1.7 alpha release. An alpha release means
that it is not feature complete, it is been actively worked on, it is primarily intended for
internal (Center) testing.
The build engine put the output into sub-folder master because this is the
name of the branch the commit happened in.
What is 006?
This is the build number, which is a global number incremented per build.
This number guarantees that the output of the build engine always uses a unique file name.
More details of the build engine and the development process can be found in our Wiki.
Last but not least I would like to emphasize that this bug fix was a nice example for synergy
that can happen in a community. The original bug fix was already quite clean
but has been improved by Chris in a remarkable way.
- Josef