Should the next release with the Availability use case be 1.3.0 or 2.0.0?

papinet / papiNet-API

papiNet is a global paper, forest products and bioproducts industry e-Business initiative.

http://www.papinet.org/

Apache License 2.0

9 stars 3 forks source link

Should the next release with the Availability use case be 1.3.0 or 2.0.0? #73

Closed patricekrakow closed 1 year ago

patricekrakow commented 1 year ago

Strictly: 2.0.0 Marketing: 1.3.0 @patricekrakow @globaltopmedia

...

patricekrakow commented 1 year ago

Strictly speaking, we MUST change the planned release "1.3.0" into "2.0.0" as some modifications are not backward compatibles, e.g. we have removed the "PUT /customer-articles/{customerArticleId}" API endpoint, because we decided that once created a customer article MUST NOT be changed anymore but stay immutable.

patricekrakow commented 1 year ago

Finally, taking into account that we have delayed all changes on the "Catalogue" use case, we can publish the "Availability" use case as Release 1.3.0.