v0.12 Release

[brendensoares]

No description provided.

[ghost]

@brendensoares Don't forget to include in release notes info on how to upgrade to v0.12. Looks like testing package is the only breaking change. So, users will have to update import paths of TestSuite type in files of tests directory.

• Old version:

package tests

import "github.com/revel/revel"

type AppTest struct {
    revel.TestSuite
}

• Required change:

package tests

import "github.com/revel/revel/testing"

type AppTest struct {
    testing.TestSuite
}

Apart from that everything works for my not-so-small application as expected, nothing is broken, its tests are passed.

---

And we also need to update README && not include https://github.com/revel/revel/blob/develop/.travis.yml#L8 to master.

[brendensoares]

@AnonX I noted the new import path. Also updated the README.md and switched the TravisCI branch to master.

We need to figure out a clean way to switch the Travis branch during release. For now, we'll just have to switch it back to develop after the release. Any better ideas?

[ghost]

@brendensoares We didn't update version.go: https://github.com/revel/revel/blob/master/version.go#L5

I'll let you know when I come up with a better idea.

[brendensoares]

@AnonX Should it be 0.12.0 or 0.12.0rc or what?

[notzippy]

@brendensoares I would go with all numeric 0.12.0

[ghost]

@brendensoares I thought v0.12.0dev meant it was develop branch. Well, if it didn't and dev part is intentional meaning revel is not stable then it's OK (although, I think v0 means exactly that without any suffixes). But what BUILD_DATE means? https://github.com/revel/revel/blob/master/version.go#L7 Why is it Jan 19, 2015?

[brendensoares]

@AnonX I agree that v0 means we've yet to reach the desired foundational features.

@notzippy I'm good with plain 0.12.0, but we may want to discuss a release candidate workflow to make releases more often as @pedromorgan has recently asked.

[brendensoares]

@AnonX BUILD_DATE refers to date of release in my mind. Thoughts? I've updated both date and version number now.