[CLOUDINARY-47] Incubator to extension Created: 24/Nov/23  Updated: 24/Nov/23

Status: In Progress
Project: Cloudinary DAM Connector
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Raphael Falvo Assignee: Raphael Falvo
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)
Team: Services
Work Started:

 Description   

Within the process of moving incubators into extensions, and aligning the processes with how product addons are handled, there are few tasks that need to be done:

  • Does the module have a Jenkinsfile? If not, most likely the magnoliaDefaultPipeline() is a good start
  • Move module’s version to permanent SNAPSHOT so that depending on it in downstream projects is easier
  • Change version of Magnolia to 6.2 permanent SNAPSHOT and use baseline property as an indication for Magnolia compatibility (e.g. in module descriptor)
  • Create “documentation” branch from master which will be used for live documentation (to inform Alex to read from it from Antora)

Generated at Mon Feb 12 00:00:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.