Hi Thierry,
I’am also a friend of a more framework like approach, at least as a service
developer.
And your ideas with using Java annotations sounds also nice and promising (and
remember me a little bit at the Java annotation PoC in Olingo v2 and
OLINGO-129).
But I also think that for Olingo 4.
Hi,
for Olingo V2 there are actual two issues (OLINGO-710 and OLINGO-689) which
were fixed
but release of them could cause an adjustment in an actual service
implementation.
For OLINGO-689 the EdmNamed validation was fixed but now invalid property names
will lead to a validation exception.
For
Hi,
a while ago I suggested to release Olingo V2 version 2.0.5
because that the fix of the two issues (OLINGO-710 and OLINGO-689)
could cause a minor adjustment in an actual service implementation [1].
In the meanwhile there were other fixes especially for the JPA processor
IMHO those bugfixes ma
Hello Dave,
one question, do you use Olingo V2 or V4 or both?
For Olingo V4 there exists currently no way to change the used XMLInputFactory
in the „ODataXmlDeserializer"
private static final XMLInputFactory FACTORY = new InputFactoryImpl();
For Olingo V2 you can set the „System Propert
change the FACTORY from explicitly depending on aalto-xml to
> using XMLInputFactory.newInstance()?
>
> If so I will gladly create a JIRA and work on a patch to contribute back.
>
> Thanks
>
> David
>
> -Original Message-
> From: mibo [mailto:m...@apache.org]
>
will any
> stax library work?
>
> In any case I'll put in a JIRA issue and provide a patch/pull request via
> github.
>
> Thanks
>
> Dave
>
> -Original Message-
> From: mibo [mailto:m...@apache.org]
> Sent: Friday, October 09, 2015 12:53 PM
>
Hi all,
to put my „two cents“ in.
I totally agree that a release must not contain critical bugs in the core parts
of the library.
Accordingly we should clearly separate between the „extension“ parts and the
„core“ parts.
Furthermore the suggestion of Ramesh with different development phases so
Hi,
from my side a +1 after our discussion about the release process ;o)
Only suggestion/adaption to below is, that we should try to change the default
priority for a new created JIRA issue to be not „major“.
IMHO the default should be between „major“ and „minor“, however this does not
exists
Hi,
from my side a „+1“ for preparation of next release and Christian as release
manager.
Before Friday I will check my assigned issues and fix or postpone them to
V4.2.0.
Best Regards,
Michael
> On Dec 15, 2015, at 3:03 PM, Amend, Christian wrote:
>
>
> Hi,
>
>
> The release date for
Hi,
>From my side the decision to replace the ANTLR based parser with an own
>implementation was good and it is nice to see the result on the feature branch.
After a look into I give a „+1“ for merge the feature branch
(OLINGO-834_Filter_Parser
) into the master.
Best Regards,
Michael
Hi all,
During work on olingo-832 I realized that the „getEntities“ method in the
„org.apache.olingo.commons.api.data.EntityCollection“ return the list of
entities directly (instead of an unmodifiable List).
IMHO the best practice for List handling is to return only unmodifiable Lists
and
Hi all,
Thanks for the hint and the clarification ;o)
In further announce mails we will not enclose links with braces,
so that there will be no misinterpreted or wrongly converted links.
I hope we have some (important) announcement in the near future
so that we can see that the links then a
Hi all,
based on the good discussions, decision and that there was no objection about
https://issues.apache.org/jira/browse/OLINGO-856.
I would merge that issue from its feature branch into the master (so that it
will be included in next release [4.2.0]).
Best Regards, Michael
PS: I wrote this
Hi all,
IMHO with the NOTICES and LICENSE added by Christian and that the „Streaming
API for XML“ is added as binary (JAR) we are align with the legal terms defined
by Apache: http://www.apache.org/legal/resolved.html#category-b
Other Apache projects also include the „Streaming API for XML“ w
Hi all,
I take a look into the release and see that the „spring-extension“ is missing
as RC01 to download [1] and on the master [2].
Based on that in the spring extension was no code change between 2.0.6 and
2.0.7 I’am totally fine with doing the release and directly set the version in
the s
Hi all,
I also agree with the 3/4 weeks from beta release.
Furthermore I will check my open JIRA issues and try to solve (or postpone)
them ;o)
Best Regards, Michael
Am 28. Juli 2016 um 16:19:49, Ramesh Reddy (rare...@redhat.com) schrieb:
No I am not actively looking at any development. Want
Hi all,
from my side I have currently no open issues/features for the upcoming release.
So feel free for building the first RC ;o)
Best Regards, Michael
Am 6. September 2016 um 16:03:30, Ramesh Reddy (rare...@redhat.com) schrieb:
we are working on OLINGO-1009 and hopefully finish this week, s
[x] +1 Release this package as Apache Olingo 4.3.0
Best Regards, Michael
Am 15. September 2016 um 15:25:01, Amend, Christian (christian.am...@sap.com)
schrieb:
Hi,
This is a vote on the Apache Olingo 4.3.0 release. The vote will be open for 72
hours and passes if no vote is (-1). Since th
IMHO I also think we should keep the barrier for further contributors (and
contributions) to the JPA extension low.
Hence using a GitHub repository as starting point could be a good decision.
This way contributing and building the first releases (alpha, beta, whatever…)
are completely independent
Hi all,
based on the good discussions, decision and that there was no objection a=
bout=C2=A0https://issues.apache.org/jira/browse/OLINGO-1018.
I would merge that issue from its feature branch into the master.
The reason for the lazy consensus mail is that the improvement contains a=
minor change
Hi All,
From my side +1 for building a new patch release.
As preparation I resolved/closed all my 2.0.8 related issues ;o)
Best Regards, Michael
Am 16. Januar 2017 um 15:52:03, Amend, Christian (christian.am...@sap.com)
schrieb:
Hi All,
there have been some commits on the V2 repository wh
4.3.0 and pushed it into
this GitHub Repo.
You can take a look into the classes here:
https://github.com/mibo/PlayOlingo4/tree/master/app/controllers
But as disclaimer this is just a PoC and not a best practice project, so please
excuse the not perfect coding ;o)
Kind Regards, Michael
Am 31
Hi Christian and Dennis,
I agree with you that both versions (2.x/4.x) should be released soon.
For 4.4.0 I will try to finish this minor issue [1] but this is no stopper for
a release.
And for 2.0.8 I can volunteer as release manager if wished.
Regards, Michael
[1]: https://issues.apache.org/j
Hi Christian,
as mentioned before I can volunteer as release manager (for 2.0.9) if wished.
After a short look on the open issues for 2.0.x I see not showstopper, so the
2.0.9 RC could be provided.
Are there any objections or do somebody else see a showstopper issue?
If not I would go ahead and
-1 Do not release this package because...
The release candidate is available here:
http://people.apache.org/~mibo/olingo2/2.0.9-RC01/
The release candidate has been signed through the key 15AB5637 in:
http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex
The release candida
Hi All,
I would continue the release when two more PMC members will give their +1 ;o)
Best Regards, Michael
Am 4. Juli 2017 um 15:05:52, Amend, Christian (christian.am...@sap.com) schrieb:
+1 from my side
From: mibo [mailto:m...@apache.org]
Sent: Freitag, 16. Juni 2017 07:52
To: dev
17 um 16:32:25, Ramesh Reddy (rare...@redhat.com) schrieb:
+1
- Original Message -
> +1 from my side
>
> From: mibo [mailto:m...@apache.org]
> Sent: Freitag, 16. Juni 2017 07:52
> To: dev@olingo.apache.org
> Subject: [VOTE] RC01 for release of Apache Olin
I also agree with the opinion of Ramesh, start with JIRA and a patch.
If it helps (e.g. for discussions) a committer can create an according branch
for proposal (and the patch(s)).
Regards, Michael
> Am 01.11.2017 um 13:46 schrieb Ramesh Reddy :
>
> IMO if you submit a patch with test cases to
[x] +1 Release this package as Apache Olingo 2.0.10
And thank you Christian that you voluntarily make the release manager ;o)
Regards, Michael
> Am 30.11.2017 um 15:34 schrieb Amend, Christian :
>
> Hi all,
>
>
>
> This is a vote on first release candidate (RC01) for Apache Olingo release
[x] +1 Release this package as Apache Olingo 4.5.0
And Thanks to Christian to volunteer as release manager ;o)
Kind Regards, Michael
> Am 06.08.2018 um 14:52 schrieb Christian Amend :
>
> Hi,
>
> This is a vote on the Apache Olingo 4.5.0 release. The vote will be
> open at least for 72 hours
+1 from me.
@Christian:
As we get our "Consensus in the project (documented via the mailing list)" do
you plan to create the necessary JIRA ticket?
Regards, Michael
> - File a JIRA ticket with INFRA to voluntarily move your project repos
> over to gitbox (as stated, this is highly automated and
Hi All,
With currently 5 votes (see below) and no vetos IMHO we have a consensus (or?).
Christian
Ramesh
Francesco
Archana
Michael
Based on this I created the JIRA issue:
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17400
So if there are no sudden objections we with Olingo will be
://gitbox.apache.org/repos/asf/olingo-odata4-js.git
Kind Regards, Michael
On Tue, Dec 11, 2018 at 9:19 PM Dave Fisher wrote:
>
> Yes, I would say do.
>
> Here’s my +1
>
> Sent from my iPhone
>
> > On Dec 11, 2018, at 12:00 PM, mibo wrote:
> >
> > Hi All,
> >
Hi All,
Since the last maintenance release for Olingo 2.0.x branch was over a
year ago and there were several fixed issues in the last months [1] I
would suggest to build a new release (Olingo 2.0.11).
If there are no objections in the next 24 hours I will start preparing
the RC and start the off
Hi All,
As there are no objections I will start with the preparations (building the RC)
for the Olingo 2.0.11 release.
Kind Regards, Michael
Am 28. Jan. 2019, 19:56 +0100 schrieb mibo :
> Hi All,
>
> Since the last maintenance release for Olingo 2.0.x branch was over a
> year ago an
Hi All,
This is a vote on first release candidate (RC01) for next Apache Olingo release
version "2.0.11".
The vote will be open for at least 72 hours (it will close on Wednesday
06/02/2019 on 8pm CET) and passes if no binding vote is (-1).
[ ] +1 Release this package as Apache Olingo 2.0.11
[ ]
Hi Aparna,
Just checked quickly and it seems that the required OSGi export for
`org.apache.olingo.odata2.core.uri;version=${project.version}`
is missing in the `odata-core` Felix-Maven-Plugin config (see code snippet from
`pom.xml` below).
Can you please open a JIRA Bug at https://issues.apache.
che Olingo 2.0.11
>
> +1 for the release
>
> On 03-Feb-2019 10:47 PM, mibo wrote:
> Hi All,
>
> This is a vote on first release candidate (RC01) for next Apache Olingo
> release version "2.0.11".
> The vote will be open for at least 72 hours (it will close on
for the release
>
> -Original Message-
> From: mibo
> Sent: Montag, 11. Februar 2019 10:40
> To: dev@olingo.apache.org
> Subject: RE: [VOTE] RC01 for release of Apache Olingo 2.0.11
>
> Hi all,
>
> Thanks for the current votes.
>
> With my `+1` vote for
Hi Michael,
Thanks for your mail and opinion.
> I have gone through most of your tutorials on how to use OLingo.
First of all, much material and examples pertain to older versions
of OLingo, and are out-of-date. This is really a shame, and costs
the Java-developer a lot of extra time when I want
Hi Ramesh,
Some days ago I had the same thought.
Last release is more than half a year ago and there exists several solved
issues.
My suggestion would be that we check current open issues and target for a
release by mid/end of April.
Some more / other opinions?
Kind regards, Michael
Am 24. Mär
time till end of this week to finish last open
issues or to give feedback regarding the release (time).
Hope this is fine with you.
Kind regards, Michael
On Mon, Apr 22, 2019 at 12:13 AM Ramesh Reddy wrote:
>
> Any update on this?
>
> On Sun, Mar 24, 2019 at 11:47 AM mibo wro
ot; libraries to latest version
> like 2.9.8, existing versions are old not somewhat sync with latest
> spring-boot versions.
>
> Ramesh..
>
> On Tue, Apr 23, 2019 at 2:39 PM mibo wrote:
>
> > Hi Ramesh,
> >
> > Since there are now other opinions (and no objectio
ot release this package because...
The release candidate is available here:
https://home.apache.org/~mibo/olingo4/4.6.0-RC01/
The release candidate has been signed through the key 0x15AB5637 in:
http://pool.sks-keyservers.net:11371/pks/lookup?op=vindex&fingerprint=on&search=0xFAF8A1C815A
ccò
> wrote:
>
> > On 2019-05-01 07:24 mibo wrote:
> > > Hi,
> > >
> > > This is a vote on first release candidate (RC01) for next Apache
> > > Olingo release version "4.6.0".
> > > The vote will be open for at least 72 hours (it wil
+1 from me (really like the new Java 8 features ;o)
On Wed, Sep 4, 2019 at 9:43 AM Vasanth, Ramya wrote:
>
> Hi All,
> Kindly vote for moving olingo library to java 8. With this we will be able to
> leverage all the new features available on java 8.
> Please find the commit id
> https://git-wip
Hi Ramesh,
Yes, doing a release is a good idea.
Next week I plan to check our dependency if some of them should be updated.
So let us plan and target for a release by end of this month?
Is this ok with you?
Or does someone have any objections?
Kind Regards, Michael
On Thu, Oct 31, 2019 at 9:08 P
9 at 10:28 PM Ramesh Reddy wrote:
>
> > The end of month works for me.
> >
> > Thank you.
> >
> > On Tue, Nov 5, 2019 at 9:56 AM mibo wrote:
> >
> >> Hi Ramesh,
> >>
> >> Yes, doing a release is a good idea.
> >> Next week
Hi Erming,
I had only a quick look in the hope to detect the problem and provide
a fix which can be part of next release.
However I'm not sure how this can happen when Olingo is used in a prober way.
Because from staring with the OData.newInstance() (see TecSvc as
sample [1]) all further objects a
7.0
[ ] -1 Do not release this package because...
The release candidate is available here:
https://people.apache.org/~mibo/olingo4/4.7.0-RC01/
The release candidate has been signed through the key 15AB5637 in:
https://keys.openpgp.org/vks/v1/by-fingerprint/53FF889B221C7FBDF4D6CCC2FAF8A1C815A
me. Can you please show me how to create a JIRA in
> your system?
>
> Thx
>
> Erming
>
> On 11/27/19, 2:20 AM, "mibo" wrote:
>
> Hi Erming,
>
> I had only a quick look in the hope to detect the problem and provide
> a fix which can be par
:
>
> +1
>
> On Wed, Nov 27, 2019 at 9:42 PM Francesco Chicchiriccò
> wrote:
>
> > On 27/11/19 13:53, mibo wrote:
> > > Hi All,
> > >
> > > This is a vote on first release candidate (RC01) for Apache Olingo
> > > release version "4.7.
Thanks, I will check it out as soon as I have some time.
Kind Regards, Michael
On Sat, Nov 30, 2019 at 5:11 PM Tuo, Erming wrote:
>
> https://issues.apache.org/jira/browse/OLINGO-1413 is created to track the
> issue
>
> On 11/27/19, 4:43 PM, "mibo" wrote:
>
>
at 11:32 AM mibo wrote:
>
> Hi all,
>
> The vote passed with three positive and no negative vote.
>
> The votes are:
> +1 Francesco Chicchiriccò (binding)
> +1 Ramesh Reddy (binding)
> +1 Michael Bolz (binding)
>
> I will now go forward with the next release steps.
Hi Ramesh,
got some issues but everything should be available till tomorrow evening.
Kind Regards, Michael
On Tue, Dec 3, 2019 at 5:37 AM Ramesh Reddy wrote:
>
> Michael,
>
> When will artifacts be pushed to Maven?
>
> Ramesh..
>
> On Sun, Dec 1, 2019 at 4:13 PM m
[ ] -1 Do not release this package because...
The release candidate is available here:
https://people.apache.org/~mibo/olingo4/4.7.1-RC01/
The release candidate has been signed through the key 15AB5637 in:
https://keys.openpgp.org/vks/v1/by-fingerprint/53FF889B221C7FBDF4D6CCC2FAF8A1C815AB5637
T
Hi all,
The vote passed with three positive and no negative vote.
The votes are:
+1 Francesco Chicchiriccò (binding)
+1 Ramesh Reddy (binding)
+1 Michael Bolz (binding)
I will now go forward with the next release steps.
Kind Regards, Michael
Hi Andrew,
Sorry for the late response but unfortunately I was first very busy and later
on vacation.
Our homepage is still on the CMS and we have no concrete migration plan.
After a quick look I would go with the GitHub pages approach:
https://infra.apache.org/github-pages.html
Based on your t
Hi All,
FYI - just in time the old Jenkins jobs were migrated to the new instance.
Find all Olingo jobs new here: https://ci-builds.apache.org/job/Olingo/
Kind Regards, Michael
-- Weitergeleitete Nachricht --
Von: Gavin McDonald
Datum: 15. Aug. 2020, 14:25 +0200
An: Apache Infra
Hi Raghu,
Best way is to ask your question at u...@olingo.apache.org
The dev mailing list (dev@olingo.apache.org) is more for dev discussion of the
contributors.
Kind Regards, Michael
> Am 21.11.2020 um 16:09 schrieb Ramakrishnan, Raghavendran
> :
>
>
>
>
> Respected Sir
>
> We are havi
Hi All,
As last Olingo V4 release is around one year ago I would like to make a new
release.
Based on the commit history there are lot fixes and updated so I would release
it as 4.8.0.
If there are no objections I would start next week with the required
preparations.
Kind Regards, Michael
[ ] -1 Do not release this package because...
The release candidate is available here:
https://people.apache.org/~mibo/olingo4/4.8.0-RC01/
The release candidate has been signed through the key 15AB5637 in:
https://keys.openpgp.org/vks/v1/by-fingerprint/53FF889B221C7FBDF4D6CCC2FAF8A1C815AB5637
T
schrieb mibo :
> Hi All,
>
> This is a vote on first release candidate (RC01) for Apache Olingo
> release version "4.8.0".
> The vote will be open for at least 72 hours (planned to close on
> Monday 17/12/2019 on 10pm CET or later) and passes if no vote is (-1).
>
> [ ]
Thanks Ramesh for the +1 vote.
Hope one of the other PMCs can have a look and give feedback.
As I have still the hope to do the release before Christmas 🙂
Kind Regards, Michael
Am 18. Dez. 2020, 15:23 +0100 schrieb Ramesh Reddy :
> +1
>
> On Fri, Dec 18, 2020 at 12:02 AM mibo wrote:
Hi -
>
> I started, but I have to be -0.
>
> The KEYS file does not contain the key used to sign the archives.
>
> If this is fixed then I will check again.
>
> Regards,
> Dave
>
> > On Dec 14, 2020, at 12:17 PM, mibo wrote:
> >
> > Hi All,
> >
fixed.
Hence I will now go forward with the next release steps.
Kind Regards, Michael
Am 14. Dez. 2020, 21:17 +0100 schrieb mibo :
> Hi All,
>
> This is a vote on first release candidate (RC01) for Apache Olingo
> release version "4.8.0".
> The vote will be open for at least
Hello,
we proudly announce that Apache Olingo 4.8.0 has been released.
This is a minor maintenance release for Olingo OData Version 4
(see OData specification [1] and new features [2]).
This release is available for download:
https://olingo.apache.org/doc/odata4/download.html
Tutorials and docu
Hello,
we proudly announce that Apache Olingo 4.8.0 has been released.
This is a minor maintenance release for Olingo OData Version 4
(see OData specification [1] and new features [2]).
This release is available for download:
https://olingo.apache.org/doc/odata4/download.html
Tutorials and docu
Hi All,
A while ago someone suggested that we (Olingo devs) use signed commits [1].
Personally I think it is a really good idea but (afaik)there is no way to make
it mandatory.
Hence, I recommended that use of signed commits is added as a note or
requirement to the contribution guide for Olingo
Hello Daniel,
Next release was planned for end of February.
However, because of some private reasons I was not able to work on Olingo in
the past two weekends.
Will now prepare the 4.8.0 release and hopefully finish it next weekend.
The 2.0.12 will be prepared afterwards.
At least this are the cu
Just realized that I wrote "prepare the 4.8.0 release“, must of course be
"4.9.0“ 😉
Am 26. Feb. 2022, 08:00 +0100 schrieb mibo :
> Hello Daniel,
>
> Next release was planned for end of February.
> However, because of some private reasons I was not able to work on Oli
[ ] -1 Do not release this package because...
The release candidate is available here:
https://people.apache.org/~mibo/olingo4/4.9.0-RC01/
The release candidate has been signed through the key 15AB5637 in:
https://keys.openpgp.org/vks/v1/by-fingerprint/53FF889B221C7FBDF4D6CCC2FAF8A1C815AB5637
T
.
Kind Regards, Michael
[1]: https://www.apache.org/legal/release-policy.html#release-approval
Am 27. Feb. 2022, 08:27 +0100 schrieb mibo :
> Hi All,
>
> This is a vote on first release candidate (RC01) for Apache Olingo
> release version "4.9.0".
> The vote will be o
s take a look too 🙂
Am 7. März 2022, 06:24 +0100 schrieb Dave Fisher :
> If this is still active I’ll take a look tomorrow.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Mar 4, 2022, at 9:45 PM, mibo wrote:
> >
> > Hi all,
> >
> >
Hi together,
The vote is over and has passed with the following votes:
+1 Stephan Klevenz (binding)
+1 Francesco Chicchiriccò (binding)
+1 Ramesh Reddy (binding)
+1 Jens Hüsken (binding)
+1 Michael Bolz (binding)
And no “-1" vote against the release.
Hence I will now go forward with the next rel
-1 Do not release this package because...
The release candidate is available here:
https://people.apache.org/~mibo/olingo2/2.0.12-RC01/
The release candidate has been signed through the key 15AB5637 in:
http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex
The release candida
release.
Thanks in advance and kind Regards, Michael
Am 13. März 2022, 07:10 +0100 schrieb mibo :
> Hi All,
>
> This is a vote on first release candidate (RC01) for next Apache Olingo
> release version "2.0.12".
> The vote will be open for at least 72 hours (it will clos
Hi Caio,
Olingo 4 is a library to support building OData 4 Clients/Servers by
providing functions to serialize/deserialize and route OData request.
Hence, there is no support for database connection.
Olingo 2 had a JPA processor to expose data provided via JPA and supports
according databases.
How
Hi together,
The vote is over and has passed with the following votes:
+1 Stephan Klevenz (binding)
+1 Christian Amend (binding)
+1 Michael Bolz (binding)
And no “-1" vote against the release.
Hence I will now go forward with the next release steps.
Expect the release be available this weekend.
Hi Craig,
Thanks for the note.
Have checked (while the second mail was written) and the was an issue during
the upload yesterday.
It is fixed now and all files are available.
Kind Regards, Michael
Am 25. Apr. 2022, 21:20 +0200 schrieb Private List Moderation
:
> On Mon, 25 Apr 2022 at 17:49, Pr
Sorry, somehow I mixed it up.
Now everything is fixed and available.
Thanks for your patience.
Kind Regards, Michael
Am 25. Apr. 2022, 21:36 +0200 schrieb Private List Moderation
:
>
>
> > On Apr 25, 2022, at 12:20 PM, Private List Moderation
> > wrote:
> >
> > On Mon, 25 Apr 2022 at 17:49, Pr
Hi All,
The last Olingo V2 and V4 release was over one year ago. Hence, I would
prepare a new release for both.
Based on the commit history there are not many fixes/improvements.
My proposal is to check open PRs/ JIRA issues till the end of June to add
some more fixes/improvements. In addition I
Hi All,
As there were no objections I would start with the required preparations and
continue as proposed.
Kind Regards, Michael
Am 12. Juni 2023, 21:05 +0200 schrieb mibo :
> Hi All,
>
> The last Olingo V2 and V4 release was over one year ago. Hence, I would
> prepare a new rele
@Francesco: Thanks for taking this.
And sorry from me for the delay. I had a longer time off and could not
check/approve requests.
Kind Regards, Michael
Am 24. Aug. 2023, 10:50 +0200 schrieb Francesco Chicchiriccò
:
> I have managed to approve your pending request, Emma, sorry it took a bit to
Hello Dev Community,
First I want to apologize for the delay with the release and the support for
newer Java / Spring Boot versions.
The reason was that I was very involved in my private and professional life. I
hope I will be better in the next few months.
The roadmap for Apache Olingo is to d
ngo 2.0.13
[ ] -1 Do not release this package because...
The release candidate is available here:
https://people.apache.org/~mibo/olingo2/2.0.13-RC01/
The release candidate has been signed through the key 15AB5637 in:
http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vinde
Hi All,
Again sorry for the delay in the release.
However, as no one in the PMC gives a vote, I’m blocked anyway ;o)
Dear PMC colleagues, can you please have a look and give feedback / a vote for
the release?
Kind Regards, Michael
Am 23. Sept. 2023, 18:19 +0200 schrieb mibo :
> Hi
ngo 4.10.0
[ ] -1 Do not release this package because...
The release candidate is available here:
https://people.apache.org/~mibo/olingo4/4.10.0-RC01/
The release candidate has been signed through the key 15AB5637 in:
https://keys.openpgp.org/vks/v1/by-fingerprint/53FF889B221C7FBDF4D6CCC2FAF8A1C815A
PR and take the decision there).
However, I’m open to opinions and discussions.
Kind Regards, Michael 'mibo'
Am 16. Sept. 2023, 10:48 +0200 schrieb mibo :
> Hello Dev Community,
>
> First I want to apologize for the delay with the release and the support for
> newer Java
ael
Am 23. Sept. 2023, 18:19 +0200 schrieb mibo :
> Hi All,
>
> This is a vote on first release candidate (RC01) for next Apache Olingo
> release version "2.0.13".
> The vote will be open for at least 72 hours (plan is to close latest on next
> Saturday 30.09
egards, Michael
Am 15. Okt. 2023, 09:18 +0200 schrieb mibo :
> Hi All,
>
> This is a vote on first release candidate (RC01) for Apache Olingo
> release version "4.10.0".
> The vote will be open for at least 72 hours (planned to close on
> Saturday 21th of October 202
planned to close on
Friday 1st of December 2023 on 10pm CET) and passes if no vote is (-1).
[ ] +1 Release this package as Apache Olingo 5.0.0
[ ] -1 Do not release this package because...
The release candidate is available here:
https://people.apache.org/~mibo/olingo4/5.0.0-ALPHA-02/
The release
> [ ] -1 Do not release this package because...
> >
> > The release candidate is available here:
> > https://people.apache.org/~mibo/olingo4/5.0.0-ALPHA-02/
> >
> > The release candidate has been signed through the key 15AB5637 in:
> >
> > https://keys.openpgp.org/vks
release.
I will now continue with the next release steps and the release should be
available in the next days.
Kind Regards, Michael
Am 3. Dez. 2023, 09:39 +0100 schrieb mibo :
> Hi All,
>
> Adding mit +1 for the release we are now at:
>
>
> +1 Ramesh Reddy (binding)
> +1 E
[
https://issues.apache.org/jira/browse/OLINGO-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mibo resolved OLINGO-1344.
--
Resolution: Fixed
Fixed with this commit: [\[OLINGO-1344\] Fix deadlock ThreadPool (by
Aleksandr)|https
[
https://issues.apache.org/jira/browse/OLINGO-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mibo resolved OLINGO-1343.
--
Resolution: Fixed
Fixed with this commit: [\[OLINGO-1343\] Fix deadlock Piped_Stream (by
Aleksandr)|https
[
https://issues.apache.org/jira/browse/OLINGO-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827214#comment-16827214
]
mibo commented on OLINGO-1343:
--
Hi [~dw3105],
Unfortunately I could not apply your p
[
https://issues.apache.org/jira/browse/OLINGO-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827215#comment-16827215
]
mibo commented on OLINGO-1344:
--
Hi [~dw3105],
Unfortunately I could not apply your p
mibo created OLINGO-1351:
Summary: Failing build because of OSGi / Karaf tests
Key: OLINGO-1351
URL: https://issues.apache.org/jira/browse/OLINGO-1351
Project: Olingo
Issue Type: Bug
[
https://issues.apache.org/jira/browse/OLINGO-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mibo reassigned OLINGO-1351:
Assignee: mibo
> Failing build because of OSGi / Karaf te
1 - 100 of 478 matches
Mail list logo
