As the project is moving to attic, on the off chance that anybody is still
interested in contributing or working on the project, I have setup the
repositories under dtpublic
https://github.com/dtpublic/apex-core
https://github.com/dtpublic/apex-malhar
https://github.com/dtpublic/apex-site
This is
[
https://issues.apache.org/jira/browse/APEXMALHAR-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804597#comment-16804597
]
Pramod Immaneni commented on APEXMALHAR-2566:
-
[~vikram25] looks
[
https://issues.apache.org/jira/browse/APEXMALHAR-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799364#comment-16799364
]
Pramod Immaneni commented on APEXMALHAR-
Pramod Immaneni created APEXMALHAR-2566:
---
Summary: NPE in FSWindowDataManager
Key: APEXMALHAR-2566
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2566
Project: Apache Apex Malhar
t; Thank you,
>
> Vlad
>
>
> > On Jan 28, 2019, at 11:58, Pramod Immaneni
> wrote:
> >
> > Amol regarding performance my thoughts were along similar lines but was
> > concerned about performance degradation to the real-time path, that new
> > change
; to current features. I will word is as "do not degrade current
> performance
> >> significantly".
> >>
> >> Amol
> >>
> >>
> >> On Fri, Jan 25, 2019 at 9:41 PM Sanjay Pujare
> >> wrote:
> >>
> >>> +1
&
Our contributor and committer guidelines haven't changed in a while. In
light of the discussion that happened a few weeks ago, where
high commit threshold was cited as one of the factors discouraging
submissions, I suggest we discuss some ideas and see if the guidelines
should be updated.
I have o
FO] -
> >> [INFO] -----
> >> [ERROR] COMPILATION ERROR :
> >> [INFO] -
> >> [ERROR]
>
I agree we should just try changing the dependency first. I am in favor of
upgrading. It will be good to explore if and how we can leverage some of
the new features in 3.x.
On Fri, Jan 11, 2019 at 11:38 AM Vlad Rozov wrote:
> Hi Aaron,
>
> I’d recommend to start with upgrading Hadoop dependency
t culture, and then wait 6 months to see if things change.
> With
> >>>> regards to listing features, that needs to be something that the
> >>>> contributors should decide.
> >>>>
> >>>> Amol
> >>>>
> >>>
n central and a dependency on a
> snapshot version are equally bad and both usually lead to broken builds.
>
> While protocol may change, API of the connector may change as well, so you
> are not well guarded here by using salesforce library, IMO.
>
> Thank you,
>
> Vlad
>
urself into the shoes of someone who just uses the
> binaries
> > available here vs. some derivate of former support contract), but putting
> > back enhancements and fixes developed as you go would be a good
> > step forward.
> >
> > Thomas
> >
> > On Wed,
We have a couple of operators notably a salesforce operator that I am
trying to get the necessary permissions at work to contribute. The
underlying salesforce client library (emp-connector) used by the operator
doesn't have a release yet so that is another reason slowing things down,
waiting to iro
What would be the purpose of such a vote? From the discussions it is quite
apparent that there is a significant, possibly majority view that project
shouldn’t go to attic. The same could be reported to the board, can’t it?
Like I also said if you or others don’t like where the project is at and
fee
is should go into the next report to the Apache board and all PMCs
> (especially those who does not want to move Apex to attic) should prepare
> to answer more concerns from the board.
>
> Thank you,
>
> Vlad
>
> > On Jan 8, 2019, at 11:07, Pramod Immaneni
> wrote:
e. If there's no pressing need to retire it, why do so?
> It's possible some enterprise may pick it up and revive it - seems that's
> more likely if it's not hidden away in the 'attic'.
> -Ilya Ganelin
>
>
> On Mon, Jan 7, 2019 at 8:24 PM Pramod Imm
> >
> >
> > On Mon, Jan 7, 2019 at 9:50 PM Atri Sharma wrote:
> >
> >> I agree.
> >>
> >> The project, IMO, still has hopes for survival since it is well
> >> respected for its capabilities. Putting it in attic basically kills it
> >
gt; > On Jan 7, 2019, at 12:06, Pramod Immaneni
> wrote:
> >
> > Yes, I have an operator that I am trying to get clearance on before
> > submitting. Will likely need a maven server to host a dependency that's
> not
> > on central.
> >
> > Thanks
> &
Yes, I have an operator that I am trying to get clearance on before
submitting. Will likely need a maven server to host a dependency that's not
on central.
Thanks
On Mon, Jan 7, 2019 at 9:08 AM Vlad Rozov wrote:
> Does anyone plan to contribute to the project in the near future?
> Otherwise, I
[
https://issues.apache.org/jira/browse/APEXCORE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580385#comment-16580385
]
Pramod Immaneni commented on APEXCORE-796:
--
We had some community discuss
[
https://issues.apache.org/jira/browse/APEXCORE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni reassigned APEXCORE-724:
Assignee: Pramod Immaneni
> Support for Kuberne
[
https://issues.apache.org/jira/browse/APEXMALHAR-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580363#comment-16580363
]
Pramod Immaneni commented on APEXMALHAR-2565:
-
The in-memory stat
[
https://issues.apache.org/jira/browse/APEXCORE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553684#comment-16553684
]
Pramod Immaneni commented on APEXCORE-796:
--
Yes, this Jira does not req
[
https://issues.apache.org/jira/browse/APEXCORE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551024#comment-16551024
]
Pramod Immaneni commented on APEXCORE-724:
--
Please see comment on APEX
[
https://issues.apache.org/jira/browse/APEXCORE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551023#comment-16551023
]
Pramod Immaneni commented on APEXCORE-796:
--
I would like to look into
nce sufficient progress is made.
> >
> > On Wed, Jun 20, 2018 at 2:02 PM Pramod Immaneni <
> pramod.imman...@gmail.com>
> > wrote:
> >
> >> That would be awesome, it would be a good use case for the platform.
> >>
> >> On Wed,
gt;
> > +1. Apex does not have as large community as other Apache project, but
> > let's try to build it.
> >
> > Thank you,
> >
> > Vlad
> >
> > On 6/20/18 10:24, Pramod Immaneni wrote:
> > > Aaron,
> > >
> > > Your
e of the project? I really like the
> framework and definitely would prefer to use it as well as contribute
> back...just want to make sure I am not going to have work on it solo or
> worse, end up having to switch to something else later...
>
> Your thoughts?
>
> Aaron
>
>
> On 6/20/18 09:09, Pramod Immaneni wrote:
> > There are hadoop IPC calls are failing possibly because of its reliance
> on
> > kryo for serializing the payload and there is some incompatibility with
> the
> > new version. I will dig in more to see what is goin
There are hadoop IPC calls are failing possibly because of its reliance on
kryo for serializing the payload and there is some incompatibility with the
new version. I will dig in more to see what is going on.
On Tue, Jun 19, 2018 at 6:54 PM Aaron Bossert wrote:
> Pramod,
>
> Thanks for taking the
understand that is
> > something of a lift. By the way, Kryo 5 just came out yesterday, so if
> > there is to be effort expended, it might be good to go with the latest
> > version...though, heads up, I tried it out and there seem to be quite a
> few
> > changes
d see if
>> the errors were different...
>>
>> Sent from my iPhone
>>
>> On Jun 11, 2018, at 15:11, Pramod Immaneni
>> wrote:
>>
>> Aaron,
>>
>> The question might be best served on the dev@apex.apache.org mailing
>> list as you are st
[
https://issues.apache.org/jira/browse/APEXCORE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517710#comment-16517710
]
Pramod Immaneni commented on APEXCORE-817:
--
The test is failing because
Pramod Immaneni created APEXCORE-817:
Summary: StramLocalCluster.testDynamicLoading test failing on
travis
Key: APEXCORE-817
URL: https://issues.apache.org/jira/browse/APEXCORE-817
Project
[
https://issues.apache.org/jira/browse/APEXCORE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni resolved APEXCORE-807.
--
Resolution: Fixed
Fix Version/s: 4.0.0
> In secure mode containers
Do you see the same errors when you run the individual tests in question in
isolation, such as using mvn test -Dtest=. If you do can you
paste the full logs of what you see when the individual tests fail.
Thanks
On Mon, Jun 18, 2018 at 11:41 AM Aaron Bossert wrote:
> please disregard the first
pose the plan on action like this.
> >>>
> >>> 1. We develop the wrapper UI for apexCli in the first phase and
> give
> >>> user all the management options as REST APIs.
> >>> 2. If some of information we require are not in the current apexC
I too think that a comprehensive UI works better standalone but given that
stram already runs a webapp server, provides web services and RM provides a
proxy with mapped url space for it, we can extend stram to provide better
visual output. Overall I am +1 on the idea.
On Mon, Jun 11, 2018 at 8:59
Congratulations Chinmay.
On Thu, May 24, 2018 at 9:39 AM Thomas Weise wrote:
> The Apache Apex PMC is pleased to announce that Chinmay Kolhatkar is now a
> PMC member.
>
> Chinmay has contributed to Apex in many ways, including:
>
> - Various transform operators in Malhar
> - SQL translation bas
ple, so we might want to find a way to keep that alive.
>>
>>
>> On Wed, May 2, 2018 at 7:33 PM, Pramod Immaneni
>> wrote:
>>
>> I see a kafka 0.7.1. Not sure if it is still being used.
>>>
>>> Thanks
>>>
>>> On Wed, May 2, 2018
>
> Thanks,
> Thomas
>
>
> On Wed, May 2, 2018 at 6:53 PM, Pramod Immaneni
> wrote:
>
> > Hello Community,
> >
> > As you may know, DataTorrent was the original developer and initial
> > contributor of Apex. There are a couple of dependencies the pro
Hello Community,
As you may know, DataTorrent was the original developer and initial
contributor of Apex. There are a couple of dependencies the project still
has on DataTorrent.
One of them is the project netlet, hosted in DataTorrent github, that
provides a networking library for data transfer.
Dear Community,
The Apache Apex community is pleased to announce release 3.7.0 of Apex
Core (the
engine).
Apache Apex is an enterprise-grade big data-in-motion platform that unifies
stream and batch processing. Apex was built for scalability and low-latency
processing, high availability and opera
Yes Thomas will complete it in a day or two.
Thanks
On Tue, Apr 24, 2018 at 9:15 AM, Thomas Weise wrote:
> Hi Pramod,
>
> Are you going to complete the release?
>
> Thanks
>
>
> On Wed, Apr 18, 2018 at 9:31 PM, Pramod Immaneni
> wrote:
>
> > The vote conc
Pramod Immaneni created APEXCORE-810:
Summary: Concurrent modification exception during connection
cleanup in buffer server
Key: APEXCORE-810
URL: https://issues.apache.org/jira/browse/APEXCORE-810
> - build from source archive
> - tests pass
> - run pi demo on YARN 2.7.1
>
> When updating the download page after the release, please also remove the
> md5 links from it.
>
> Thanks,
> Thomas
>
>
> On Sat, Apr 14, 2018 at 11:48 AM, Pramod Immaneni
> wrote:
Pramod Immaneni created APEXCORE-809:
Summary: Documentation does not build with current versions
(8.11.x) of nodejs
Key: APEXCORE-809
URL: https://issues.apache.org/jira/browse/APEXCORE-809
Pramod Immaneni created APEXCORE-808:
Summary: Change min supported java version dependency to Java 8
Key: APEXCORE-808
URL: https://issues.apache.org/jira/browse/APEXCORE-808
Project: Apache Apex
[
https://issues.apache.org/jira/browse/APEXCORE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni updated APEXCORE-807:
-
Issue Type: Bug (was: Task)
> In secure mode containers are failing after one day
[
https://issues.apache.org/jira/browse/APEXCORE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442548#comment-16442548
]
Pramod Immaneni commented on APEXCORE-807:
--
This is happening because
Pramod Immaneni created APEXCORE-807:
Summary: In secure mode tokens containers are failing after one
day and the application is failing after seven days
Key: APEXCORE-807
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/APEXCORE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni updated APEXCORE-807:
-
Summary: In secure mode containers are failing after one day and the
application is
Updated master to 4.0.0-SNAPSHOT.
On Wed, Apr 11, 2018 at 5:04 PM, Pramod Immaneni
wrote:
> Will move this one to 4.0
>
> On Mon, Apr 9, 2018 at 11:19 AM, Pramod Immaneni
> wrote:
>
>> Can this be moved to the next release as it is not done
>>
>> https://issue
Dear community,
Please verify and vote.
Thanks
On Sun, Apr 15, 2018 at 8:45 AM, Pramod Immaneni
wrote:
> Hi,
>
> Regd [4][5], these are templates used to generate a base application
> project for users to modify and use when they run the maven archetype,
> which users can eve
re made Sun 15 Apr 01:21:20 2018 AEST
> gpg:using RSA key EB4B068AE51B20BFA40FDAA779480420239E728D
> gpg: requesting key 79480420239E728D from hkps server
> hkps.pool.sks-keyservers.net
> gpg: key 79480420239E728D: public key "Pramod Immaneni "
> importe
The old key was not used at all.
> On Apr 14, 2018, at 3:32 PM, Vlad Rozov wrote:
>
> Please fix the KEYS before proceeding with the vote.
>
> Thank you,
>
> Vlad
>
>> On 4/14/18 11:48, Pramod Immaneni wrote:
>> Dear Community,
>>
>> Ple
Dear Community,
Please vote on the following Apache Apex Core 3.7.0 release candidate.
This is a source release with binary artifacts published to Maven.
List of all issues fixed: https://s.apache.org/fWT8
User documentation: https://apex.apache.org/docs/apex-3.7/
Staging directory:
https://di
[
https://issues.apache.org/jira/browse/APEXCORE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni updated APEXCORE-755:
-
Fix Version/s: (was: 3.7.0)
4.0.0
> Deprecate dt.* propert
Will move this one to 4.0
On Mon, Apr 9, 2018 at 11:19 AM, Pramod Immaneni
wrote:
> Can this be moved to the next release as it is not done
>
> https://issues.apache.org/jira/browse/APEXCORE-755
>
> On Mon, Apr 9, 2018 at 8:32 AM, Pramod Immaneni
> wrote:
>
>> The
s described above),
> not removed.
>
>
>
>
>
> On 4/9/18 16:13, Pramod Immaneni wrote:
>
>> I lost my gpg key and had to generate a new one, folks please sign it when
>> you can.
>>
>> http://pgp.mit.edu/pks/lookup?op=get&search=0x79480420239E728D
>>
&
no branch created for *release versions* though.
>
> +1 for major version change
>
> On Mon, Apr 9, 2018 at 2:36 PM, Pramod Immaneni
> wrote:
>
> > git branch -a | grep release
> >
> > remotes/origin/release-3.0
> > remotes/origin/release-3.1
>
://apex.apache.org/release.html
Thanks
On Mon, Apr 9, 2018 at 1:45 PM, Vlad Rozov wrote:
> What was the reason to create the branch? Usually there is no branch
> created, only tag.
>
> Thank you,
>
> Vlad
>
>
> On 4/9/18 08:32, Pramod Immaneni wrote:
>
>> The branch rel
Also, since we will be changing min jdk version to 8 for next release, I am
fine with thomas's suggestion to change next version to 4.0. If there are
no objections I will update the version on master.
Thanks
On Mon, Apr 9, 2018 at 11:19 AM, Pramod Immaneni
wrote:
> Can this be move
Can this be moved to the next release as it is not done
https://issues.apache.org/jira/browse/APEXCORE-755
On Mon, Apr 9, 2018 at 8:32 AM, Pramod Immaneni
wrote:
> The branch release-3.7 has been created and master changed to
> 3.8.0-SNAPSHOT.
>
> On Fri, Apr 6, 2018 at 1:0
The branch release-3.7 has been created and master changed to
3.8.0-SNAPSHOT.
On Fri, Apr 6, 2018 at 1:03 PM, Pramod Immaneni
wrote:
> Now that this has been merged, I will cut the release branch over the
> weekend.
>
> Thanks
>
> On Fri, Mar 23, 2018 at 12:49 PM, T
Now that this has been merged, I will cut the release branch over the
weekend.
Thanks
On Fri, Mar 23, 2018 at 12:49 PM, Thomas Weise wrote:
> https://github.com/apache/apex-core/pull/583
>
>
> On Thu, Mar 22, 2018 at 1:47 PM, Pramod Immaneni
> wrote:
>
> > Is there a
[
https://issues.apache.org/jira/browse/APEXCORE-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni resolved APEXCORE-789.
--
Resolution: Fixed
Fix Version/s: 3.7.0
> Update security doc to describe
Is there anything folks would want to get merged before the release process
starts. Remember this would be the last release supporting Java 7.
Thanks
On Sat, Feb 24, 2018 at 5:16 AM, Pramod Immaneni
wrote:
> ok
>
> On Mon, Feb 19, 2018 at 1:30 PM, Thomas Weise wrote:
>
>> I
ok
On Mon, Feb 19, 2018 at 1:30 PM, Thomas Weise wrote:
> I think that should be done after the release, along with 4.x version
> change.
>
>
> On Mon, Feb 19, 2018 at 10:06 AM, Pramod Immaneni
> wrote:
>
> > Shall we move to Java 8 with this release
> >
&g
Shall we move to Java 8 with this release
On Wed, Jan 31, 2018 at 9:06 AM, Pramod Immaneni
wrote:
> I can do it if no one is volunteering.
>
> Thanks
>
> > On Jan 31, 2018, at 7:59 AM, Thomas Weise wrote:
> >
> > We are still looking for a volunteer to run the
;
> Vlad
>
> On 2/3/18 09:13, Pramod Immaneni wrote:
>> I too agree that the discussion has veered off from the original topic. Why
>> can't LIBRARY_JARS be used for this, albeit with a minor improvement?
>> Currently, our attribute layering is an overr
I too agree that the discussion has veered off from the original topic. Why
can't LIBRARY_JARS be used for this, albeit with a minor improvement?
Currently, our attribute layering is an override, so if you have an
attribute that is specified as apex.application..attr.
it overrides apex.attr. for th
;>>>
>>>>> - Chinmay.
>>>>>
>>>>> On 18 Jan 2018 8:58 pm, "Tushar Gosavi" wrote:
>>>>>
>>>>> +1 for the release
>>>>>>
>>>>>> Regards,
>>>>>> - Tush
Pramod Immaneni created APEXCORE-804:
Summary: Setting to let application know when DAG is not being
created for launch
Key: APEXCORE-804
URL: https://issues.apache.org/jira/browse/APEXCORE-804
gt;
> Thank you,
>
> Vlad
>
> On 1/19/18 11:36, Sanjay Pujare wrote:
>> Are they mutually exclusive? Otherwise "start supporting Java 9" doesn't
>> have to imply stopping Java 8 support. I think Vlad implied supporting both.
>>
>> Sanjay
Java 9 will shut people out as 8 is not yet eol. The majority of the
installations I have seen are running 8 and people are moving from 7 to 8.
Other projects in our space are also moving to 8.
> On Jan 19, 2018, at 8:31 AM, Vlad Rozov wrote:
>
> +1. It will be good to start supporting Java 9
+1
> On Jan 17, 2018, at 7:25 AM, Thomas Weise wrote:
>
> Last release was 3.6.0 in May and following issues are ready for release:
>
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.7.0%20AND%20project%20%3D%20APEXCORE%20ORDER%20BY%20status%20ASC
>
> Any opinions on cutting a
s
returned. It does not enforce nor rely that DAGs returned by multiple calls
to populateDAG be the same DAG.
>
> Thank you,
>
> Vlad
>
>
> On 12/21/17 10:05, Pramod Immaneni wrote:
>
>> Asking users to create plugins for something they want to do in their
>> ap
Gugale wrote:
> >
> >> +1
> >> Sometimes this context is required. We shouldn't change any default
> >> behaviour other than making this config available.
> >>
> >> -Priyanka
> >>
> >>
> >>
> >> On Wed, Dec 20,
[
https://issues.apache.org/jira/browse/APEXCORE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni resolved APEXCORE-801.
--
Resolution: Fixed
Fix Version/s: 3.7.0
> Committer guidelines for depende
;
> On 12/20/17 02:23, Priyanka Gugale wrote:
>
>> +1
>> Sometimes this context is required. We shouldn't change any default
>> behaviour other than making this config available.
>>
>> -Priyanka
>>
>>
>>
>> On Wed, Dec 20, 2017 at 5:32 AM, Pr
thing like file output operator would
work but not our db kind of operator. Both options could be supported in
the operator.
> Regarding not emitting stragglers until the next input arrives, can this
> not be accomplished using IdleTimeHandler?
>
> What is preventing the use of virtu
something that is more enforceable. So I like the
>> idea
>> of another method but that introduces incompatibility so may be in 4.0?
>>
>> On Tue, Dec 19, 2017 at 9:40 AM, Munagala Ramanath <
>> amberar...@yahoo.com.invalid> wrote:
>>
>> +1
>>&g
I have a mini proposal. The command get-app-package-info runs the
populateDAG method of an application to construct the DAG but does not
actually launch the DAG. An application developer does not know in which
context the populateDAG is being called. For example, if they are recording
application s
lt for a request submitted in the previous window. This
> also implies that idempotency cannot be guaranteed across runs of the same
> input data. In fact all threaded implementations have this issue as
> ordering of the results is not guaranteed to be unique even within a given
>
Hi Anath,
Sounds interesting and looks like you have put quite a bit of work on it.
Might I suggest changing the title of 2260 to better fit your proposal and
implementation, mainly so that there is differentiation from 2261.
I wanted to discuss the proposal to use multiple threads in an operator
[
https://issues.apache.org/jira/browse/APEXCORE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni reassigned APEXCORE-801:
Assignee: Pramod Immaneni
> Committer guidelines for dependency CVE failu
Pramod Immaneni created APEXCORE-801:
Summary: Committer guidelines for dependency CVE failures
Key: APEXCORE-801
URL: https://issues.apache.org/jira/browse/APEXCORE-801
Project: Apache Apex Core
[
https://issues.apache.org/jira/browse/APEXCORE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni resolved APEXCORE-790.
--
Resolution: Fixed
Fix Version/s: 3.7.0
> Enforce dependency analysis for
A bit delayed but nevertheless important announcement, Apache Apex PMC is
pleased to announce Tushar Gosavi as a new PMC member.
Tushar has been contributing to Apex from the beginning of the project and
has been working on the codebase for over 3 years. He is among the few who
have a wide breadth
facts that are published to maven including sql and contrib,
> the dependencies must be removed, upgraded/replaced or marked (as a last
> resort) as optional.
> >
> > Thank you,
> >
> > Vlad
> >
> > On 11/1/17 13:06, Pramod Immaneni wrote:
> >> If we go by
> On Thu, Nov 2, 2017 at 11:35 PM, Pramod Immaneni
> wrote:
>
> > If the PR introduces a CVE by all means lets fail it initally and later
> > look at whitelisting it if needed. Why fail all PRs that haven't caused
> the
> > problem. What happens when there are no PRs
ell as a set of artefacts in the project modules
> that summarise the community’s awareness of the issue.
>
>
> Regards
> Ananth
>
> > On 3 Nov 2017, at 8:38 am, Pramod Immaneni
> wrote:
> >
> > The question is which build? We can definitely make it a mandat
interested fixing the issues.
> >>
> >> Perhaps if after a CI failure the issue can be identified as
> pre-existing,
> >> we can whitelist and create a JIRA that must be addressed prior to the
> next
> >> release?
> >>
> >>
> >>
entire library as optional, somebody may
> use only one operator from the entire library.
>
> Thank you,
>
> Vlad
>
>
> On 11/1/17 12:49, Pramod Immaneni wrote:
>
>> I was thinking of it more in terms of optional that Justin mentioned
>> earlier.
>>
&
>
> > On 2 Nov 2017, at 6:10 am, Vlad Rozov wrote:
> >
> > It does not matter whether sql (and demos) is part of the main profile
> or not. It is a source release, not a binary release and source includes
> all profiles.
> >
> > Thank you,
> >
> >
ving/fixing those dependencies.
>>>
>>> Those were directly introduced in PRs. I am not against adding additional
>> checks that verify the PR better.
>>
> Right and it would be much better to catch the problem at the time it was
> introduced, but Category X list (a
profiles.
>
> Thank you,
>
> Vlad
>
>
> On 11/1/17 11:50, Pramod Immaneni wrote:
>
>> Vlad can you add this command to the release instructions and the
>> committer
>> guidelines. If we are unable to address this for this release, we can
>> consider movin
;>>>>>> ~ Bhupesh
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>>
>>>>>>> Bhupesh Chawda
>>>>>>>
>>>>>>>
st adding additional
checks that verify the PR better.
>
> Thank you,
>
> Vlad
>
>
> On 11/1/17 11:21, Pramod Immaneni wrote:
>
>> My original concern still remains. I think what you have is valuable but
>> would prefer that it be activated in an independent b
1 - 100 of 562 matches
Mail list logo
