+1 for option 2 (primary)
+1 for option 1 (secondary)
Thank you,
Vlad
On 8/21/17 23:37, Ananth G wrote:
+1 for option 2 and second vote for option 1
Have we finalized the library name ? Going from Apex-malhar 3.7 to
Apex-malhar-1.0 would be counter intuitive. Also it would be great if we have
an agreed process to mark an operator from @evolving to stable version given we
are trying to address this as well as part of the proposal
Regards
Ananth
On 22 Aug 2017, at 11:40 am, Thomas Weise <t...@apache.org> wrote:
+1 for option 2 (second vote +1 for option 1)
On Mon, Aug 21, 2017 at 6:39 PM, Thomas Weise <t...@apache.org> wrote:
This is to formalize the major version change for Malhar discussed in [1].
There are two options for major version change. Major version change will
rename legacy packages to org.apache.apex sub packages while retaining file
history in git. Other cleanup such as removing deprecated code is also
expected.
1. Version 4.0 as major version change from 3.x
2. Version 1.0 with simultaneous change of Maven artifact IDs
Please refer to the discussion thread [1] for reasoning behind both of the
options.
Please vote on both options. Primary vote for your preferred option,
secondary for the other. Secondary vote can be used when counting primary
vote alone isn't conclusive.
Vote will be open for at least 72 hours.
Thanks,
Thomas
[1] https://lists.apache.org/thread.html/bd1db8a2d01e23b0c0ab98a785f6ee
9492a1ac9e52d422568a46e5f3@%3Cdev.apex.apache.org%3E
Thank you,
Vlad
