Re: ignite-1.4 version is still "unreleased" in Jira

I released "ignite-1.4". And also removed "1.5". Who created it? Why not rename "ignite-1.5"? --Yakov 2015-10-07 19:28 GMT+03:00 Konstantin Boudnik <c...@apache.org>: > Techically it should be the RM. I am looking through the website and wiki

Re: ignite-1.4 version is still "unreleased" in Jira

gt; On Thu, Oct 8, 2015 at 7:31 AM, Yakov Zhdanov <yzhda...@apache.org> >> wrote: >> >> > I released "ignite-1.4". >> > >> > And also removed "1.5". Who created it? Why not rename "ignite-1.5"? >> > >> >

Re: ignite-1.4 version is still "unreleased" in Jira

This is very easy. >> >> --Yakov >> >> 2015-10-08 17:35 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: >> >>> On Thu, Oct 8, 2015 at 7:31 AM, Yakov Zhdanov <yzhda...@apache.org> >>> wrote: >>> >>> > I released

Re: ignite-1.4 version is still "unreleased" in Jira

On Thu, Oct 8, 2015 at 7:31 AM, Yakov Zhdanov <yzhda...@apache.org> wrote: > I released "ignite-1.4". > > And also removed "1.5". Who created it? Why not rename "ignite-1.5"? > Yakov, there was discussion to remove "ignite" word from all

ignite-1.4 version is still "unreleased" in Jira

Hi Igniters, 1.4 has been released, but Jira shows "ignite-1.4" version as "unreleased". Can anyone with corresponding rights please fix this? Thanks, -- -- Pavel Tupitsyn GridGain Systems, Inc. www.gridgain.com

Re: ignite-1.4 version is still "unreleased" in Jira

Tupitsyn wrote: > Hi Igniters, > > 1.4 has been released, but Jira shows "ignite-1.4" version as "unreleased". > Can anyone with corresponding rights please fix this? > > Thanks, > > -- > -- > Pavel Tupitsyn > GridGain Systems, Inc. > www.gridgain.com

Re: ignite 1.4 status

Alexey, I have been running Vert.x cluster manager tests today. IGNITE-1171 doesn't reproduces anymore. But new problem was found: https://issues.apache.org/jira/browse/IGNITE-1534 I'll try to create Ignite test for this problem. I hope you have some ideas about how to reproduce (stable) and

Re: ignite 1.4 status

Alex, I merged 1171 to 1.4 branch. We have very few tickets left. Guys, who is in charge of checking this - https://issues.apache.org/jira/browse/IGNITE-973? Please provide the update? Hopefully, we will release tomorrow. Thanks! --Yakov 2015-09-23 8:37 GMT+03:00 Alexey Goncharuk

Re: ignite 1.4 status

I'm working to reproduce IGNITE-973 On Wed, Sep 23, 2015 at 7:35 PM, Yakov Zhdanov wrote: > Alex, I merged 1171 to 1.4 branch. > > We have very few tickets left. > > Guys, who is in charge of checking this - > https://issues.apache.org/jira/browse/IGNITE-973? Please provide

Re: ignite 1.4 status

I couldn't reproduce IGNITE-973 but would like to get a comment from the reporter. Maybe some points for testing of issue have been missed by me... On Wed, Sep 23, 2015 at 8:48 PM, Sergey Kozlov wrote: > I'm working to reproduce IGNITE-973 > > On Wed, Sep 23, 2015 at 7:35

Re: ignite 1.4 status

Alex, I spent some time debugging this today. I noticed that we do not verify that topology version of the custom message is identical to current ring version. After I added this condition test started passing. However, it hangs from time to time since custom message gets discarded before it gets

Re: ignite 1.4 status

Igniters, While working on ignite-1171 we discovered couple more issues in discovery that might have threaten custom events processing under some circumstances (we have continuous processes based on this logic, for example). Alexey Goncharuk has picked this up. Another critical issue discovered

Re: ignite 1.4 status

Alex, I think it makes sense to continue investigating this. We can discuss whether we include or skip the fix once fix is ready. As far as other tickets:

Re: ignite 1.4 status

Guys, I want to update release status. Testing has revealed some cache issues which should be fixed with the release. Moreover, it turned out that these issues block vert.x release. So, if we fix them we can consider including vert.x into 1.4 release. Which is good I think. I think that Alex

Re: ignite 1.4 status

