Hi all, Last (bugfix) release for Apache Olingo V2 is some time ago and in the meanwhile we have fixed several issues (see: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314520&version=12328918 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314520&version=12328918>). Hence I suggest we create next maintenance/bugfix release version 2.0.2.
A reasonable timeline for me would be: - Today/Tomorrow clean up/move open JIRA “Bug" issues (related to V2) [1] - Code freeze at Monday (26.01.) - Create RC01 on next Monday/Tuesday and start voting - If all works well create release on next week Thursday/Friday If there are no objections I will proceed with above listed timeline. Kind regards, Michael [1]: https://issues.apache.org/jira/issues/?jql=project%20%3D%20OLINGO%20AND%20issuetype%20%3D%20Bug%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20in%20(odata2-annotation%2C%20odata2-core%2C%20odata2-documentation%2C%20odata2-jpa)%20ORDER%20BY%20priority%20DESC <https://issues.apache.org/jira/issues/?jql=project%20=%20OLINGO%20AND%20issuetype%20=%20Bug%20AND%20resolution%20=%20Unresolved%20AND%20component%20in%20(odata2-annotation,%20odata2-core,%20odata2-documentation,%20odata2-jpa)%20ORDER%20BY%20priority%20DESC>
smime.p7s
Description: S/MIME cryptographic signature
