Version 1.3 has been submitted and should be in the App Catalog soon.
Bugs
- Load More showing gaps in home timeline
- TweetPhoto: upload and in-app photo viewing restored
- can remove account if username changed on Twitter
- RT's now show timestamp of RT, not original tweet
- webOS 1.4 issues are fixed (for upcoming webOS update)
Features and Changes
- specify RT style: old, new or prompt (per tweet) tions
Sarah Allen approached Pivotal back in December wanting to host a Palm webOS hack session. She knew that there was curiosity among the San Francisco Rails community about the platform and wanted to have a hands-on coding day where they could learn.
One of our clients recently presented a demo of a new web application we built for them to a potential customer. This customer happens to be a large corporation who enforces, as large corporations will do, the use of IE6 on all of their corporate machines. When we found this out we feared the worst: many tortuous hours of work twisting the fabric of good sense and CSS standards to eke a sensibly rendered site out of the maw of the IE6 beast.
Imagine our relief and surprise when the head of corporate IT for the potential customer not only decided that the application was essential for the organization, but that to support it they would eliminate the use of IE6 on their corporate machines.
Mark one in the win column for the good guys.
Ajaxed pages frequently need to update many parts of the page within ajax callbacks. Here I'll outline how we use jQuery and Rails do this on Mavenlink. Our approach encodes behavior declaratively in markup and minimizes client-side logic.
This Pivotal Tracker update allows you to see GitHub or other SCM commits in your stories, your project activity in your team's Campfire chat room, and introduces the first wave of integrations with other bug/issue tracking applications including JIRA, Lighthouse, and Satisfaction.
There is also a new version of the API (V3), with support for moving stories, file attachments, as well as activity web hooks. The first version of the API (V1) is no longer available.
Continue reading for more details on what's new.
Now that I'm starting to use DelayedJob to perform jobs in the future in my Heroku Sinatra app, its important that they happen at the scheduled time. But unless you pay attention, you'll find that times get mysteriously changed -- in my case, since I'm in San Francisco in the wintertime, by +/-8 hours -- which means that some conversion to or from UTC is being attempted, but it's only working halfway.
Trying to keep a handle on which libraries are attempting, and which are failing, to convert times is a losing battle, so I'm trying to do the right thing and save all my times in the database in UTC, and convert them to and from the user's local time as close to the UI as possible. Unfortunately, a variety of gotchas in Ruby and ActiveRecord and PostgreSQL makes this trickier than it should be. Here's a little catalog of my workarounds.
We are planing to do a Tracker upgrade (with new features including API V3 and some integrations) tomorrow, Saturday Jan 23, at 5:30pm PST. We expect the upgrade to take under two hours.
Also, Engine Yard will be performing some maintenance and upgrades our hardware cluster on Sunday, from 10:00am to 1:00pm PST.
Sorry for the inconvenience. If you need access to your project data during the downtime, we recommend you export your project(s) beforehand:
http://www.pivotaltracker.com/help#howcaniexportstoriesfrommyproject
Also, as a reminder, the first version of the API (V1) will be disabled as part of tomorrow's release. More information on that here.
If you've been looking for a way to turn emails into Tracker stories, take a look at tgethr. It's an email collaboration service for groups, and it now integrates with Pivotal Tracker.
Read about it in this tgethr blog post.
Interesting Things
- Caveat Experior: Pivot Mike found a bug in Webrat in Selenium mode when using #click_link. He filed a ticket at Lighthouse.
- Caveat Coracinatus: Attention to those "Riding the Toad" (I didn't make this up - it's on Hoptoad's homepage): the Hoptoad Notifier gem that was released on Jan 20, v2.1.1, is missing a file. Make sure to update to the latest version, v2.1.2 in order for this gem to work. You should be on the latest gem anyway because there's a deprecation in the session code that will stop working in February. If you have a site that's not actively being developed you will need to update the gem & redeploy your app in order to continue to receive exception notifications.
If you notice that your classes have more than one responsibility, you can easily split them up into multiple, more cohesive classes using Ruby's DelegateClass.