Releases: vmware-archive/postfacto
2.5.0
💡 We now have an optional session timeout so users who've logged into Retros using a password don't stay logged in for, like, forever. This will help all the shared computer folks who would leave the Retro but forget to hit that sign out button. Google OAuth sessions will still stay logged in until we also make that change there.
🛠 You can also customize the session time for the above feature using the SESSION_TIME env variable. More in the docs! #RTFM.
🚨 Redeploying will know invalidate any existing sessions of Postfacto. We'll look to smooth this out in the future.
🛠 You can now deploy to Heroku! Thanks for putting the work in @mjstallard. You're our fav ❤️.
💡 Password field now (finally) automatically focuses when you hit the login page for a Retro. Thanks @butzopower.
🛠 We upgraded a bunch of dependencies for the application including some big dogs such as Rails and JQuery.
🛠 You'll notice we've removed the Concourse pipelines from our package. This was getting hard to maintain and didn't seem to be widely used. Happy to hear dissent on this!
🐞 Trying to use Postfacto with a non password protected Redis will now work. If you're doing this: we really hope you know what you're doing.
Issues/PRs included in release: https://github.com/pivotal/postfacto/milestone/7?closed=1
2.4.2
🛠 Deploy scripts (deploy.sh) are now easier to run from wherever you want on your computer. Have fun with that! Thanks @Kehrlann!
🛠 We need a bigger smaller boat! Postfacto's frontend (web) will now only use 64MB of memory instead of 1GB (as it was defaulting to before).
Issues/PRs included in release: https://github.com/pivotal/postfacto/milestone/6?closed=1
2.4.1
🛠 Deployment is now focused around downloading a package that can be installed on PCF/PWS without any build steps. We'll include a package with each release as an attachment. If you've been Concours-ing: remain calm and carry on. We're still including pipelines in the package.
Issues/PRs included in release: https://github.com/pivotal/postfacto/milestone/5?closed=1
2.4.0
💡 Always wanted a robot to facilitate your retro? Well your dream has come true! Pressing the right arrow on your keyboard will now transition to the next retro item for you. Thanks for this @crswty.
💡 If you're like @crswty and you need to add an Item or Action Item with multiple lines you can now do that by hitting Shift + Enter while you're adding one.
🛠 You can now enable analytics if you'd like to help us learn about how you're using Postfacto and about how we could make it even better.
Issues/PRs included in release: https://github.com/pivotal/postfacto/milestone/4?closed=1
2.3.1
2.3.0
💡 You can now let users sign up using their Google Account so they can create Retros themselves. You can of course not do this and remain a (benevolent) dictator of your Postfacto. This feature comes courtesy of @leungandrew. Thanks!
🛠 You no longer need PostgreSQL or MySQL for local development. Say hello to SQLite!
Issues/PRs included in release: https://github.com/pivotal/postfacto/milestone/3?closed=1
2.2.0
💡 Retros created in the admin dashboard are now private by default.
💡 Retros can be deleted from the admin dashboard.
🛠 Example deployment for PCF available in deployment/pcf.
🛠 API no longer requires a specific Ruby buildpack to work (we'll get to the Web npm problems I promise).
🚨 We've changed how we do authentication so users will have to log back in after you've deployed this version.
Issues/PRs included in release: https://github.com/pivotal/postfacto/milestone/2?closed=1
2.1.0
💡 Retro owners can be changed from the Admin dashboard
💡 Now works with both Pivotal Redis and Redis Cloud services
🚨 Websockets port is now configurable (if you're running on PWS make sure to set to 4443 like the example deployment in deployment/pws)
Issues/PRs included in release: https://github.com/pivotal/postfacto/milestone/1?closed=1
From now on we'll announce new releases both here and via our mailing list.