Re: [VOTE] Major version change for Apex Library (Malhar)

I think the backward in-compatibility is there in both options. I think we should give sufficient time frame for community members/ users for major changes. So, I'm -1 on both options. On Fri, Sep 1, 2017 at 5:43 PM, Sandeep Deshmukh wrote: > -1 from my side for

Re: [VOTE] Major version change for Apex Library (Malhar)

-1 for option 2 as well. I do not see any reason why we should do so. This will just confuse the users. On Fri, Sep 1, 2017 at 5:48 PM, Yogi Devendra wrote: > One thing which is not clear to me is: if someone has any contributions > planned for 3.x; will that

Re: [VOTE] Major version change for Apex Library (Malhar)

One thing which is not clear to me is: if someone has any contributions planned for 3.x; will that contribution need 2 different PRs? If yes, then can we avoid this by giving sufficient time for the community to prepare for this change? -1 for immediate release. -1 for immediate separation for

Re: [VOTE] Major version change for Apex Library (Malhar)

-1 from my side for "1. Version 4.0 as major version change from 3.x" Was out of station for festival season in India so delay in voting and replying. Reason: I don't see a compelling reason for a major change at this moment. As a user of Apex, I have developed a system using Apex but now I

Re: [VOTE] Major version change for Apex Library (Malhar)

Apologies for being late in discussions. I wanted to understand one thing. As Thomas mentioned some of our operators are not matured enought or lacks operability. Do we know if such operators need any backword incompatible changes? e.g. modification to api etc? Do we have plan to promote operators

Re: [VOTE] Major version change for Apex Library (Malhar)

Hi First of all my apologies for voting late. However, I will still do it since the mail says the vote would remain open for *at least* 72 hours :) I believe the objective is to do the right things rightly. Moving to a new version is something that is a part of any product lifecycle. While doing

Re: [VOTE] Major version change for Apex Library (Malhar)

Being against something is not a valid reason. I also want to repeat a point made earlier regarding discussion style: To facilitate a constructive, continuous discussion and make progress, it is necessary that participants take into account what was already addressed. A few folks that never

Re: [VOTE] Major version change for Apex Library (Malhar)

I am not against a new major version. I am against the reason for it. Please include a list of functional feature set in the vote for 4.0, not just package name changes. Regards, Ashwin. On Aug 25, 2017 5:02 PM, "Thomas Weise" wrote: > Always welcome. But before you go.. What

Re: [VOTE] Major version change for Apex Library (Malhar)

Always welcome. But before you go.. What do you mean by rigged? Your vote? ;) Why do I get the impression someone could be pulling strings to stop a new major version after the changes were discussed for such a long time? Why not let the community continue development, it does not prevent anyone

Re: [VOTE] Major version change for Apex Library (Malhar)

Haha I missed your personal attacks Thomas. Love it! This voting thread is rigged, I am out :) Anyway - as a user when a project announces a new major version - I would expect it to include some major features. I stand by my vote until we associate and list some major features with the major

Re: [VOTE] Major version change for Apex Library (Malhar)

Welcome back to the mailing list (it has been 6 months according to the archive?). The topic seems to be important enough, so hopefully you had the chance to review the related discussion threads as these already address some of what repeats here? On Fri, Aug 25, 2017 at 2:00 PM, Ashwin Chandra

Re: [VOTE] Major version change for Apex Library (Malhar)

I agree that it makes the project consistent to have the package names changed to org.apache.apex. However, it seems like an unnecessary overhead to make a major version change for just changing package names. I may be wrong but is there a major feature set in the proposed vote that deems for a

Re: [VOTE] Major version change for Apex Library (Malhar)

I'm +1 on option 2, second +1 on option 1. Having two names, in our case Apex and Malhar, in a project tend to confuse people, especially since the prefix "mal" usually has a negative connotation in English. David On Aug 23, 2017 3:17 PM, "Sergey Golovko" wrote: > -1

Re: [VOTE] Major version change for Apex Library (Malhar)

-1 for the option 2 I don't think it makes sense to rush to rename the package name. There are Apache Java projects that use the original package names after migration to Apache Software Foundation. For instance, Apache Felix (org.osgi) Apache

Re: [VOTE] Major version change for Apex Library (Malhar)

So far everyone else has voted +1 on option 1. Your -1 is not a veto (unlike your previous -1 on a pull request), but your response also states "I am for option 1" and that you want to have the branch release-3 included. So why don't you include that into your vote for option 1 as a condition,

Re: [VOTE] Major version change for Apex Library (Malhar)

On just voting part, I remain -1 on both options Thks Amol E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre* www.datatorrent.com On Tue, Aug 22, 2017 at 4:35 PM, Pramod Immaneni wrote: > I think we should take this discussion to a separate thread as

Re: [VOTE] Major version change for Apex Library (Malhar)

I think we should take this discussion to a separate thread as it is a vote thread. I don't see a need for this change now as there isn't enough justification (such as things are falling apart without this) for the disruption it will cause. My earlier point is that there was a justification when

Re: [VOTE] Major version change for Apex Library (Malhar)

Do you mean that prior to groupId change nobody was using that groupId or that nobody was using the library itself :)? If nobody was using the library, the version 3.x at the beginning of the project is questionable. My question is why -1 (veto) as long as things won't fall apart either way.

Re: [VOTE] Major version change for Apex Library (Malhar)

I would argue that things won't fall apart in both cases whether artifactId and version are changed or not, so I don't see why it is -1 for the option 2. When groupId was changed from com.datatorrent to org.apache.apex, things have not fall apart :). Thank you, Vlad On 8/22/17 08:31, Pramod

Re: [VOTE] Major version change for Apex Library (Malhar)

On Tue, Aug 22, 2017 at 10:03 AM, Amol Kekre wrote: > I am -1 on option 2. There is no need to do so, as going back on versions > at this stage has consequences to Apex users. > > I am for option 1, but I want to propose explicit change to the text. Based > on verbatim

Re: [VOTE] Major version change for Apex Library (Malhar)

I am -1 on option 2. There is no need to do so, as going back on versions at this stage has consequences to Apex users. I am for option 1, but I want to propose explicit change to the text. Based on verbatim text, I am voting -1 on option 1. I believe in the original discussion thread there was

Re: [VOTE] Major version change for Apex Library (Malhar)

+1 for option 1 -1 for option 2 as I see no impending need to do this now, as in if we don't do this, things will fall apart. It will be a source of more disruption and confusion. Malhar has been around for quite some time, evolving and growing during this period and going to version 4.0 would be

Re: [VOTE] Major version change for Apex Library (Malhar)

+1 for option 2 (primary) +1 for option 1 (secondary) Ram On Tuesday, August 22, 2017, 6:58:46 AM PDT, Vlad Rozov wrote: +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

Re: [VOTE] Major version change for Apex Library (Malhar)

+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

Re: [VOTE] Major version change for Apex Library (Malhar)

+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

Re: [VOTE] Major version change for Apex Library (Malhar)

+1 for option 2 (second vote +1 for option 1) On Mon, Aug 21, 2017 at 6:39 PM, Thomas Weise 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