[SOLVED] v2 or 1.2.0 ?

[LoganTann]

#137 (comment) : Generally a good idea, but since we plan v2 after v1.1 (https://github.com/materializecss/materialize/releases) we can do it there. This will include upgrade of all relevant parts.

As suggested by @DanielRuf, the next release will be v2.0 and not v1.2

I understand the suggestion, but I think we have to release 1.2 first before moving to a new release.

First, there are a lot of issues which just fixes bugs (i.e. don't add new features) that can be easily resolved. See https://github.com/orgs/materializecss/projects/1 if you have the collaborator rights.

Moreover, there are also some issues that suggests enhancements and a complete rewriting of some components (for example, replacing the use of floats to a flexbox or even a CSS grid for our grid component)

Judging by the time to fix a single bug and what we should add for v2, moving directly to the next release will take a lot of time. Maybe in more than 6 months ? That's why I'm suggesting we have to submit a 1.2 pre-release before.

Feel free to explain what are your thoughts about a 1.2 release instead of v2.

Thanks in advance !

[DanielRuf]

The next release will be v1.1. See the releases tab. The current release is v1.1-alpha (which comes before beta and stable).

v2 will provide a modernized setup, much more changes and will break things.

There is no v1.2 planned.

[LoganTann]

Okay it's more clear now, thanks for the reply !

[DanielRuf]

and a complete rewriting of some components

These would be breaking changes ;-)

[AJLeonardi]

Is there a timeline on the next release? we've been on 1.1-alpha for almost a year.