You say this, which echoes the opinions of several here, but we’re now at post 100 on this topic and yet nobody has addressed the issues raised against it in order to make a case for this view.
There seems to be a belief that more reliable estimates should be possible at this stage than have been given to date (each sprint is an estimate - usually two to three weeks), but I don’t see the reason why that should be the case. I’ve explained why I don’t think it’s feasible, or helpful to give them regardless.
I’m sure MaidSafe will take these views into account, they have always tried to do what the community wants, but unless someone can make a good case for this I hope they’ll stay cautious.
Once reliable estimates can be produced, for less complex, “been here, done that” code and tools, MaidSafe will I’m sure be able to give more in this respect. But we are still dealing with the core, never done before features, and still relatively early days using a new and evolving toolset.
Frankly, I think the best thing MaidSafe can do to respond to these concerns is get Rust-5 out there, and then move into the next sprint.
Clearly this discussion would not have happened if they’d achieved Rust-5 even last week. We’d all be busy playing with the network. This is in large part understandable community disappointment and anxiety, because this has been a big bump at a time when we’re on the verge of something really fantastic. It’ll be back in track soon I’m sure, and everyone will be much happier and these calls will die down to their previous level. And MaidSafe can get on with the important work of the next sprint, tweaking the network and adding features.
I thought all the major issues raised have now been addressed …well were addressed around 60 posts ago…lol. I’m not sure what everyone’s arguing about still. I said some time ago that I had answers from devs that satisfied my concerns, I think @Seneca said a similar thing and most of the others are quite happy I think.
We’ve been told “weeks” for Rust 5/basic Network, then we’ll be in a better position to do Roadmap of when all the extra bits get added - with estimated timescales.
Basically, they’ll be better able to give timescales once Rust 5 done.
The ongoing debate about whether devs should give timescales has been decided already - they will…lol
What am I missing?
finish up RUST-5 - fixing the bugs and deliver on the planned activities of RUST-5
As people try out the code there may be a few more touch ups to be done
Planning for RUST-6 – 1 to 2 weeks is the typical timeframe for planning
List of activities for RUST-6 will be released
Doing Rust-6
Bug fixing
Somewhere in all that will be time off during the holiday season for the devs to spend time with families etc.
We are really at the business end of the code, that is producing something that can work globally, even though it is not feature complete. So I’d expect there to be a series of whack-a-mole situations on the bugs because at this time they are bringing together the modules and testing them for real life operation.
I’d say that after testsafecoin has (RUST-6 or 7) completed and tests OK then estimations on timeframes will be possible/better because the unique innovations will have been traversed and simple feature additions are easier to set approx timeframes for.
