On Friday, 08.06.2018 at 17:21, Martin Lucina wrote: > An update on this: > > After discussing with some of the core Mirage folks and others at robur, > we've come to the conclusion that it is better to release what we have now > rather than wait after the renaming is complete. > > So, the rough plan is to: > > 1. Decide on a "flag day" and rewrite Git history on master to sort out > the issue of my mis-attributed commits, > 2. Cut a "minimalist" Solo5 0.3.0 release of what we have now on master, > and subsequently the Mirage/Solo5 integration bits (as pointed to by the > OPAM repository in Solo5/opam-solo5). > 3. After that, continue with the renaming and restructuring of the > codebase as outlined in #172. > > I'll follow up in more detail on Monday.
And another update. Point 1 above is now moot as I have decided to just push an empty commit with "errata", referring to the mis-attributed commits in question. I will proceed with point 2 over the course of this week. Thanks, -mato
