[MGNLFE-455] DOC: Rules for upgrade frontend libraries for Frontend helper (draft) Created: 23/Mar/23  Updated: 23/Oct/23  Resolved: 25/May/23

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Phong Le Quoc Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes MGNLFE-457 DOC: Rules for upgrade frontend libra... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLFE-456 DOCSub: Rules for upgrade frontend li... Sub-task Completed Martin Drápela  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: SPA Maintenance
Sprint: DevX 38
Story Points: 0.5
Team: DeveloperX
Work Started:
Approved:
Yes

 Description   

Currently, we don't have an official document about when to upgrade to what versions of frontend libraries on frontend-helper projects, ex: react, angular, vue, nodeJS...

Please refer to this wiki page for information: https://wiki.magnolia-cms.com/display/~plequoc/Frontend+helper+library+versions

 

Should be documented at least on this page: https://docs.magnolia-cms.com/headless/spa-development/magnolia-front-end-helpers-for-SPA.html

Document the principles for which version is supported. ie..."Editor: keep the current version until".. then link to the Changelogs where the developer can find the actual version supported.

(Once it is documented, the wiki page should be removed so that we dont have out-of-date duplicates.)

The Frontend Library release process shoulld be updated such that developers keep the docs up to date. 

Also add to the process thaat the changelog should always document the latest supported version.
https://wiki.magnolia-cms.com/display/DEVINT/Release+process+for+frontend-helpers+NPM+packages

 


Generated at Mon Feb 12 05:47:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.