FYI, the servcecomb-kie repo is created, please feel free to send the PRs.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Apr 19, 2019 at 11:53 AM Xiaoliang Tian
wrote:
>
> servicecomb-kie
>
> Willem Jiang 于2019年4月18日周四 下午2:29写道：
>
> > Hi，
> >
> > I just did a quick search on the
discussed with @willem.jiang , because only
"Optional" is new feature, we can create 1.2.1 branch based on current
master(1.3.0-SNAPSHOT)
Willem Jiang 于2019年4月29日周一 上午9:14写道：
> I think we can start from 1.2.0 to avoid introduce new feature of 1.3.0.
>
> Willem Jiang
>
> Twitter: willemjiang
>
I think we can start from 1.2.0 to avoid introduce new feature of 1.3.0.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Apr 29, 2019 at 8:37 AM wjm wjm wrote:
>
> create 1.2.1 branch based on current master(1.3.0-SNAPSHOT)
> or create a new branch based on 1.2.0 and then cherry
Yeah, we could release 1.2.1 for these important patches.
As the 1.2.1 is a patch release, my suggestion is we back port the
patches of bug fixing into the 1.2.x branch, and then cut the release
candidate.
@wjm do you mind mark the JIRAs of the bug with the fix version of
1.2.1, then we could
there are some important fix for 1.2.0
- when create microservice meta failed, will destroy failed meta, but
leak to destroy related configuration resources, rarely happen, but it's a
leak problem.
- when log framework is log4j2, will leak some log4j2 marker object for
every
