-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plan for 2.0.0-M14 🎯 #1531
Comments
@JaroslawLegierski, @mgdlkundera, @cyril2maq is it OK for you if we try to do a code freeze in |
I have just received information from my French colleagues - They plan test 2.0.0-M14RC in the next week. |
Let's declare a 🥶 code freeze in This release should include :
This gives us 1 week to test using either :
|
@JaroslawLegierski, @mgdlkundera, @cyril2maq, let me know when I have green light 🟢 to start the release process. On my side there is no urgency but please let me some approximate visibility about this 🙏 (and no problem if that changes later) |
On my side, I did perform non reg tests (hence the created issue)+ some check of the new behavior (no more error console logs DDFFileParser, SendRequest checks, updated objectId range and definition) |
From our side also 🟢 |
For me it is also 🟢 |
👷 Release process is ongoing ! 🚧 |
🎉 Release is out : 2.0.0-M14 is out ! 🎉 Thx all for you help 🙏 !! |
A 2.0.0-M14 release was requested by Orange. (#1520 (comment))
If possible Orange would like to have it released for Thursday, November 23.
So let's start to discuss and plan work to do about it.
What is currently included for M14:
New commits in
master
since M13 :Redis Store Compatibility break :
No break.
What is missing ?
Here is some topic that we maybe want in M14 ?
Add support to "/" for Read-Composite. #989Negative values handling for Write Attribute #1451If you have more ideas, please comments 👇
The text was updated successfully, but these errors were encountered: