As I recall there wasn't an abundance of notice of Pivotal Tracker's sunset, but I did kind of expect someone to come up with a more 1:1 open-source replacement with a one-step migration tool.
We looked at Linear and other options but ultimately ended up going with Shortcut. We wrote our own small migration script and moved over the old Pivotal IDs to keep as much historical context as we could. Shortcut's been a good tool overall, though I preferred Pivotal's Goldilocks level of compactness as far as the UI was concerned, as well as the general design.
Pivotal's API was tidy and integrated nicely into our development process. We have some git aliases such as `git start <branch>` where the branch name will end with a story ID by convention. The alias would do the work of creating the branch, setting the remote to the dev's fork of our repo, marking the story as started, and assigning the dev as the owner. It saved a lot of manual steps, so thank you for your involvement in the project which allowed such a nice workflow!
Hah, wow. A post with an ID under 10k. Meanwhile this one is over 47M.
I didn't realize I've been reading HN nearly its whole existence. For all my complaining about what's happened to the internet since those days, HN has managed to stay high quality without compromising.
> Maybe I don't hang out with the trust fund crowd enough
I'm not sure that's a fair characterization of people taking a gap year, especially people in tech. The industry pays well relatively early and there is a surplus of jobs. If you keep your expenses low relative to your salary, don't let your lifestyle inflate beyond your means, and are fortunate enough not to be burdened with debt, health problems, or other large expenses, a gap year seems completely doable.
I think failure to save money is by far the most likely reason sabbaticals are uncommon, though I've been told by hiring managers they're more common in tech than you'd think. There's also probably some stigma against being unemployed, especially in professional circles, as well as fear of the dreaded "resume gap." As far as I can tell, that concern is fairly overblown for those in tech as well.
We looked at Linear and other options but ultimately ended up going with Shortcut. We wrote our own small migration script and moved over the old Pivotal IDs to keep as much historical context as we could. Shortcut's been a good tool overall, though I preferred Pivotal's Goldilocks level of compactness as far as the UI was concerned, as well as the general design.
Pivotal's API was tidy and integrated nicely into our development process. We have some git aliases such as `git start <branch>` where the branch name will end with a story ID by convention. The alias would do the work of creating the branch, setting the remote to the dev's fork of our repo, marking the story as started, and assigning the dev as the owner. It saved a lot of manual steps, so thank you for your involvement in the project which allowed such a nice workflow!