We will need to figure out what changes should be backported to 2.0.X and create a single ticket in jira (backport x,y) so we have that work logged adequately comes time when something is accidentally broken we will know where the change came from.
As you can see from the commit log I’m trying to squash entire issues into single commits so the commit history is easier to understand moving forward. On Thu, Apr 23, 2020 at 10:02 AM Emmanuel Lécharny <[email protected]> wrote: > Hi ! > > > we have a few issues and improvements that would deserve a release in > both the 2.0 and 2.1 branches. Jonathan has done a JIRA review lately. > > I can probably find a few hours here and the in the coming week (and > week-end) to get some work done and ultimately cut the release (although > squeezing those hours in a busy day job agenda and a more than busy > family constraints - the 3 years old has to be taken care of now that > she can't go to school anymore - is kind of tough) > > wdyt ? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
