First up let me say that Node-RED 1.3.0-beta.1 is coming this week. There is one PR left to merge which should happen tomorrow.
Putting that aside, we're starting to think about the 2.0 release. We published our plan last year that explained how we intend to release Node-RED 2.0 to coincide with the end-of-life of Node.js 10. That happens at the end of April - just 8 weeks from now.
Whilst we aren't looking to make any significant breaking changes (other than no longer supporting Node 8 and 10), releasing a new major version is an opportunity to consider changes that we wouldn't necessarily want to do in minor releases.
We also need to be realistic as to what we can achieve in the relatively short time frame available - keeping in mind that 1.3 still needs to be finished off even after the beta is shipped.
We're putting together a list of the items we want to get done for 2.0. And this is where we'd like to get feedback from the wider community.
The type of thing we're looking at is changing some default node configurations - so existing flows continue working as before, but newly added instances of some nodes may come with a different default setup. There may be some settings in the settings.js file we'll be deprecating in favour of better alternatives.
Are there changes we should be considering? This is not meant to be a feature wish list. It's more about changes to default behaviours, or changing the way something works.
You can see the current list here: Node-RED 2.0 Planning · GitHub
If there's something you'd like us to consider, please add a comment either here, or onto this github issue.