You are viewing a single comment's thread from:
RE: Curation reverse auction changing from 15 minutes to 1 minute in hard fork 21
So, HF21 is out for testing and there are still features to be implemented?
Shouldn't there be a code freeze?
So, HF21 is out for testing and there are still features to be implemented?
Shouldn't there be a code freeze?
It was frozen, but this was a hot topic before that was missed on the final chopping block. Because it is a simple three line change, it was added. Each additional hard fork introduces risk so on one hand, you want to do as much as you can each hard fork, on the other hand, you don't want to change too much so it becomes a balancing act.
I don't remember this being discussed here anywhere.
It my be only a 3 line change, but this can have huge impact.
Anyway, no one did any end user testing yet, AFAIK, so it shouldn't matter
Continuous improvement, I guess... development should not stop because a specific version of the code is being tested. But I am not sure how much time it’s agreed as safe here.
Posted using Partiko iOS
Even with ci, there are certain delivery dates, with approved targets, features, etc.
But this seems just random.
Then I would prefer to delay the HF then having a bad experience, like on the last one. If that needs to get into the HF.
This isn't really a code change it is just changing a constant. Due to some other bug fixes that were needed there will be a respin on the release candidate offering an opportunity to get this in. It had been previously discussed but the ball got dropped along the way.
AZ-5 is also just a button...
:)))
Let's hope for nothing like that Ж)