Re: [HEADS UP] Migrating what remains of the Camel Confluence Site
Thank you too for your help with various docs and all the other polishing helps. On Fri, 9 Mar 2018 at 14:02, Andrea Cosentino wrote: > Finally we migrated all the remaining EIPs. So now we need to write a TOC > and go ahead with the new website. > > Thanks a lot to Onder for his great help! > > -- > Andrea Cosentino > -- > Apache Camel PMC Member > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Thursday, February 8, 2018, 2:27:33 PM GMT+1, Claus Ibsen < > claus.ib...@gmail.com> wrote: > > > > > > It does not create the adoc files itself, it just reports its missing. > So you add that file yourself. > > On Thu, Feb 8, 2018 at 2:23 PM, Onder SEZGIN > wrote: > > and some eips don't get created by those json files? > > eg: how convertBodyTo-eip.adoc is created? > > > > > > On Thu, Feb 8, 2018 at 4:10 PM, Onder SEZGIN > wrote: > > > >> Ok so far, code reading is going on for me before completing missing > eips. > >> As far as i can understand, camel-maven-package-plugin reads up all > .json > >> files under target/classes/org/apache/camel/model. > >> > >> I think something else under buildtools or tooling places those json > files. > >> Can somebody tell me how those are getting created, or at least could > you > >> guide me a starting point to read the code and complete missing eips? > >> > >> > >> On Wed, Feb 7, 2018 at 3:15 PM, Claus Ibsen > wrote: > >> > >>> Hi > >>> > >>> For the EIPs then you can see this table, and find the broken links > >>> for the missing docs > >>> https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc > >>> > >>> Or an alternative is to build camel-core, and in the end it reports a > >>> list of missing EIP docs. > >>> > >>> mvn install -P fastinstall > >>> > >>> Also some of the existing EIP doc pages could use some examples, as > >>> that helps end users to understand these EIPs better. We also added > >>> some EIPs in the new adoc that was not on the old site, eg > >>> convertBodyTo etc. > >>> > >>> Some of the DSL models from Camel is skipped for that readme page, but > >>> we could essentially if we wanted have an adoc page for every one, > >>> also those DSL types for configuring stuff, or those that refer to > >>> cross cutting functionality such as error handling etc. > >>> > >>> But lets start with getting the EIPs docs finished. > >>> > >>> > >>> On Wed, Feb 7, 2018 at 1:08 PM, Andrea Cosentino > >>> wrote: > >>> > I don't think there is an easy way, once we finish to migrate the > >>> remaining EIPs, we'll need to write a TOC of what we want in the > >>> documentation and then migrate only the confluence pages related to > the TOC. > >>> > > >>> > -- > >>> > Andrea Cosentino > >>> > -- > >>> > Apache Camel PMC Member > >>> > Apache Karaf Committer > >>> > Apache Servicemix PMC Member > >>> > Email: ancosen1...@yahoo.com > >>> > Twitter: @oscerd2 > >>> > Github: oscerd > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > On Wednesday, February 7, 2018, 1:05:03 PM GMT+1, Onder SEZGIN < > >>> ondersez...@gmail.com> wrote: > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > Hi, > >>> > > >>> > Considering, CAMEL-11497; > >>> > > >>> > I have generated adoc files from confluence export. > >>> > There are almost 900 adoc files. And also I've checkout exsiting adoc > >>> files > >>> > under my local git clone. > >>> > > >>> > :~/github/camel$ ls -ltrR | grep ".adoc" | wc -l > >>> > 872 > >>> > > >>> > I think the numbers are quite close. > >>> > > >>> > I think i can catch up with missing adoc files. > >>> > > >>> > As complete build to generated all adoc file takes quite a bit long > time > >>> > for my old computer, i am considering comparing all the adoc file > >>> generated > >>> > by cxf-web and complete build's result of adoc files. > >>> > > >>> > So i think i can write a quick small bash command to do such > comparison, > >>> > but the problem is that some adoc files in the repo and cxf-web's > export > >>> > does not match. > >>> > I think it is because of naming convention used to generate .adoc > file > >>> from > >>> > the repo. > >>> > > >>> > Is there an easy way to detect and compare both list to find out > missing > >>> > pieces from repo and the pieces existing in the confluence export. > >>> > > >>> > That will make comparing easier and add missing adoc files to > >>> repository. > >>> > > >>> > Thanks. > >>> > > >>> > Ex: > >>> > > >>> > :~/github/cxf-web/export/camel$ ls -l loop.adoc > >>> > -rw-rw-r-- 1 virt virt 5009 Şub 6 11:20 loop.adoc > >>> > > >>> > ~/github/camel/camel-core/src/main/docs/eips$ ls -l loop-eip.adoc > >>> > -rw-rw-r-- 1 onders onders 5786 Şub 6 11:58 loop-eip.adoc > >>> > > >>> > > >>> > On Tue, Feb 6, 2018 at 3:16 PM, Zoran Regvart > >>> wrote: > >>> > > >>> >> Hi Önder, > >>> >> gulp will do some of the work[1] to copy and transform existing > files. >
Re: [HEADS UP] Migrating what remains of the Camel Confluence Site
Awesome. Thanks ! Regards JB Le 9 mars 2018 à 12:02, à 12:02, Andrea Cosentino a écrit: >Finally we migrated all the remaining EIPs. So now we need to write a >TOC and go ahead with the new website. > >Thanks a lot to Onder for his great help! > >-- >Andrea Cosentino >-- >Apache Camel PMC Member >Apache Karaf Committer >Apache Servicemix PMC Member >Email: ancosen1...@yahoo.com >Twitter: @oscerd2 >Github: oscerd > > > > > > >On Thursday, February 8, 2018, 2:27:33 PM GMT+1, Claus Ibsen > wrote: > > > > > >It does not create the adoc files itself, it just reports its missing. >So you add that file yourself. > >On Thu, Feb 8, 2018 at 2:23 PM, Onder SEZGIN >wrote: >> and some eips don't get created by those json files? >> eg: how convertBodyTo-eip.adoc is created? >> >> >> On Thu, Feb 8, 2018 at 4:10 PM, Onder SEZGIN >wrote: >> >>> Ok so far, code reading is going on for me before completing missing >eips. >>> As far as i can understand, camel-maven-package-plugin reads up all >.json >>> files under target/classes/org/apache/camel/model. >>> >>> I think something else under buildtools or tooling places those json >files. >>> Can somebody tell me how those are getting created, or at least >could you >>> guide me a starting point to read the code and complete missing >eips? >>> >>> >>> On Wed, Feb 7, 2018 at 3:15 PM, Claus Ibsen >wrote: >>> Hi For the EIPs then you can see this table, and find the broken links for the missing docs >https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc Or an alternative is to build camel-core, and in the end it reports >a list of missing EIP docs. mvn install -P fastinstall Also some of the existing EIP doc pages could use some examples, as that helps end users to understand these EIPs better. We also added some EIPs in the new adoc that was not on the old site, eg convertBodyTo etc. Some of the DSL models from Camel is skipped for that readme page, >but we could essentially if we wanted have an adoc page for every one, also those DSL types for configuring stuff, or those that refer to cross cutting functionality such as error handling etc. But lets start with getting the EIPs docs finished. On Wed, Feb 7, 2018 at 1:08 PM, Andrea Cosentino wrote: > I don't think there is an easy way, once we finish to migrate the remaining EIPs, we'll need to write a TOC of what we want in the documentation and then migrate only the confluence pages related to >the TOC. > > -- > Andrea Cosentino > -- > Apache Camel PMC Member > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Wednesday, February 7, 2018, 1:05:03 PM GMT+1, Onder SEZGIN < ondersez...@gmail.com> wrote: > > > > > > Hi, > > Considering, CAMEL-11497; > > I have generated adoc files from confluence export. > There are almost 900 adoc files. And also I've checkout exsiting >adoc files > under my local git clone. > > :~/github/camel$ ls -ltrR | grep ".adoc" | wc -l > 872 > > I think the numbers are quite close. > > I think i can catch up with missing adoc files. > > As complete build to generated all adoc file takes quite a bit >long time > for my old computer, i am considering comparing all the adoc file generated > by cxf-web and complete build's result of adoc files. > > So i think i can write a quick small bash command to do such >comparison, > but the problem is that some adoc files in the repo and cxf-web's >export > does not match. > I think it is because of naming convention used to generate .adoc >file from > the repo. > > Is there an easy way to detect and compare both list to find out >missing > pieces from repo and the pieces existing in the confluence >export. > > That will make comparing easier and add missing adoc files to repository. > > Thanks. > > Ex: > > :~/github/cxf-web/export/camel$ ls -l loop.adoc > -rw-rw-r-- 1 virt virt 5009 Şub 6 11:20 loop.adoc > > ~/github/camel/camel-core/src/main/docs/eips$ ls -l loop-eip.adoc > -rw-rw-r-- 1 onders onders 5786 Şub 6 11:58 loop-eip.adoc > > > On Tue, Feb 6, 2018 at 3:16 PM, Zoran Regvart wrote: > >> Hi Önder, >> gulp will do some of the work[1] to copy and transform existing >files. >> I think the easiest way could be to create new ascii docs on the >> master and then rebase the website branch to pick those up, >> >> zoran >> >> [1] https://github.com/apache/cam
Re: [HEADS UP] Migrating what remains of the Camel Confluence Site
Finally we migrated all the remaining EIPs. So now we need to write a TOC and go ahead with the new website. Thanks a lot to Onder for his great help! -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, February 8, 2018, 2:27:33 PM GMT+1, Claus Ibsen wrote: It does not create the adoc files itself, it just reports its missing. So you add that file yourself. On Thu, Feb 8, 2018 at 2:23 PM, Onder SEZGIN wrote: > and some eips don't get created by those json files? > eg: how convertBodyTo-eip.adoc is created? > > > On Thu, Feb 8, 2018 at 4:10 PM, Onder SEZGIN wrote: > >> Ok so far, code reading is going on for me before completing missing eips. >> As far as i can understand, camel-maven-package-plugin reads up all .json >> files under target/classes/org/apache/camel/model. >> >> I think something else under buildtools or tooling places those json files. >> Can somebody tell me how those are getting created, or at least could you >> guide me a starting point to read the code and complete missing eips? >> >> >> On Wed, Feb 7, 2018 at 3:15 PM, Claus Ibsen wrote: >> >>> Hi >>> >>> For the EIPs then you can see this table, and find the broken links >>> for the missing docs >>> https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc >>> >>> Or an alternative is to build camel-core, and in the end it reports a >>> list of missing EIP docs. >>> >>> mvn install -P fastinstall >>> >>> Also some of the existing EIP doc pages could use some examples, as >>> that helps end users to understand these EIPs better. We also added >>> some EIPs in the new adoc that was not on the old site, eg >>> convertBodyTo etc. >>> >>> Some of the DSL models from Camel is skipped for that readme page, but >>> we could essentially if we wanted have an adoc page for every one, >>> also those DSL types for configuring stuff, or those that refer to >>> cross cutting functionality such as error handling etc. >>> >>> But lets start with getting the EIPs docs finished. >>> >>> >>> On Wed, Feb 7, 2018 at 1:08 PM, Andrea Cosentino >>> wrote: >>> > I don't think there is an easy way, once we finish to migrate the >>> remaining EIPs, we'll need to write a TOC of what we want in the >>> documentation and then migrate only the confluence pages related to the TOC. >>> > >>> > -- >>> > Andrea Cosentino >>> > -- >>> > Apache Camel PMC Member >>> > Apache Karaf Committer >>> > Apache Servicemix PMC Member >>> > Email: ancosen1...@yahoo.com >>> > Twitter: @oscerd2 >>> > Github: oscerd >>> > >>> > >>> > >>> > >>> > >>> > >>> > On Wednesday, February 7, 2018, 1:05:03 PM GMT+1, Onder SEZGIN < >>> ondersez...@gmail.com> wrote: >>> > >>> > >>> > >>> > >>> > >>> > Hi, >>> > >>> > Considering, CAMEL-11497; >>> > >>> > I have generated adoc files from confluence export. >>> > There are almost 900 adoc files. And also I've checkout exsiting adoc >>> files >>> > under my local git clone. >>> > >>> > :~/github/camel$ ls -ltrR | grep ".adoc" | wc -l >>> > 872 >>> > >>> > I think the numbers are quite close. >>> > >>> > I think i can catch up with missing adoc files. >>> > >>> > As complete build to generated all adoc file takes quite a bit long time >>> > for my old computer, i am considering comparing all the adoc file >>> generated >>> > by cxf-web and complete build's result of adoc files. >>> > >>> > So i think i can write a quick small bash command to do such comparison, >>> > but the problem is that some adoc files in the repo and cxf-web's export >>> > does not match. >>> > I think it is because of naming convention used to generate .adoc file >>> from >>> > the repo. >>> > >>> > Is there an easy way to detect and compare both list to find out missing >>> > pieces from repo and the pieces existing in the confluence export. >>> > >>> > That will make comparing easier and add missing adoc files to >>> repository. >>> > >>> > Thanks. >>> > >>> > Ex: >>> > >>> > :~/github/cxf-web/export/camel$ ls -l loop.adoc >>> > -rw-rw-r-- 1 virt virt 5009 Şub 6 11:20 loop.adoc >>> > >>> > ~/github/camel/camel-core/src/main/docs/eips$ ls -l loop-eip.adoc >>> > -rw-rw-r-- 1 onders onders 5786 Şub 6 11:58 loop-eip.adoc >>> > >>> > >>> > On Tue, Feb 6, 2018 at 3:16 PM, Zoran Regvart >>> wrote: >>> > >>> >> Hi Önder, >>> >> gulp will do some of the work[1] to copy and transform existing files. >>> >> I think the easiest way could be to create new ascii docs on the >>> >> master and then rebase the website branch to pick those up, >>> >> >>> >> zoran >>> >> >>> >> [1] https://github.com/apache/camel/blob/website/camel-website/ >>> gulpfile.js >>> >> >>> >> On Tue, Feb 6, 2018 at 10:11 AM, Onder SEZGIN >>> >> wrote: >>> >> > Hi, >>> >> > >>> >> > I have gone through the steps Andrea described and checked out >>> Zoran's >>> >> > branch. >>> >> > >>> >> > Now
[GitHub] camel pull request #2250: CAMEL-11497 - add rollback-eip considering transac...
Github user onderson closed the pull request at: https://github.com/apache/camel/pull/2250 ---
Re: News on front page about new website and documentation
Hi, I also want to help with it. best Bennet > On 9. Mar 2018, at 1:47 AM, Sascha Dirbach > wrote: > > Hi > > Am 06.03.2018 um 10:48 schrieb Claus Ibsen: >> Anyone wanna help with that? > > I would also be interested on helping. > > Is there already a channel to coordinate that work? > > Kind regards, > Sascha >
Re: Getting ready for Apache Camel 2.21 release
Hi Thanks Gregor, that sounds good. I put out the word on twitter about "last call" On Fri, Mar 9, 2018 at 9:50 AM, Gregor Zurowski wrote: > Hi Claus, > > I am not sure if I have any capacity to start this before Sunday. So please > take your time to finish your work. > > Thanks, > Gregor > > On Mar 9, 2018 9:15 AM, "Claus Ibsen" wrote: > >> Hi >> >> I have a bit more work on the camel-rabbitmq component I would like to >> get done before we cut the release. >> As I am traveling this morning I am not sure when I get a chance to do >> a bit of coding. >> But would have time later this afternoon. >> >> Gregor how is your timeline looking? Can you possible start the >> release procedure tomorrow? >> >> If anyone got a bit of time it would be nice to pre-test the >> 2.21.0-SNAPSHOT agains the source code for the CiA2 book. >> We usually do that against the RCs but would be better to catch them >> ahead of time if there is any issues. >> >> >> >> On Thu, Mar 8, 2018 at 8:13 AM, Claus Ibsen wrote: >> > Hi >> > >> > So the CI builds had 3 successfully builds recently >> > https://builds.apache.org/job/Camel/job/master/ >> > >> > The build #120 was hanging and I killed it, and it started a new build >> #121. >> > That build should have a fix that caused the previous builds to fail >> > with due to a recent cdi-pax upgrade. >> > >> > We have today and tomorrow morning to get the bits in, before we hand >> > it over to Gregor, to cut the release. >> > >> > >> > On Tue, Mar 6, 2018 at 11:04 AM, Andrea Cosentino >> wrote: >> >> Hello, >> >> >> >> Actually we have the SMX bundles release of February under vote. The >> bundles are here: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? >> projectId=12311206&version=12342774 >> >> >> >> I believe Saxon, gRPC and OkHttp 3.10 should be included in 2.21.0 (and >> others maybe, but with less importance), the vote should close soon, I >> should be able to update everything before Friday. >> >> >> >> >> >> >> >> >> >> -- >> >> Andrea Cosentino >> >> -- >> >> Apache Camel PMC Member >> >> Apache Karaf Committer >> >> Apache Servicemix PMC Member >> >> Email: ancosen1...@yahoo.com >> >> Twitter: @oscerd2 >> >> Github: oscerd >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Tuesday, March 6, 2018, 10:58:23 AM GMT+1, Claus Ibsen < >> claus.ib...@gmail.com> wrote: >> >> >> >> >> >> >> >> >> >> >> >> Hi >> >> >> >> So this week we are closing in on getting ready for cutting the Camel >> >> 2.21.0 release in the weekend. >> >> >> >> The CI server are doing many tests and we have improved and fixed some >> >> of its failures, and also found some flaky tests that we have >> >> disabled. >> >> https://builds.apache.org/job/Camel/job/master/ >> >> >> >> There are 10 JIRAs assigned for 2.21.0 and I will go over them >> >> https://issues.apache.org/jira/issues/?jql=project%20% >> 3D%20CAMEL%20AND%20fixVersion%20%3D%202.21.0%20AND% >> 20statusCategory%20%3D%20new >> >> >> >> Some of these will be moved to 2.22.0 or 2.21.1. >> >> >> >> Otherwise we should focus on bug fixes, smaller improvements, polish >> >> the docs, examples etc. >> >> >> >> >> >> Andrea is there any SMX bundle release we potentially are waiting for? >> >> >> >> >> >> >> >> On Sun, Mar 4, 2018 at 9:22 AM, Claus Ibsen >> wrote: >> >>> Hi >> >>> >> >>> On Sun, Mar 4, 2018 at 9:19 AM, Alex Dettinger >> wrote: >> Hi, >> >> Just a quick note that I had a successful build this night on my >> local >> machine too. >> >> >>> >> >>> Thanks for testing and reporting back. >> >>> >> >>> >> Alex >> >> On Wed, Feb 28, 2018 at 10:34 AM, Claus Ibsen >> wrote: >> >> > 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 > > >> > wrote: >> > > Hi >> > > >> > > We should start to close down and get ready for the expected Camel >> 2.21 >> > release. >> > > >> > > If
[GitHub] camel pull request #2250: CAMEL-11497 - add rollback-eip considering transac...
GitHub user onderson opened a pull request: https://github.com/apache/camel/pull/2250 CAMEL-11497 - add rollback-eip considering transactional-client.adoc ⦠â¦from export of current camel-web. Not sure if that would provide the right whole information about rollback-eip. Could you please review? You can merge this pull request into a Git repository by running: $ git pull https://github.com/onderson/camel CAMEL-11497 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2250.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2250 commit e4a1343a915ff24a7835a49bf5b56728b44356bf Author: Sezgin Date: 2018-03-09T07:59:10Z CAMEL-11497 - add rollback-eip considering transactional-client.adoc from export of current camel-web ---
Re: Getting ready for Apache Camel 2.21 release
Hi Claus, I am not sure if I have any capacity to start this before Sunday. So please take your time to finish your work. Thanks, Gregor On Mar 9, 2018 9:15 AM, "Claus Ibsen" wrote: > Hi > > I have a bit more work on the camel-rabbitmq component I would like to > get done before we cut the release. > As I am traveling this morning I am not sure when I get a chance to do > a bit of coding. > But would have time later this afternoon. > > Gregor how is your timeline looking? Can you possible start the > release procedure tomorrow? > > If anyone got a bit of time it would be nice to pre-test the > 2.21.0-SNAPSHOT agains the source code for the CiA2 book. > We usually do that against the RCs but would be better to catch them > ahead of time if there is any issues. > > > > On Thu, Mar 8, 2018 at 8:13 AM, Claus Ibsen wrote: > > Hi > > > > So the CI builds had 3 successfully builds recently > > https://builds.apache.org/job/Camel/job/master/ > > > > The build #120 was hanging and I killed it, and it started a new build > #121. > > That build should have a fix that caused the previous builds to fail > > with due to a recent cdi-pax upgrade. > > > > We have today and tomorrow morning to get the bits in, before we hand > > it over to Gregor, to cut the release. > > > > > > On Tue, Mar 6, 2018 at 11:04 AM, Andrea Cosentino > wrote: > >> Hello, > >> > >> Actually we have the SMX bundles release of February under vote. The > bundles are here: > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12311206&version=12342774 > >> > >> I believe Saxon, gRPC and OkHttp 3.10 should be included in 2.21.0 (and > others maybe, but with less importance), the vote should close soon, I > should be able to update everything before Friday. > >> > >> > >> > >> > >> -- > >> Andrea Cosentino > >> -- > >> Apache Camel PMC Member > >> Apache Karaf Committer > >> Apache Servicemix PMC Member > >> Email: ancosen1...@yahoo.com > >> Twitter: @oscerd2 > >> Github: oscerd > >> > >> > >> > >> > >> > >> > >> On Tuesday, March 6, 2018, 10:58:23 AM GMT+1, Claus Ibsen < > claus.ib...@gmail.com> wrote: > >> > >> > >> > >> > >> > >> Hi > >> > >> So this week we are closing in on getting ready for cutting the Camel > >> 2.21.0 release in the weekend. > >> > >> The CI server are doing many tests and we have improved and fixed some > >> of its failures, and also found some flaky tests that we have > >> disabled. > >> https://builds.apache.org/job/Camel/job/master/ > >> > >> There are 10 JIRAs assigned for 2.21.0 and I will go over them > >> https://issues.apache.org/jira/issues/?jql=project%20% > 3D%20CAMEL%20AND%20fixVersion%20%3D%202.21.0%20AND% > 20statusCategory%20%3D%20new > >> > >> Some of these will be moved to 2.22.0 or 2.21.1. > >> > >> Otherwise we should focus on bug fixes, smaller improvements, polish > >> the docs, examples etc. > >> > >> > >> Andrea is there any SMX bundle release we potentially are waiting for? > >> > >> > >> > >> On Sun, Mar 4, 2018 at 9:22 AM, Claus Ibsen > wrote: > >>> Hi > >>> > >>> On Sun, Mar 4, 2018 at 9:19 AM, Alex Dettinger > wrote: > Hi, > > Just a quick note that I had a successful build this night on my > local > machine too. > > >>> > >>> Thanks for testing and reporting back. > >>> > >>> > Alex > > On Wed, Feb 28, 2018 at 10:34 AM, Claus Ibsen > wrote: > > > 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 > > > 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
Re: Getting ready for Apache Camel 2.21 release
Hi I have a bit more work on the camel-rabbitmq component I would like to get done before we cut the release. As I am traveling this morning I am not sure when I get a chance to do a bit of coding. But would have time later this afternoon. Gregor how is your timeline looking? Can you possible start the release procedure tomorrow? If anyone got a bit of time it would be nice to pre-test the 2.21.0-SNAPSHOT agains the source code for the CiA2 book. We usually do that against the RCs but would be better to catch them ahead of time if there is any issues. On Thu, Mar 8, 2018 at 8:13 AM, Claus Ibsen wrote: > Hi > > So the CI builds had 3 successfully builds recently > https://builds.apache.org/job/Camel/job/master/ > > The build #120 was hanging and I killed it, and it started a new build #121. > That build should have a fix that caused the previous builds to fail > with due to a recent cdi-pax upgrade. > > We have today and tomorrow morning to get the bits in, before we hand > it over to Gregor, to cut the release. > > > On Tue, Mar 6, 2018 at 11:04 AM, Andrea Cosentino > wrote: >> Hello, >> >> Actually we have the SMX bundles release of February under vote. The bundles >> are here: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311206&version=12342774 >> >> I believe Saxon, gRPC and OkHttp 3.10 should be included in 2.21.0 (and >> others maybe, but with less importance), the vote should close soon, I >> should be able to update everything before Friday. >> >> >> >> >> -- >> Andrea Cosentino >> -- >> Apache Camel PMC Member >> Apache Karaf Committer >> Apache Servicemix PMC Member >> Email: ancosen1...@yahoo.com >> Twitter: @oscerd2 >> Github: oscerd >> >> >> >> >> >> >> On Tuesday, March 6, 2018, 10:58:23 AM GMT+1, Claus Ibsen >> wrote: >> >> >> >> >> >> Hi >> >> So this week we are closing in on getting ready for cutting the Camel >> 2.21.0 release in the weekend. >> >> The CI server are doing many tests and we have improved and fixed some >> of its failures, and also found some flaky tests that we have >> disabled. >> https://builds.apache.org/job/Camel/job/master/ >> >> There are 10 JIRAs assigned for 2.21.0 and I will go over them >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.21.0%20AND%20statusCategory%20%3D%20new >> >> Some of these will be moved to 2.22.0 or 2.21.1. >> >> Otherwise we should focus on bug fixes, smaller improvements, polish >> the docs, examples etc. >> >> >> Andrea is there any SMX bundle release we potentially are waiting for? >> >> >> >> On Sun, Mar 4, 2018 at 9:22 AM, Claus Ibsen wrote: >>> Hi >>> >>> On Sun, Mar 4, 2018 at 9:19 AM, Alex Dettinger >>> wrote: Hi, Just a quick note that I had a successful build this night on my local machine too. >>> >>> Thanks for testing and reporting back. >>> >>> Alex On Wed, Feb 28, 2018 at 10:34 AM, Claus Ibsen wrote: > 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 > 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% >