Yakov, Igniters, I have found at least one issue related to ignite-1171 hang, it is caused by a race between discovery custom message and collectDiscoveryData() call (updated the ticket). I remember we wanted to call collectDiscoveryData() during the NodeAddFinishedMessage processing, however it

Re: ignite 1.4 status

On Tue, Sep 15, 2015 at 6:50 PM, Dmitriy Setrakyan wrote: > Raul, should we have any documentation for these features on readme.io? > Sure, do I have access? (if I do, I've forgotten, sorry!) *Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect,

Re: ignite 1.4 status

l > request (updated yesterday). I had to update it today because in the last > days some commit in master caused a conflict. So I would appreciate it if > you could merge it to master @ ASF (and perhaps to ignite-1.4 if you'd like > to release MQTT in 1.4) soon so I don't have to ke

Re: ignite 1.4 status

Guys, Current status is the following: 1. Sam needs to merge his fixes after TC is finished. 2. Some minor changes pending from Denis + release notes fix pointed by Dmitry. 3. Several suites are still red on TC I have moved plenty of tickets to ignite-1.5. Here is the link to currently open

[jira] [Created] (IGNITE-1396) Remove platforms from public API for ignite-1.4.

Vladimir Ozerov created IGNITE-1396: --- Summary: Remove platforms from public API for ignite-1.4. Key: IGNITE-1396 URL: https://issues.apache.org/jira/browse/IGNITE-1396 Project: Ignite

Re: Removing ignite-1.4 branch.

to > build and test the platform integration (C++ and .NET), so others can play > with it a bit before we take such drastic measures? > > D. > > On Wed, Sep 9, 2015 at 3:40 AM, Vladimir Ozerov <voze...@gridgain.com> > wrote: > > > Folks, > > > > P

Re: Removing ignite-1.4 branch.

gt; Folks, > > Platforms integration is almost ready and I think it fits ignite-1.4 > release. For this reason I'd like to merge the branch ignite-1.4 to master, > then remove it and recreate from master again in the nearest time, as soon > as our release deadlines are finally established.

Re: Removing ignite-1.4 branch.

> > > > D. > > > > On Wed, Sep 9, 2015 at 3:40 AM, Vladimir Ozerov <voze...@gridgain.com> > > wrote: > > > > > Folks, > > > > > > Platforms integration is almost ready and I think it fits ignite-1.4 > > > release. For this reason I

Re: Ignite 1.4

Seems worth specify "None" fixversion instead of 1.5. Thoughts? On Mon, Sep 7, 2015 at 2:50 PM, Sergey Kozlov wrote: > Guys > > We still have unclosed/unresolved more than 100 issues. > Could you review issues assigned on you and move then on next release (1.5) > if it

Re: Ignite 1.4

I'm ok On Mon, Sep 7, 2015 at 3:31 PM, Anton Vinogradov wrote: > Seems worth specify "None" fixversion instead of 1.5. > Thoughts? > > On Mon, Sep 7, 2015 at 2:50 PM, Sergey Kozlov > wrote: > > > Guys > > > > We still have unclosed/unresolved

Re: Ignite 1.4

Guys We still have unclosed/unresolved more than 100 issues. Could you review issues assigned on you and move then on next release (1.5) if it won't be done for 1.4? Thanks! On Fri, Sep 4, 2015 at 3:24 PM, Vladimir Ozerov wrote: > Please disregard p.2 and p.3 as they are

Re: Ignite 1.4

I would introduce new version "pending". This way we can distinguish newly filed tickets (version default), postponed tickets (pending) and scheduled ones (e.g. 1.4) Thoughts? Thanks! Yakov On Sep 7, 2015 15:31, "Anton Vinogradov" wrote: > Seems worth specify "None"

Re: Ignite 1.4

Sounds good On Mon, Sep 7, 2015 at 4:16 PM, Yakov Zhdanov wrote: > I would introduce new version "pending". This way we can distinguish newly > filed tickets (version default), postponed tickets (pending) and scheduled > ones (e.g. 1.4) > > Thoughts? > > Thanks! > > Yakov >

Re: Ignite 1.4

Please disregard p.2 and p.3 as they are out of Ignite scope. On Fri, Sep 4, 2015 at 3:23 PM, Vladimir Ozerov wrote: > Done. > 1) No changes from my side to Ignite. > 2) Added missing enterprise release notes for 7.3.3. > 3) Updated enterprise release notes for 7.4.1. > >

Re: Ignite 1.4

