Hey folks, Sorry this took so long, but Version 0.8.12 has been tagged on Github. As I told Dmitry, I was hesitant about tagging a new release with known crashes. But now that I've managed to solve all the crashes and weird errors I've encountered, as well as those from Issues and those posted to IRC, feel comfortable releasing this.
This is *mostly* an update for stability. A number of compile crashes, silent errors, cryptic error messages, broken tests, incompatibilities (between dependencies and the new OTP 17) have all been fixed, along with fixed translations in views, redirecting epgsql to David Welton's new unified epgsql project. Also, because relying on Github's release text thing is a little weird to me, I've added a CHANGELOG.md, which will update along with updates as they come in. https://github.com/ChicagoBoss/ChicagoBoss/blob/master/CHANGELOG.md Now that the stability issues are out of the way here, I'm feeling the itch for more tests, improving documentation. Among one of the more interesting fixes here is the ability to use rebar's update-deps command to update your app to a recent version. Keep in mind that the erlando dependency now relies on a ChicagoBoss fork (for the purposes of dependency conflict resolution), and as such 'update-deps' won't work immediately from that. The easy solution is to delete the deps/erlando directory before running `./rebar update-deps`, but that *should* work. Unfortunately, due to so many Erlang projects not having actual tags, a *lot* of the CB dependencies have been tied to specific tags (this is partially to help with git bisect, which is nearly impossible going far enough back to do so many dependencies pointing to {branch, master} or "HEAD" on semi-active projects). The *other* thing to be aware of is recent changes to ErlyDTL require a new version of rebar to compile. So make sure you copy the rebar executable from the ChicagoBoss repository into your app's root. Otherwise, you're going to get view compilation errors. Anyway, if you notice any new issues, go ahead and file new issues. Going forward, I'm going to push for a more rapid release cycle, and my main effort, as said when I joined the project, is stability and documentation - making CB more accessible to new users. Thanks for all your contributions, issues, IRC questions, and overall participation in the ChicagoBoss community. Let's continue the push to 1.0 :) Thanks, -- Jesse Gumm Owner, Sigma Star Systems 414.940.4866 || sigma-star.com || @jessegumm -- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/chicagoboss. To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/CAPTXyXd0cNP9uuWTJeRgWsoCZtq6Cpw2-xqihE2327rg5aNsgA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
