cosmos icon indicating copy to clipboard operation
cosmos copied to clipboard

Version 1 release schedule and migration plans

Open andresgalante opened this issue 6 years ago • 0 comments

The design systems team is proud to announce that Cosmos v1 will see the light the first week of March. Since it started as a proof of concept we've learned a lot from our wins and our mistakes.

Version 1 is a clean slate that will not only allow authors to create more flexible and robust UIs but also give the project a solid base to create and extend feature.

In order to get there v1 will introduce two breaking changes:

  • Removal of margins on all components to create a layout system following our guidelines #1108
  • An API refactoring #1277 and #1225

Migration

To make the migration process as smooth as possible, we will write a migration guide and offer support as well as split the v1 releases into 3 stages:

v1.0.0-alpha1

Alpha 1 will see the light during January and will include:

  • A layout system to position, distribute and size components on the screen
  • Introduction of a margin prop that will allow an author to opt-in margins.

v1.0.0-alpha2

Alpha 2 will be released during February and will include an API refactoring.

v1.0.0

Version 1.0 is scheduled for the first week of March. It'll include a migration guide as well as an improved tokens system, a refactoring of some components such as sidebar, list and form, improvements on the docs, and all the tasks related to a major release.

Removal of all margins in components

Since the spacing between components should be done by the layouts, components should not have margins.

During January and February, we'll work with the Manhattan team to make sure that Comos' layouts can handle real life use-cases and do a progressive implementation of layouts on Manhattan screens.

Once we've proved they are viable we'll remove margin on v1.0 in March.

Code Freeze

Version 0.12 will be the last version of the 0.x series.

We will not continue developing new features on 0.x but we’ll work on bugs.

Migration path

We encourage author to follow our alpha releases.

It will give them access to new features while making smaller steps towards v1.

They are welcome to jump directly into v1, the result would be the same. But as shown of @siddharthkp great graph, the area under to cover is the same, but it's easier to chew in smaller bites

migration

andresgalante avatar Jan 08 '19 12:01 andresgalante