Of course, we will release ignite-1.4.0. Anton V, can you please fix? --Yakov 2015-09-04 12:50 GMT+03:00 Sergey Kozlov : > Igniters, > > Current version in released branch is 1.4.1 (there were issues related to > update notifier but it fixed now). Make sense to change to

Re: Ignite 1.4

Done. 1) No changes from my side to Ignite. 2) Added missing enterprise release notes for 7.3.3. 3) Updated enterprise release notes for 7.4.1. On Fri, Sep 4, 2015 at 2:46 PM, Yakov Zhdanov wrote: > Guys, I have updated release notes (IGNITE_HOME/RELEASE_NOTES.txt). I think

Re: Ignite 1.4

Igniters, Current version in released branch is 1.4.1 (there were issues related to update notifier but it fixed now). Make sense to change to 1.4.0? On Fri, Sep 4, 2015 at 12:05 PM, Yakov Zhdanov wrote: > Guys, > > We need to postpone release due to TC state. I think it

Re: Ignite 1.4

On Thu, Sep 3, 2015 at 1:31 AM, Sergey Kozlov wrote: > Could someone provide the list of key features (fixes) added for release > 1.4? > I would also like to see the release notes for 1.4. Also, is the release still happening tomorrow? How close are we? > > > On Wed,

Re: Ignite 1.4

Could someone provide the list of key features (fixes) added for release 1.4? On Wed, Sep 2, 2015 at 3:51 PM, Yakov Zhdanov wrote: > Yes, we will be moving almost all the issues to further versions. > > Branch has already been created. > > --Yakov > > 2015-09-01 22:14

Re: Ignite 1.4

Yes, we will be moving almost all the issues to further versions. Branch has already been created. --Yakov 2015-09-01 22:14 GMT+03:00 Branko Čibej : > On 01.09.2015 20:46, Konstantin Boudnik wrote: > > On Tue, Sep 01, 2015 at 08:45PM, Sergey Kozlov wrote: > >> FYI: We've at

Re: Ignite 1.4

FYI: We've at least 161 unclosed issues planned to fix in version 1.4 On Tue, Sep 1, 2015 at 11:48 AM, Vladimir Ozerov <voze...@gridgain.com> wrote: > I'm going to create a branch "ignite-1.4" for this release from master. > Please let me know if anyone has concerns. &g

Re: Ignite 1.4

Ozerov <voze...@gridgain.com> > wrote: > > > I'm going to create a branch "ignite-1.4" for this release from master. > > Please let me know if anyone has concerns. > > > > On Mon, Aug 31, 2015 at 9:10 PM, Konstantin Boudnik <c...@apache.org> > >

Re: Ignite 1.4

On 01.09.2015 20:46, Konstantin Boudnik wrote: > On Tue, Sep 01, 2015 at 08:45PM, Sergey Kozlov wrote: >> FYI: We've at least 161 unclosed issues planned to fix in version 1.4 > If there're so many issues to go - perhaps it makes sense not to branch out > this early to avoid extra merges? Or

Re: Ignite 1.4

I'm going to create a branch "ignite-1.4" for this release from master. Please let me know if anyone has concerns. On Mon, Aug 31, 2015 at 9:10 PM, Konstantin Boudnik <c...@apache.org> wrote: > On Mon, Aug 31, 2015 at 08:08PM, Branko Čibej wrote: > > On 31.08.2015 20:06,

Re: Ignite 1.4

Yakov, Thanks for clarification - that makes sense. the filter doesn't seem to be shared. Also, if you safe a filter in JIRA, the URL will be real short as it only would include filter id. Cos On Mon, Aug 31, 2015 at 09:38AM, Yakov Zhdanov wrote: > Thanks for clarification, Cos. Of course, I

Re: Ignite 1.4

On Mon, Aug 31, 2015 at 08:08PM, Branko Čibej wrote: > On 31.08.2015 20:06, Konstantin Boudnik wrote: > > Submitting for vote and releasing are two different events. The release date > > is when the vote is closed and its tally is counted. > > Heh, actually, the release date is when the release

Re: Ignite 1.4

Guys, Here is the correct link to jira issues that should work for everyone -

Re: Ignite 1.4

Agree with Brane, let's always release on Monday. On Mon, Aug 31, 2015 at 4:33 PM, Branko Čibej wrote: > On 31.08.2015 08:14, Konstantin Boudnik wrote: > > On Mon, Aug 31, 2015 at 01:29AM, Yakov Zhdanov wrote: > >> Igniters, > >> > >> I think we have got to the point to start