Replies: 3 comments 3 replies
-
I'm ok with starting to plan for a v2 release, there's a lot of things that I'd like to deprecate. I'm not on Discord because I find it too distracting. If you don't mind, I'd rather we do the planning here, we can also create an issue to list all of the things that we want to deprecate or change and work towards the 2.0 release. Some things that I want to rework:
|
Beta Was this translation helpful? Give feedback.
-
Lots of great ideas, in general, we can introduce new features over time so we can keep the releases small-ish and stable. For me, 2.X is more about the release where we'll drop backwards compatibility for deprecated features and not where we release X number of huge features.
I'll have to review a more concrete proposal on which methods will be moved to which class. But I think this discussion is for after we introduce the
In general, I haven't had much trouble with this so far, this is okay to do but not a high priority.
Yes.
I don't think we'll gain much from switching the default. I'd still argue that the forking mechanism is a good default. We can keep the
Agree, maybe we can introduce a
|
Beta Was this translation helpful? Give feedback.
-
@selwin a draft doc on the main |
Beta Was this translation helpful? Give feedback.
-
@selwin I've been thinking about some changes, but I always run into backwards compatibility issues. Have you given some though on a possible V2? Are you on DIscord so we could sync on this?
Beta Was this translation helpful? Give feedback.
All reactions