Hi devs,
I've noticed that we are providing 4 different version lines (1.1.x, 1.0.x,
0.10.x, 0.9.x) in download page, and I expect we will add one more for
1.2.0. Moreover, we have one more develop version line (2.0.0 - master)
which most of development happens there.
Recently we're releasing 3 v
+1 to maintain 3 version lines.
I think the next focus should be 2.0.0 than 1.3.0.
On 2/12/18, 11:40 PM, "Jungtaek Lim" wrote:
>Hi devs,
>
>I've noticed that we are providing 4 different version lines (1.1.x, 1.0.x,
>0.10.x, 0.9.x) in download page, and I expect we will add one more for
>1.2
+1 to maintaining 3 version lines as suggested by Jungtaek.
On 2/13/18, 9:51 AM, "Arun Iyer on behalf of Arun Mahadevan"
wrote:
+1 to maintain 3 version lines.
I think the next focus should be 2.0.0 than 1.3.0.
On 2/12/18, 11:40 PM, "Jungtaek Lim" wrote:
+1 (non binding) to maintaining less version lines, provided that
1.2.x branch is maintained long enough to allow progressive adoption
of 2.x
Alexandre Vermeerbergen
2018-02-13 19:38 GMT+01:00 Priyank Shah :
> +1 to maintaining 3 version lines as suggested by Jungtaek.
>
> On 2/13/18, 9:51 AM, "
+1 to maintain 3 version lines. Let’s properly announce that in our portal and
users list such that users know what’s coming.
Agree with focusing on 2.0 which has a lot of improvements, rather than 1.x, x
>= 3.
> On Feb 13, 2018, at 10:43 AM, Alexandre Vermeerbergen
> wrote:
>
> +1 (non bind
+1 to maintain 3 version lines, though we may want to look at what we can
do for storm mesos, which I think it currently stuck on 1.0.x.
2018-02-13 20:17 GMT+01:00 Hugo Da Cruz Louro :
> +1 to maintain 3 version lines. Let’s properly announce that in our portal
> and users list such that users kn
Thanks for keeping storm-mesos in mind Stig. :) I'd be most worried about
any issues we might see with the backported storm-kafka-client and how we
*might* need to fix bugs in 1.0.x. At least it should be easy to
cherry-pick fixes back into 1.0.x after the backport-stomping of STORM-2937.
Look f
We're in discussion to split out storm-kafka-client to have separate
release version and cycle. Since we have applied necessary changes to
storm-core of 1.1.x/1.0.x, unless storm-kafka-client needs more changes on
storm-core, storm-core 1.1.x/1.0.x should be compatible with
storm-kafka-client be co
This (3 version lines) is effectively what we’ve been doing — when a new
version comes out major/minor version comes out, we stop updating/supporting
the oldest previous version. For example, if we release 2.0 or 1.3
(hypothetical), we would EOL 1.0.x. In some cases, like a security
vulnerabili
As part of the release process I updated the download page [1] to move older
releases to archive.a.o as requested by INFRA. I also removed the “Current
Release” sections for 0.9.x and 0.10.x to make it more clear that those lines
are no longer supported.
If we want to add a more explicit statem
Did download page being reverted only from published site? I can see
release notes are published (so I guess gitpubsub works well) but download
page doesn't represent current storm-site. Is it due to LGPL issue on Storm
1.2.0?
2018년 2월 17일 (토) 오전 2:18, P. Taylor Goetz 님이 작성:
> As part of the rele
11 matches
Mail list logo
