karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Lilja <mindcoo...@gmail.com>
Subject Re: Merry Christmas & releases on the way
Date Wed, 25 Dec 2019 17:13:33 GMT
Thanks for the update, JB!

Will KARAF-6480 [1] and KARAF-6514 [2] make it into 4.2.8?

[1] https://issues.apache.org/jira/browse/KARAF-6480
[2] https://issues.apache.org/jira/browse/KARAF-6514

- Eric L

On Wed, Dec 25, 2019 at 10:13 AM Jean-Baptiste Onofré <jb@nanthrax.net>
wrote:

> Hi guys,
>
> on behalf of the Karaf team, I wish a Merry Christmas to the whole Karaf
> community.
>
> Let me use this mail to give you an update about releases:
> - Karaf 4.2.8 is planned before the end of this year (this week or early
> beginning of next week).
> - I do my best to cut 4.3.0.RC1 next week, but it's possible that I will
> cut the release first week of January (depending how fast I can be on
> 4.2.8 preparation).
> - Decanter 2.3.0 preparation moved well, but I have to release Karaf
> 4.2.8 first (as I have dependency to KarafTestSupport 4.2.8 for Decanter
> itests).
>
> I keep you posted !
>
> Again, Merry Christmas and enjoy time with family and friends.
>
> Regards
> JB
>
> On 11/10/2019 07:31, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > I've almost finished the refactoring of Cave for Cave 4.2.0 release:
> >
> > https://github.com/jbonofre/karaf-cave/tree/REFACTORING
> >
> > I'm polishing a bit this morning and merge to master later today.
> > I will prepare the Cave 4.2.0 during the week end.
> >
> > On the other hand, I moved forward on Karaf master heading to 4.3.0.RC1.
> > I should be able to push a first RC (RC1) beginning on next week.
> >
> > Meantime, I also moved forward on Decanter 2.3.0 preparation with new
> > improvements, fixes, etc.
> > The target is to submit this release in couple of weeks.
> >
> > Stay tuned !
> >
> > Regards
> > JB
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message