next release - 3.9.0 or 4.0.0?
Thank you,
Vlad
On 7/13/17 22:25, Thomas Weise wrote:
It is time to resurrect this thread and get going with the work.
For the next release, I will sign up to do the package move in Malhar:
https://issues.apache.org/jira/browse/APEXMALHAR-2517
In general this
Would prefer to have bw compatibility stubs for the regularly used
operators such as kafka (0.8), file, db etc and mark them deprecated. Would
like to have at least one 3.x release before going to 4.0 where we can
remove all the deprecated code.
Thanks
On Fri, Jul 14, 2017 at 7:55 AM, Vlad Rozov
next release is 3.8.0
On Fri, Jul 14, 2017 at 7:55 AM, Vlad Rozov wrote:
> next release - 3.9.0 or 4.0.0?
>
> Thank you,
>
> Vlad
>
> On 7/13/17 22:25, Thomas Weise wrote:
>
>> It is time to resurrect this thread and get going with the work.
>>
>> For the next release, I will sign up to do the p
[
https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087463#comment-16087463
]
ASF GitHub Bot commented on APEXCORE-757:
-
PramodSSImmaneni commented on a chang
My preference is to agree that the next Malhar release is 4.0.0 and make
the proposed changes when 3.8.0 goes out. Otherwise why to keep semantic
versioning checks on Malhar in case there is no version compatibility.
Thank you,
Vlad
On 7/14/17 08:11, Thomas Weise wrote:
next release is 3.8.0
[
https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087496#comment-16087496
]
ASF GitHub Bot commented on APEXCORE-757:
-
vrozov commented on a change in pull
[
https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087498#comment-16087498
]
ASF GitHub Bot commented on APEXCORE-757:
-
PramodSSImmaneni commented on a chang
[
https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087503#comment-16087503
]
ASF GitHub Bot commented on APEXCORE-757:
-
PramodSSImmaneni commented on a chang
Vlad,
Please get in touch with infra and have the JIRA PR comments turned off.
That was the previous setup.
Transition planned and discussed upfront can help avoiding such churn.
Thanks,
Thomas
On Thu, Jul 13, 2017 at 7:46 PM, Vlad Rozov wrote:
> I open ticket INFRA-14588 to enable it back.
[
https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087521#comment-16087521
]
ASF GitHub Bot commented on APEXCORE-757:
-
PramodSSImmaneni commented on a chang
Semantic versioning makes sense when you have a stable baseline. As long as
frequent fixes need to be made to address basic issues, it makes no sense
to declare operators stable, which is why they are marked evolving.
Instead of finding reasons to avoid changes that should have been made a
long ti
Thomas,
I already updated INFRA-14588 with the request to disable update of Apex
JIRAs with PR comments. Note that your comments on INFRA-14588 were
already present and ignored when INFRA enabled gitbox notifications to JIRA.
I did not expect that it would be a transition. My expectation was
If entire library is not stable, its version should be 0.x.x and there
should not be any semantic versioning enabled or implied. It evolves. If
some operators are stable as 3.8.x version suggests, the library should
follow semantic versioning and it is not OK to make a major change that
breaks
[
https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087561#comment-16087561
]
ASF GitHub Bot commented on APEXCORE-757:
-
vrozov commented on a change in pull
Most of the operators evolve, as is quite clearly indicated by @Evolving
annotations. So while perhaps 0.x.x would be a more appropriate version
number, I don't think you can change that.
Thomas
On Fri, Jul 14, 2017 at 9:35 AM, Vlad Rozov wrote:
> If entire library is not stable, its version sh
We had a discussion a while back, agreed to relegate non-stable and
experimental operators to contrib and also added this to contribution
guidelines. We aexecuted on this and cleaned up the repo by moving
operators deemed non-suitable for production use at that time to contrib.
So I wouldn't say th
[
https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087624#comment-16087624
]
ASF GitHub Bot commented on APEXCORE-757:
-
PramodSSImmaneni commented on a chang
We need to keep the discussion here on topic, if other things are piled on
top then nothing gets done.
Most operators today are not stable, they are @Evolving. So perhaps it is
necessary to have a separate discussion about that, outside of this thread.
My guess is that there are only a few operato
[
https://issues.apache.org/jira/browse/APEXMALHAR-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087701#comment-16087701
]
ASF GitHub Bot commented on APEXMALHAR-2518:
sandeshh commented on issue
How about coming up with a list of @Evolving operators that we would like
to see in the eventual stable list and move those along with the not
@Evolving ones in org.apache.apex with b/w stubs and leave the rest as they
are. Then have a follow up JIRA for the rest to be moved over to contrib
and be
[
https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087752#comment-16087752
]
Vinay Bangalore Srikanth commented on APEXCORE-759:
---
I checked for an
[
https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087765#comment-16087765
]
Pramod Immaneni commented on APEXCORE-759:
--
Thanks vinay. I will update the JIR
[
https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni updated APEXCORE-759:
-
Summary: Topology validation needs to happen correctly for operators
connected using THR
[
https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088117#comment-16088117
]
Vinay Bangalore Srikanth commented on APEXCORE-759:
---
I tried these as
[
https://issues.apache.org/jira/browse/APEXCORE-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088239#comment-16088239
]
ASF GitHub Bot commented on APEXCORE-734:
-
PramodSSImmaneni commented on issue #
[
https://issues.apache.org/jira/browse/APEXCORE-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088247#comment-16088247
]
ASF GitHub Bot commented on APEXCORE-734:
-
PramodSSImmaneni commented on a chang
[
https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088246#comment-16088246
]
ASF GitHub Bot commented on APEXCORE-757:
-
sanjaypujare commented on a change in
[
https://issues.apache.org/jira/browse/APEXCORE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088248#comment-16088248
]
ASF GitHub Bot commented on APEXCORE-757:
-
vrozov commented on a change in pull
[
https://issues.apache.org/jira/browse/APEXCORE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088265#comment-16088265
]
ASF GitHub Bot commented on APEXCORE-743:
-
PramodSSImmaneni commented on a chang
[
https://issues.apache.org/jira/browse/APEXCORE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088266#comment-16088266
]
ASF GitHub Bot commented on APEXCORE-743:
-
PramodSSImmaneni commented on a chang
[
https://issues.apache.org/jira/browse/APEXMALHAR-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXMALHAR-2518.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> Kafka input operator stops reading tuples whe
Sandesh created APEXCORE-761:
Summary: Add a utility class/methods to read the system properties
Key: APEXCORE-761
URL: https://issues.apache.org/jira/browse/APEXCORE-761
Project: Apache Apex Core
[
https://issues.apache.org/jira/browse/APEXCORE-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-761:
Assignee: Sandesh
> Add a utility class/methods to read the system properties
> -
33 matches
Mail list logo
