Igniters,
I think we have got to the point to start finalization of 1.4 release. It contains many important fixes and several new features (e.g. secure communication). One more point - this will be our first release as top level project. The complete list of issues closed/resolved on 1.4 is here: https://issues.apache.org/jira/issues/?filter=12333035&jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC Let's do the following: 1. Make sure TC is green 2. Run final benchmarks to make sure that there is no drop 3. Make sure that documentation for all features is on the website It will be perfect if we can release on Fri Sep 4th. By the way, I don't see ticket for secure communication here, but I know for sure we added this feature. Who was in charge of it? Nick Tikhonov is it you? Vladimir Ozerov, I see quiet a lot of .Net related tickets closed on 1.4. Are changes really in master? If not please move tickets on further version. I will update release notes on Wed, when I come back to Saint Petersburg. Please let me know if anyone have questions. --Yakov |
Migration of GridGain platforms to Ignite happens as a bunch of small
tickets. Every ticket is merged to master as soon as it is finished. So yes, all closed tickets for 1.4 is really in master. On Mon, Aug 31, 2015 at 1:29 AM, Yakov Zhdanov <[hidden email]> wrote: > Igniters, > > I think we have got to the point to start finalization of 1.4 release. > > It contains many important fixes and several new features (e.g. secure > communication). One more point - this will be our first release as top > level project. > > The complete list of issues closed/resolved on 1.4 is here: > > https://issues.apache.org/jira/issues/?filter=12333035&jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > Let's do the following: > > 1. Make sure TC is green > 2. Run final benchmarks to make sure that there is no drop > 3. Make sure that documentation for all features is on the website > > It will be perfect if we can release on Fri Sep 4th. > > By the way, I don't see ticket for secure communication here, but I know > for sure we added this feature. Who was in charge of it? Nick Tikhonov is > it you? > > Vladimir Ozerov, I see quiet a lot of .Net related tickets closed on 1.4. > Are changes really in master? If not please move tickets on further > version. > > I will update release notes on Wed, when I come back to Saint Petersburg. > > Please let me know if anyone have questions. > > --Yakov > |
In reply to this post by yzhdanov
On Mon, Aug 31, 2015 at 01:29AM, Yakov Zhdanov wrote:
> Igniters, > > I think we have got to the point to start finalization of 1.4 release. > > It contains many important fixes and several new features (e.g. secure > communication). One more point - this will be our first release as top > level project. > > The complete list of issues closed/resolved on 1.4 is here: > https://issues.apache.org/jira/issues/?filter=12333035&jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > Let's do the following: > > 1. Make sure TC is green > 2. Run final benchmarks to make sure that there is no drop > 3. Make sure that documentation for all features is on the website > > It will be perfect if we can release on Fri Sep 4th. Here's the calculation: 9/4 - 72 hours of the vote = 9/1 Hence, the RC should be in the vote on Tuesday hence the release will go without much of the testing by the community, right? > By the way, I don't see ticket for secure communication here, but I know > for sure we added this feature. Who was in charge of it? Nick Tikhonov is > it you? > > Vladimir Ozerov, I see quiet a lot of .Net related tickets closed on 1.4. > Are changes really in master? If not please move tickets on further version. > > I will update release notes on Wed, when I come back to Saint Petersburg. > > Please let me know if anyone have questions. > > --Yakov |
Thanks for clarification, Cos. Of course, I meant to have RC ready on Fri.
On Aug 31, 2015 09:13, "Konstantin Boudnik" <[hidden email]> wrote: > On Mon, Aug 31, 2015 at 01:29AM, Yakov Zhdanov wrote: > > Igniters, > > > > I think we have got to the point to start finalization of 1.4 release. > > > > It contains many important fixes and several new features (e.g. secure > > communication). One more point - this will be our first release as top > > level project. > > > > The complete list of issues closed/resolved on 1.4 is here: > > > https://issues.apache.org/jira/issues/?filter=12333035&jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > > Let's do the following: > > > > 1. Make sure TC is green > > 2. Run final benchmarks to make sure that there is no drop > > 3. Make sure that documentation for all features is on the website > > > > It will be perfect if we can release on Fri Sep 4th. > > Here's the calculation: 9/4 - 72 hours of the vote = 9/1 Hence, the RC > should > be in the vote on Tuesday hence the release will go without much of the > testing by the community, right? > > > By the way, I don't see ticket for secure communication here, but I know > > for sure we added this feature. Who was in charge of it? Nick Tikhonov is > > it you? > > > > Vladimir Ozerov, I see quiet a lot of .Net related tickets closed on 1.4. > > Are changes really in master? If not please move tickets on further > version. > > > > I will update release notes on Wed, when I come back to Saint Petersburg. > > > > Please let me know if anyone have questions. > > > > --Yakov > |
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 meant to have RC ready on Fri. > On Aug 31, 2015 09:13, "Konstantin Boudnik" <[hidden email]> wrote: > > > On Mon, Aug 31, 2015 at 01:29AM, Yakov Zhdanov wrote: > > > Igniters, > > > > > > I think we have got to the point to start finalization of 1.4 release. > > > > > > It contains many important fixes and several new features (e.g. secure > > > communication). One more point - this will be our first release as top > > > level project. > > > > > > The complete list of issues closed/resolved on 1.4 is here: > > > > > https://issues.apache.org/jira/issues/?filter=12333035&jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > > > > Let's do the following: > > > > > > 1. Make sure TC is green > > > 2. Run final benchmarks to make sure that there is no drop > > > 3. Make sure that documentation for all features is on the website > > > > > > It will be perfect if we can release on Fri Sep 4th. > > > > Here's the calculation: 9/4 - 72 hours of the vote = 9/1 Hence, the RC > > should > > be in the vote on Tuesday hence the release will go without much of the > > testing by the community, right? > > > > > By the way, I don't see ticket for secure communication here, but I know > > > for sure we added this feature. Who was in charge of it? Nick Tikhonov is > > > it you? > > > > > > Vladimir Ozerov, I see quiet a lot of .Net related tickets closed on 1.4. > > > Are changes really in master? If not please move tickets on further > > version. > > > > > > I will update release notes on Wed, when I come back to Saint Petersburg. > > > > > > Please let me know if anyone have questions. > > > > > > --Yakov > > |
In reply to this post by yzhdanov
Guys,
One immediate post-graduation change is removing the word "incubating" from the produced source, maven, and binary artifacts. I filed a ticket for it here: https://issues.apache.org/jira/browse/IGNITE-1330 Anton, given that you are an expert in the build, would be great if you could pick it up. Thanks, D. On Mon, Aug 31, 2015 at 12:29 AM, Yakov Zhdanov <[hidden email]> wrote: > Igniters, > > I think we have got to the point to start finalization of 1.4 release. > > It contains many important fixes and several new features (e.g. secure > communication). One more point - this will be our first release as top > level project. > > The complete list of issues closed/resolved on 1.4 is here: > > https://issues.apache.org/jira/issues/?filter=12333035&jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > Let's do the following: > > 1. Make sure TC is green > 2. Run final benchmarks to make sure that there is no drop > 3. Make sure that documentation for all features is on the website > > It will be perfect if we can release on Fri Sep 4th. > > By the way, I don't see ticket for secure communication here, but I know > for sure we added this feature. Who was in charge of it? Nick Tikhonov is > it you? > > Vladimir Ozerov, I see quiet a lot of .Net related tickets closed on 1.4. > Are changes really in master? If not please move tickets on further > version. > > I will update release notes on Wed, when I come back to Saint Petersburg. > > Please let me know if anyone have questions. > > --Yakov > |
In reply to this post by Konstantin Boudnik-2
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 finalization of 1.4 release. >> >> It contains many important fixes and several new features (e.g. secure >> communication). One more point - this will be our first release as top >> level project. >> >> The complete list of issues closed/resolved on 1.4 is here: >> https://issues.apache.org/jira/issues/?filter=12333035&jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC >> >> Let's do the following: >> >> 1. Make sure TC is green >> 2. Run final benchmarks to make sure that there is no drop >> 3. Make sure that documentation for all features is on the website >> >> It will be perfect if we can release on Fri Sep 4th. > Here's the calculation: 9/4 - 72 hours of the vote = 9/1 Hence, the RC should > be in the vote on Tuesday hence the release will go without much of the > testing by the community, right? Plus 24 hours for mirrors to catch up. And a side note: a Friday release? Really? :) -- Brane |
Agree with Brane, let's always release on Monday.
On Mon, Aug 31, 2015 at 4:33 PM, Branko Čibej <[hidden email]> 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 finalization of 1.4 release. > >> > >> It contains many important fixes and several new features (e.g. secure > >> communication). One more point - this will be our first release as top > >> level project. > >> > >> The complete list of issues closed/resolved on 1.4 is here: > >> > https://issues.apache.org/jira/issues/?filter=12333035&jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > >> > >> Let's do the following: > >> > >> 1. Make sure TC is green > >> 2. Run final benchmarks to make sure that there is no drop > >> 3. Make sure that documentation for all features is on the website > >> > >> It will be perfect if we can release on Fri Sep 4th. > > Here's the calculation: 9/4 - 72 hours of the vote = 9/1 Hence, the RC > should > > be in the vote on Tuesday hence the release will go without much of the > > testing by the community, right? > > Plus 24 hours for mirrors to catch up. > > And a side note: a Friday release? Really? :) > > -- Brane > > -- Alexey Kuznetsov GridGain Systems www.gridgain.com |
In reply to this post by Branko Čibej
Guys,
Here is the correct link to jira issues that should work for everyone - https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC Brane, if we are ready on Friday I would prefer to submit the build for vote immediately. If not, Monday is still fine. Thanks! -- Yakov > Plus 24 hours for mirrors to catch up. > > And a side note: a Friday release? Really? :) > > -- Brane > > |
Dmitriy,
I've fixed sources and made test release. Result can be checked here https://dist.apache.org/repos/dist/release/ignite/2.2.2-test/ On Mon, Aug 31, 2015 at 2:29 PM, Yakov Zhdanov <[hidden email]> wrote: > Guys, > > Here is the correct link to jira issues that should work for everyone - > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > Brane, if we are ready on Friday I would prefer to submit the build for > vote immediately. If not, Monday is still fine. > > Thanks! > -- > Yakov > > > > > Plus 24 hours for mirrors to catch up. > > > > And a side note: a Friday release? Really? :) > > > > -- Brane > > > > > |
In reply to this post by yzhdanov
On Mon, Aug 31, 2015 at 4:29 AM, Yakov Zhdanov <[hidden email]> wrote:
> Guys, > > Here is the correct link to jira issues that should work for everyone - > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > Yakov, any chance you can create a saved named filter? As Cos suggested, saved filters are easier to manage. > Brane, if we are ready on Friday I would prefer to submit the build for > vote immediately. If not, Monday is still fine. > > Thanks! > -- > Yakov > > > > > Plus 24 hours for mirrors to catch up. > > > > And a side note: a Friday release? Really? :) > > > > -- Brane > > > > > |
In reply to this post by Anton Vinogradov
On Mon, Aug 31, 2015 at 4:56 AM, Anton Vinogradov <[hidden email]>
wrote: > Dmitriy, > I've fixed sources and made test release. > Result can be checked here > https://dist.apache.org/repos/dist/release/ignite/2.2.2-test/ > > Thanks for quick turn around! > > On Mon, Aug 31, 2015 at 2:29 PM, Yakov Zhdanov <[hidden email]> > wrote: > > > Guys, > > > > Here is the correct link to jira issues that should work for everyone - > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > > Brane, if we are ready on Friday I would prefer to submit the build for > > vote immediately. If not, Monday is still fine. > > > > Thanks! > > -- > > Yakov > > > > > > > > > Plus 24 hours for mirrors to catch up. > > > > > > And a side note: a Friday release? Really? :) > > > > > > -- Brane > > > > > > > > > |
In reply to this post by yzhdanov
Submitting for vote and releasing are two different events. The release date
is when the vote is closed and its tally is counted. Cos On Mon, Aug 31, 2015 at 02:29PM, Yakov Zhdanov wrote: > Guys, > > Here is the correct link to jira issues that should work for everyone - > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > Brane, if we are ready on Friday I would prefer to submit the build for > vote immediately. If not, Monday is still fine. > > Thanks! > -- > Yakov > > > > > Plus 24 hours for mirrors to catch up. > > > > And a side note: a Friday release? Really? :) > > > > -- Brane > > > > |
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 is announced. :) Which is typically after it's on all the mirrors, heh. -- Brane > On Mon, Aug 31, 2015 at 02:29PM, Yakov Zhdanov wrote: >> Guys, >> >> Here is the correct link to jira issues that should work for everyone - >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC >> >> Brane, if we are ready on Friday I would prefer to submit the build for >> vote immediately. If not, Monday is still fine. >> >> Thanks! >> -- >> Yakov >> >> >> >>> Plus 24 hours for mirrors to catch up. >>> >>> And a side note: a Friday release? Really? :) >>> >>> -- Brane >>> >>> |
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 is announced. :) > Which is typically after it's on all the mirrors, heh. Yeah, you right - sorry for the confusion ;) > > -- Brane > > > On Mon, Aug 31, 2015 at 02:29PM, Yakov Zhdanov wrote: > >> Guys, > >> > >> Here is the correct link to jira issues that should work for everyone - > >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > >> > >> Brane, if we are ready on Friday I would prefer to submit the build for > >> vote immediately. If not, Monday is still fine. > >> > >> Thanks! > >> -- > >> Yakov > >> > >> > >> > >>> Plus 24 hours for mirrors to catch up. > >>> > >>> And a side note: a Friday release? Really? :) > >>> > >>> -- Brane > >>> > >>> > |
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 <[hidden email]> wrote: > 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 is announced. :) > > Which is typically after it's on all the mirrors, heh. > > Yeah, you right - sorry for the confusion ;) > > > > > -- Brane > > > > > On Mon, Aug 31, 2015 at 02:29PM, Yakov Zhdanov wrote: > > >> Guys, > > >> > > >> Here is the correct link to jira issues that should work for everyone > - > > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > >> > > >> Brane, if we are ready on Friday I would prefer to submit the build > for > > >> vote immediately. If not, Monday is still fine. > > >> > > >> Thanks! > > >> -- > > >> Yakov > > >> > > >> > > >> > > >>> Plus 24 hours for mirrors to catch up. > > >>> > > >>> And a side note: a Friday release? Really? :) > > >>> > > >>> -- Brane > > >>> > > >>> > > > |
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 <[hidden email]> 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 <[hidden email]> > wrote: > > > 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 is announced. :) > > > Which is typically after it's on all the mirrors, heh. > > > > Yeah, you right - sorry for the confusion ;) > > > > > > > > -- Brane > > > > > > > On Mon, Aug 31, 2015 at 02:29PM, Yakov Zhdanov wrote: > > > >> Guys, > > > >> > > > >> Here is the correct link to jira issues that should work for > everyone > > - > > > >> > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > >> > > > >> Brane, if we are ready on Friday I would prefer to submit the build > > for > > > >> vote immediately. If not, Monday is still fine. > > > >> > > > >> Thanks! > > > >> -- > > > >> Yakov > > > >> > > > >> > > > >> > > > >>> Plus 24 hours for mirrors to catch up. > > > >>> > > > >>> And a side note: a Friday release? Really? :) > > > >>> > > > >>> -- Brane > > > >>> > > > >>> > > > > > > |
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? Cos > On Tue, Sep 1, 2015 at 11:48 AM, Vladimir Ozerov <[hidden email]> > 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 <[hidden email]> > > wrote: > > > > > 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 is announced. :) > > > > Which is typically after it's on all the mirrors, heh. > > > > > > Yeah, you right - sorry for the confusion ;) > > > > > > > > > > > -- Brane > > > > > > > > > On Mon, Aug 31, 2015 at 02:29PM, Yakov Zhdanov wrote: > > > > >> Guys, > > > > >> > > > > >> Here is the correct link to jira issues that should work for > > everyone > > > - > > > > >> > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20AND%20(status%20%3D%20resolved%20or%20status%20%3D%20closed)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > > >> > > > > >> Brane, if we are ready on Friday I would prefer to submit the build > > > for > > > > >> vote immediately. If not, Monday is still fine. > > > > >> > > > > >> Thanks! > > > > >> -- > > > > >> Yakov > > > > >> > > > > >> > > > > >> > > > > >>> Plus 24 hours for mirrors to catch up. > > > > >>> > > > > >>> And a side note: a Friday release? Really? :) > > > > >>> > > > > >>> -- Brane > > > > >>> > > > > >>> > > > > > > > > > |
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 just go ahead and release 1.4 and get those issues addressed in 1.5. It's not as if skipping a "planned to fix" issue would be the end of the world. -- Brane |
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 <[hidden email]>: > 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 just go ahead and release 1.4 and get those issues addressed in 1.5. > It's not as if skipping a "planned to fix" issue would be the end of > the world. > > -- Brane > > |
Free forum by Nabble | Edit this page |