You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fluo.apache.org by Keith Turner <ke...@deenlo.com> on 2017/12/01 18:56:06 UTC
[DISCUSS] 1.2.0 release
I think it would be good to start working towards a 1.2.0 release.
Does anyone have any outstanding issues they would like to see in
1.2.0?
Also, I am thinking of running the following test for 1.2.0.
* Run stress test for 24 hours on multiple nodes on EC2 (use YARN to run)
* Run webindex for 24 hours on multiple nodes on EC2 (use Mesos+Docker to run)
* Develop some test that stresses the new read lock feature and run
it for 24 hours
Are there other test we should run for 1.2.0?
Keith
Re: [DISCUSS] 1.2.0 release
Posted by Mike Walch <mw...@apache.org>.
I think 1.2.0 release would be great. I have no outstanding issues. I am
going to start running some tests this week.
On Fri, Dec 1, 2017 at 1:56 PM Keith Turner <ke...@deenlo.com> wrote:
> I think it would be good to start working towards a 1.2.0 release.
> Does anyone have any outstanding issues they would like to see in
> 1.2.0?
>
> Also, I am thinking of running the following test for 1.2.0.
>
> * Run stress test for 24 hours on multiple nodes on EC2 (use YARN to run)
> * Run webindex for 24 hours on multiple nodes on EC2 (use Mesos+Docker to
> run)
> * Develop some test that stresses the new read lock feature and run
> it for 24 hours
>
> Are there other test we should run for 1.2.0?
>
> Keith
>
Re: [DISCUSS] 1.2.0 release
Posted by Christopher <ct...@apache.org>.
I don't know about testing, but I think a 1.2.0 would be good to get out
there. I know there's been lots of improvements.
On Fri, Dec 1, 2017 at 1:56 PM Keith Turner <ke...@deenlo.com> wrote:
> I think it would be good to start working towards a 1.2.0 release.
> Does anyone have any outstanding issues they would like to see in
> 1.2.0?
>
> Also, I am thinking of running the following test for 1.2.0.
>
> * Run stress test for 24 hours on multiple nodes on EC2 (use YARN to run)
> * Run webindex for 24 hours on multiple nodes on EC2 (use Mesos+Docker to
> run)
> * Develop some test that stresses the new read lock feature and run
> it for 24 hours
>
> Are there other test we should run for 1.2.0?
>
> Keith
>