Release 3.10.1

[onlyjob]

3.10.0 appears to be released without fixes for #422 which IMHO makes releasing 3.10.1 an immediate priority.
As far as I'm aware current state of "master" is ready to be released as 3.10.1.
Let's release it ASAP as per #440.

What's left to do to release 3.10.1?

[psarna]

1. Some more commits related to 23e3af5. It is a replacement for client tools, which would now be bundled in one lizardfs binary. Details are available in commit message. All backward compatible of course.
2. Implementing a task manager for lengthy operations: snapshot, setgoal, settrashtime, etc. It would make all these operations asynchronous, so master will not hang for several seconds on huge directory trees anymore.
3. Obey (minimum) goal settings #227 is a candidate as well since it looks simple enough

[onlyjob]

Great: it looks like 2. is going to fix #329...

[psarna]

#329 and any future issues with lengthy commands. They are redesigned at their core so it will take some time to test them all properly, but in the end master would become even more responsive, which is one of the priorities right now.

Question: what is the safest way to update LizardFS master / shadow / chunkserver / metalogger? Do I need to follow a certain order?

[psarna]

https://github.com/lizardfs/lizardfs/blob/master/UPGRADE

On Wed, Aug 17, 2016 at 7:43 PM, Asher256 notifications@github.com wrote:

Question: what is the safest way to update LizardFS master / shadow /
chunkserver / metalogger? Do I need to follow a certain order?

Thanks.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#449 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ8yF2Oe9Bkluq-KL7aF266dONZbl0lVks5qg0gpgaJpZM4JmAFI
.

Thank you Psarna!

[biocyberman]

@Asher256 Good that you asked. I learn a new thing as well.

[onlyjob]

Fixed by 3.10.2. Thanks.