Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
What is the process for community developers to learn/be informed of breaking changes in the NEO Core? #272
(b) the thousands or 10,000s of community developer hours worth of effort that are continuously being invested in trying to keep up-to-date (in a totally 100% reactive way) with the changes to the NEO Core being dumped into the NEO network, and
(c) the damage being done to the reputation of NEO community apps and dev tools when they fail due to breaking NEO Core changes,
...this is a horrible waste and drain on the ecosystem and very damaging to the reputation of the NEO blockchain when the NEO Foundation/NGD chooses to continuously dump new breaking changes into the NEO network.
What is needed is an effective release process:
These are the basic requirements ...and shouldn't ...can't... wait any longer ...else the NEO platform and NEO ecosystem is simply a house of cards (a facade) that breaks down every few weeks/months as exemplified by #271.
changed the title from
What is the process for community developers to learn/be informed of breaking changes?
What is the process for community developers to learn/be informed of breaking changes in the NEO network?
Jun 20, 2018
Additional feedback from the NEO community (direct quotes edited for spelling and simple grammar):
@saltyskip, these are the solutions listed in the Open Letter in the form a list deliverables (for the most part) that I suggest need to be created and delivered. Here they are again with a bit more detail and some examples plus another item or two:
What else do people feel needs to be on the list in terms of missing release process tasks/deliverables?
What else to people feel is needed in the NEO ecosystem overall?
RE: NEO R&D Roadmap https://neo.org/blog/Details/4086
The above is a marketing roadmap, at best, a product marketing roadmap. A proper detailed technical roadmap is needed ...i.e. more details. In addition, it is not accurate (e.g. NEP-10 is not a Q4 activity - it's already an Accepted and Final NEP standard that is being implemented by SC developers as I write this).