Right, so fork a 0.4 branch so that master can head towards a 0.5 release. Sounds good.
On Sat, 1 Jul 2017, at 01:40 PM, Evan Hughes wrote: > Well ATM we don't have a specific branch situation, so it's more about > creating a 0.4.# branch to preserve the past and allow us to fix the bugs > in that release. Because I believe we still wanted to do a release > soonish. > > On 1 Jul 2017 10:12 PM, "Upayavira" <u...@odoko.co.uk> wrote: > > > Presumably the time to do that would be when making a 0.5.0 release, no? > > :-) > > > > On Sat, 1 Jul 2017, at 07:41 AM, Evan Hughes wrote: > > > Hello All, > > > > > > wanting to gauge community feedback and feedback from the committers on > > > the > > > proposal of us bumping to version 0.5. I suggest we do this as I've been > > > working on "refacing" the project to look fresher and changing the > > > direction of the project to offer a generic back end server with a full > > > rest API. > > > > > > Will submit a pull request in the next few days which will have most of > > > the > > > new front face of the project started. > > > > > > ~ Evan > >
