I haven't used it and not sure it ticks all your boxes, but heard good things - Overview - Redmine[^]

No, I didn't make it that far. It was as if it wasn't there at all as far as Disk Utility was concerned.

Thanks for the info. The kit I bought (OWC 1.0TB Aura Pro X2) had an enclosure but the enclosure only supported the old (current) drive and not the new one. I had put the new ssd in the machine and attempted to set it up using disk utility in recovery mode (or whatever that mode is) but it wouldn't recognize the new drive. After a few attempts I decided to return the drive and put the return funds toward an eventual new machine as I'm coming up on 7 years with the laptop. Enjoy your spruced up machine!

At first, I couldn't even get the the mac to recognize and mount the SSD so I could clone, but I finally got that working. How did you get this working? I got hung up here doing an iFixit SSD upgrade to my macbook pro and decided to pass on the upgrade.

Go for 1920x1200. The bit of extra height is handy.

Lots of good ideas here, but depending on your situation, preferences and comfort level you could consider offering a different approach: - Make an outline (mental or otherwise) of all the information you want to convey. - Set up meeting(s) with the staff who will take over your projects. - Present the material. - THEY create the documentation. - You can give the documentation a once over afterwards if you are inclined. In addition to saving you the agony of writing documentation, the company gets the benefit of having remaining staff become familiar with your projects before you are out the door.

I think this is the heart of your issue. It's not the tools but how you are using them. - All changes should be checked in before they go to test. - Test (and Prod) should be always be built from some specific SVN revision. - You probably could use a branch for what's in prod where quick fixes can go and another branch or trunk for the next big release. You'd have to merge prod fixes to the release code. And you might want a dev server to "test" the bigger changes on. Something like that...

"requirements come from the client" - sounds like you have a great client, sometimes you have to guess at what they want :)