Thanks a lot for your time Gregor
Il giorno ven 21 feb 2020 alle ore 08:40 Gregor Zurowski <
gre...@list.zurowski.org> ha scritto:
> I found the issue in the meantime and fixed it on the release branch:
> https://github.com/apache/camel-spring-boot/commit/e354d5af
>
> I am moving forward now and
I found the issue in the meantime and fixed it on the release branch:
https://github.com/apache/camel-spring-boot/commit/e354d5af
I am moving forward now and hope to release Camel Spring Boot 3.1.0
without further issues.
Thanks Andrea for your support!
On Thu, Feb 20, 2020 at 7:39 PM Gregor Zur
Hi Everyone:
After creating the Camel 3.1.0 release, I've attempted to create the
Camel Spring Boot 3.1.0 release, but ran into the following issue:
When running a dry run for release:prepare, I am getting the following error:
[INFO] --
Yeah, perfect.
Il giorno gio 20 feb 2020 alle ore 17:24 Gregor Zurowski <
gre...@list.zurowski.org> ha scritto:
> OK, sure. With every new major/minor release, I usually create a new
> "camel-MAJOR.MINOR.x" branch anyway. And for the actual release I
> create another branch "release/camel-MAJOR.M
OK, sure. With every new major/minor release, I usually create a new
"camel-MAJOR.MINOR.x" branch anyway. And for the actual release I
create another branch "release/camel-MAJOR.MINOR.PATCH". I would
apply corresponding branches for Camel Spring Boot.
I believe that should be sufficient?
On Thu,
I'm talking about the camel-spring-boot repository.
Suppose you cut an RC for camel-3.1.0, and after that someone push on
master. The gh action syncing master camel and camel-sb could open a PR on
Camel-spring-boot with alignments or someone may regen the
camel-spring-boot project with the latest
I've finished with Camel 3.1.0 and will now proceed with Camel Spring Boot.
What do you mean by "we should create a branch with the current
history"? Are you talking about the Camel repository or the Camel
Spring Boot repository? And what history are you referring to?
Thanks in advance,
Gregor
O
Probably we should create a branch with the current history, to avoid
mixing up the master with the master branch in camel-sb
Il giorno gio 20 feb 2020 alle ore 13:38 Andrea Cosentino
ha scritto:
> Hello Gregor,
>
> are you cutting also the camel-spring-boot release already?
>
> Il giorno gio 2
Hello Gregor,
are you cutting also the camel-spring-boot release already?
Il giorno gio 20 feb 2020 alle ore 06:30 Claus Ibsen
ha scritto:
> Hi Gregor
>
> The memory leaks should have been fixed now. The code base should be
> good for the release.
>
> On Wed, Feb 19, 2020 at 11:41 PM Gregor Zur
Thank you, I see that this issue has been labeled as gsoc2020. So I would
like to get some suggestions for references inorder to learn about the
project scope and so on. And also I hope to give some contributions on easy
fix issues from this weekend onwards.
Thank you.😊😊
On Sat, 25 Jan 2020, 21:54
10 matches
Mail list logo