Hi We have now moved some JIRA tickets to 2.22 so the roadmap for 2.21 is shorter and also what we would actually focus on. That said if there is something you really would like to get in 2.21 that was moved to 2.22 then say so, and work on it. We have this week to work on improvements, new features etc. And then next week we should focus mostly on bug fixes, polishing, testing, and fix up docs etc. And then Gregor will cut the release in the weekend (eg around March 9-11th)
I ran tests overnight and found 3 issues which I have logged and fixed this morning. So all tests pass on my laptop, but would also be good to have tested on other platforms. The CI servers are temporary disabled and we are migrating to Jenkins Pipeline to make the CI server jobs more faster and less resource intensive. There is another talk on @dev about this. On Mon, Feb 26, 2018 at 10:10 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > We should start to close down and get ready for the expected Camel 2.21 > release. > > If you have any new functionality then its last call to get that > implemented and committed. > > There are currently 61 tickets [1] assigned to 2.21.0 release which is > too much. I will go over them and you are of course also welcome to > take a look, and move tickets to 2.21.1 or 2.22.0. > > I think we need to use this week to get the last tickets resolved, > bugs fixed, stable the CI tests and what else, and then we can touch > base in start of next week to plan for cutting the 2.21 RC builds. > Gregor do you have time for example from next week / next weekend to > cut the RC? > > > [1] - > https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.21.0%20AND%20statusCategory%20%3D%20new > > > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
