Skip to content

[preset-env] v8 process #461

@romainmenke

Description

@romainmenke

visit the v8 branch


For the next major version of postcss-preset-env we want to try out a new process.

  • well defined scope for all changes
  • release candidates
  • keeping the current major version (v7) maintained for a short period

multiple batches

As discussed in #460 v8 will be quite large and the process will take a while.

To keep a good overview we will work in multiple batches.
Only the first batch has been scoped at this time.

Knowing the scope ahead of time allows everyone to plan for these changes.

We might try to release alpha versions of v8 after each batch has been completed.

release candidates

As postcss-preset-env is also packaged in other projects we want to give everyone time to try out the updates and give feedback.

We absolutely want to avoid having to ship another major version shortly after because we overlooked something.

v7 maintenance and support

We will keep supporting v7 for 3 months after the initial release of v8.

Because of the amount of plugins and the complexity of the whole project we can't keep supporting older versions for long stretches of time.

If 3 months is too short (or long) for you, please let us know.


in practice

Most work will happen against a new v8 branch.
All breaking changes to plugins and postcss-preset-env will happen there.

Regular maintenance and updates will be done on the main branch (v7).
These changes will then be ported over to v8.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions