[MGNLFE-590] System to ensure we keep FE demo projects up to date Created: 28/Jul/23 Updated: 05/Sep/23 |
|
| Status: | Open |
| Project: | Magnolia Frontend Helpers |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Bartosz Staryga |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: | |
| Epic Link: | SPA On The Ball |
| Description |
|
See where this ticket is tagged here: Pro-actively update minimal-headless-spa-demos at least once a month. Use cases: As a developer learning Magnolia, I also want all of the key Magnolia demo projects, especially those used in tutorials, to be using recent versions of those libraries - including metaframeworks like Nextjs.- So that I can use them on my projectss which use those recent versions, and so that I get a good impression of Magnolia and feel that I can rely on the company to stay up to date. As a Magnolia developer, I want to have a process or system that ensures that all demos are up to date so that I am not embarrassed when a customer points it out. For example notifications, reminders, auto ticket creation, auto pull request creation etc. Note: We should devise this plan with Services team. They are owning the minimal-spa-headless-demos. |
| Comments |
| Comment by Christopher Zimmermann [ 04/Sep/23 ] |
|
Hey there - any timeline horizon on this? Will be nice.... |
| Comment by Bartosz Staryga [ 04/Sep/23 ] |
|
I plan to start moving the minimal demos to it's own repos within 1-2 weeks, with speed one repo/demo per week. Once we have first repo moved I will be updating README in current minimal demo to point users to new repos. |
| Comment by Christopher Zimmermann [ 04/Sep/23 ] |
|
Oh cool. Thanks. Are you still thinking about some build process to create the customer-facing simpler projects based on some kind of internal "master repo"? I'm thinking its nice to have the shared light modules with templlate / dialog diffs. Otherwise will be a bit of extra work to keep the demos in sync when something changes. (but of course there are trade-offs.) |
| Comment by Bartosz Staryga [ 05/Sep/23 ] |
|
czimmermann for starters just a hard split. Next step we'll think about streamlining. |