Quote:Where are they? Why are these discussions internal? Why can't we have a say? It's our proposal.
It's something Fireburn and Wesley
should be taking care of, but are not. There
should have been a roadmap in February, in fact, it was promised to the Core Management that there would be one. There
should be a solid plan for updating, it
should exactly be clear what kind of features go in LVP 3.0, tasks
should have been divided.
Instead of blaming the Core Management (or me, whatever you prefer, it's not really the same), try looking closer to your own position, specifically the Development Management. I'm assuming Fireburn told you the proposal got denied because it's too vague, please allow me to emphasise on the points you put forward;
-
Post Information about 3.0's development for every 20% of progress (Milestones)
This is not possible unless you have a strict planning and exactly know what 20% actually means. Features and time would have to be divided among developers and everything would have to be clear. Next to that, a milestone has a date associated to it.
-
This means there will be 5 posts, excluding posts for public betas etc.
I think anyone can figure that one post per 20% of progress means there will be five posts in total. Void point.
-
Posts should be on the site, but with a link in the forum news to it + a redirection topic in Dev Blog
How you announce it is entirely up to you. Void point.
-
A progress indicator in the forum news
Same story as the first point, the Development planning is undefined right now, so this simply is not doable.
-
A !progress command in IRC, like LVP 2.90 had one
Idem.
I seriously hope you can agree that this is vague, undefined and simply open to anything you would like to do. Introducing a new feature will most likely introduce new bugs, which will lead to a higher ticket count, which effectively means that introducing a feature would
decrease the progress percentage.
Let me also share a response of one of the Development Management members with you: "We will work on a quite strict planning, which we already planned (lol! ...) to do so. I'll get back to this asap, because we need a solution quick". Did you notice anything about that? This post was made on April 23rd. I surely haven't. While the proposal put forward had been denied because of it's unclarity, putting up a new one always is fine, but the Dev Management just doesn't.
Simply put, problems are being caused by your Development Management not fulfilling any of their promises and not communicating properly towards the Development Team. The Core Management is very much aware of this performance by the Development Management, had various talks with them about it, but agrees that little progress has been made. Jay, we had talks about this on IRC and I suggested a solution which would work for you, instead of moaning or extorting you could simply try to do that, as I wouldn't have suggested it otherwise.
