Evergreen Status

The current goal is a Spring 2018 release of Evergreen 1.0. Which is rather ambitious, I know, and I wouldn’t be shocked if it was Spring 2019. But that’s the goal.

The build is currently broken, has been broken for months, and will continue as broken for at least another few weeks.

Here’s the scoop: I decided to do syncing in 1.0. It will probably be just one system at first (most likely FeedBin, since that’s what I use) — but this meant looking at the data and database level and figuring out what’s needed to make it usable when syncing. I’m in the middle of making the needed changes.

(Originally each syncing system was going to have its own database code, but I realized that that would be foolish.)

And, because I’m such a weird database-code-loving freak, I’m not using Core Data. (Total dummy, me. Don’t tell me.) An example is DatabaseLookupTable.swift, which manages relationships.

* * *

Progress is slow, since I don’t get to work on it every day, and even when I do it’s often just for half an hour. There are occasional days where I get a few hours. But, except when I’m on vacation, progress is steady — and that’s how you get things done. (It helps to be obsessed.)

(Frontier, meanwhile, is on the back burner — I picked Evergreen to ship first just because it was further along. I’ll get back to it.)

22 Aug 2017

Archive