Thanks for sharing! Got an answer to my question about updates there in the FAQ:
> How exactly does the two years work?
> The two year timeframe applies to each software version that is made available. Methods of making software available include pushing a Git commit, publishing a package to a repository, or mailing out a CD in a tin. For example, one could clone a repo, run git checkout `git rev-list -n 1 --before="2 years ago" master`, and—if LICENSE.md is FSL—use that version under MIT or Apache 2.0.
So the key is to download the source for each version you use and record the date and the current license text. Also, use the oldest version you're comfortable with since it converts the soonest. I'm thinking for down the road when new releases are under a different (even commercial) license and the pull the source for old versions. Then cost starts to go up a lot. Not saying it will, but I hope the software is successful but that sometimes leads to bad things for customers.
> How exactly does the two years work?
> The two year timeframe applies to each software version that is made available. Methods of making software available include pushing a Git commit, publishing a package to a repository, or mailing out a CD in a tin. For example, one could clone a repo, run git checkout `git rev-list -n 1 --before="2 years ago" master`, and—if LICENSE.md is FSL—use that version under MIT or Apache 2.0.