Stefan Kristiansson
2014-12-13 21:07:41 UTC
As the thumb rule for new mor1kx releases is that we do them when the
development branch starts to deviate enough from the current release branch.
Or in other words, when we got enough exciting stuff merged into master.
With all the multicore stuff merged in, I felt we're at such a point now.
There's a bunch of other interesting things in there apart from multicore
go check out the logs to see for yourselfs.
To (once again) put the versioning system we have for mor1kx into print,
our development branch (master branch) always carries the minor number .0,
which makes all official first releases carry the minor number .1.
So, this means that the master branch now has moved on to carry the version
number 4.0.
Stefan
development branch starts to deviate enough from the current release branch.
Or in other words, when we got enough exciting stuff merged into master.
With all the multicore stuff merged in, I felt we're at such a point now.
There's a bunch of other interesting things in there apart from multicore
go check out the logs to see for yourselfs.
To (once again) put the versioning system we have for mor1kx into print,
our development branch (master branch) always carries the minor number .0,
which makes all official first releases carry the minor number .1.
So, this means that the master branch now has moved on to carry the version
number 4.0.
Stefan