Package List For Releases

[christianm (Christian Müller)]

This should become living documentation on packages we have to ease the process of updating dependency requirements and branching:

Primary concern are obviously the two development collections:

• GitHub - neos/flow-development-collection: The unified repository containing the Flow core packages, used for Flow development.

  • Neos.Cache
  • Neos.Eel
  • Neos.Error.Messages
  • Neos.Flow.Log
  • Neos.Flow
  • Neos.FluidAdaptor
  • Neos.Kickstarter
  • Neos.Utility.Arrays
  • Neos.Utility.Files
  • Neos.Utility.Lock
  • Neos.Utility.MediaTypes
  • Neos.Utility.ObjectHandling
  • Neos.Utility.OpcodeCache
  • Neos.Utility.Pdo
  • Neos.Utility.Schema
  • Neos.Utility.Unicode

• GitHub - neos/neos-development-collection: The unified repository containing the Neos core packages, used for Neos development.

  • Neos.ContentRepository
  • Neos.Diff
  • Neos.Fusion
  • Neos.Fusion.Afx
  • Neos.Media.Browser
  • Neos.Media
  • Neos.Neos
  • Neos.NodeTypes.AssetList
  • Neos.NodeTypes.BaseMixins
  • Neos.NodeTypes.ColumnLayouts
  • Neos.NodeTypes.ContentReferences
  • Neos.NodeTypes.Form
  • Neos.NodeTypes.Html
  • Neos.NodeTypes.Navigation
  • Neos.NodeTypes
  • Neos.SiteKickstarter

Those are branched and released via Jenkins!
The respective split repositories of the sub packages should never
be touched manually.

• GitHub - neos/imagine: A package for easy use of imagine in Flow applications (REQUIRED)

This one is important as it’s a direct dependency of the Neos
collection. It has it’s own release cycle “as needed”. The
dependencies must be adjusted, branches created if necessary
and releases created, all via github.

• GitHub - neos/twitter-bootstrap: Twitter Bootstrap, packaged for use in Flow applications (REQUIRED)

Another direct dependency of the Neos collection.
It has it’s own release cycle “as needed”. The
dependencies must be adjusted, branches created if necessary
and releases created, all via github.
We should get rid of this one at some point, but media browser still needs it for sure.

• GitHub - neos/form: Flow Form Framework (REQUIRED)

And another direct dependency of the Neos collection.
It has it’s own release cycle “as needed”. The dependencies must be adjusted, branches created if necessary and releases created, all via github.

• GitHub - neos/party: A party package for PHP based on the OASIS Customer Information Quality (CIQ) XML Standard (REQUIRED)

Is a dependency of the Neos collection.
Release cycle was roughly aligned with Flow, although
becomes more and more decoupled. The dependencies must be adjusted, branches created if necessary and releases created, all via github.

• GitHub - neos/setup: An extensible setup tool for Flow based applications (REQUIRED)

Dependency of the Neos collection and roughly follows same release cycle. The dependencies must be adjusted, branches created if necessary and releases created, all via github.

• GitHub - neos/neos-seo: A package to bundle SEO-related functionality for Neos. (REQUIRED)

This is a dependency of the demo package (and probably many sites)
it’s vital that it works with every release. It has it’s own
release cycle “as needed”. The dependencies must be adjusted,
branches created if necessary and releases created, all via github.

• GitHub - neos/behat

Generally on the same release track as Flow, but is not co released.
Important for build jobs in travis.
The dependencies must be adjusted,
branches created if necessary and releases created, all via github.

• GitHub - neos/Neos.Demo: The Neos demo site package

The branch job for Neos also branches the Neos.Demo as well as the
release job releases that package as well. So this is also never
manually branched/released.

• GitHub - neos/flow-welcome: This package provides a start screen for the Flow distribution with links to online resources (REQUIRED)

It’s branched together with the Flow collection via jenkins, BUT it
is not released automatically with the Jenkins job (TODO), so
you need to manually tag a version here.

• GitHub - neos/BuildEssentials: Flow build toolchain essentials (REQUIRED)

It’s branched together with the Flow collection via jenkins, BUT it
is not released automatically with the Jenkins job (TODO), so
you need to manually tag a version here.

• GitHub - neos/swiftmailer: A Flow package for easy use of SwiftMailer

Follows the swiftmailer package release cycle roughly.
The dependencies must be adjusted,
branches created if necessary and releases created, all via github.

• GitHub - neos/content-repository-search: Neos Contentrepository search common package

So far roughly aligned with Neos major releaes.
The dependencies must be adjusted,
branches created if necessary and releases created, all via github.

• GitHub - neos/neos-ui: Neos CMS UI written in ReactJS with Immutable data structures. (REQUIRED)

Currently completely separate, release also via jenkins.
TODO: Document how, when and what!

• GitHub - neos/redirecthandler: The Neos.RedirectHandler package for Flow (REQUIRED)

It has it’s own release cycle “as needed”. The
dependencies must be adjusted, branches created if necessary
and releases created, all via github.

• GitHub - neos/redirecthandler-databasestorage: DB storage for the Neos.RedirectHandler (REQUIRED)

It has it’s own release cycle “as needed”. The
dependencies must be adjusted, branches created if necessary
and releases created, all via github.

• GitHub - neos/redirecthandler-neosadapter: Neos RedirectHandler adapter for Neos CMS for creating redirects and status codes (REQUIRED)

It has it’s own release cycle “as needed”. The
dependencies must be adjusted, branches created if necessary
and releases created, all via github.

• GitHub - neos/neos-googleanalytics: A package to enable the use and display of Google Analytics data inside Neos.

Status?
It has it’s own release cycle “as needed”. The
dependencies must be adjusted, branches created if necessary
and releases created, all via github.

• ~~https://github.com/neos/fusion-afx~~ Has become part of the collection

• GitHub - neos/metadata-extractor: Extractor to extract asset meta data into Neos MetaData objects

Status?
It has it’s own release cycle “as needed”. The
dependencies must be adjusted, branches created if necessary
and releases created, all via github.

• GitHub - neos/metadata-contentrepositoryadapter: Neos MetaData ContentRepositoryAdapter

Status?
It has it’s own release cycle “as needed”. The
dependencies must be adjusted, branches created if necessary
and releases created, all via github.

• GitHub - neos/ldap: A LDAP integration for the Neos Flow Framework

Status?
It has it’s own release cycle “as needed”. The
dependencies must be adjusted, branches created if necessary
and releases created, all via github.

[christianm (Christian Müller)]

I marked a whole bunch of packages REQUIRED now, those absolutely must have a tagged version with correct dependencies for the to be released version of Flow/Neos available.

[christianm (Christian Müller)]

Need to update package list with Neos 9.0 packages and dependencies (neos/eventstore)