wiki:development/2.3
Last modified 3 years ago

2.3 Roadmap Discussion

The following are candidate items for inclusion in 2.3. Please note that it is very likely that a large number of these won't make it into 2.3 - this is just a list of everything that has been discussed.

General

RESTful Server - Ingo - 2.3

  • Dependencies: SearchContext?
  • State: Two implementations
  • Includes DataFormatter?
  • Still hard to customize, unsure if the monolithic server approach holds up (hard to customize, see clustering in sscmap project)
  • Relations not fully supported
  • Needs documentation

ModelAdmin - Sam - 2.3

  • Includes CSV bulk loader
  • Dependencies: None
  • State: API well tested in 4 different usecases; needs documentatin
  • Ingo thinks that ModelAdmin? Javascript could use improvement, but it is debatable how much. A little more organisation into javascript for the various areas of the UI would be handy.

CMS

Workflow - Sam - 2.3, just what already exists in a project branch

  • Polish existing workflow infrastructure
  • High customer demand
  • Sam to review

Static publishing - Sam - 2.3, turn it into a module

Forms

Formfield Restructuring - Ingo - some in 2.3

  • Deprecation of useless fields like LabelledLiteralField? vs. LiteralField?
  • Moving country-specific fields to new module
  • Moving special and rarely-used fields to new module

Field scaffolding - Ingo - 2.3

  • State: Well used and tested, but needs some FieldSet? improvements to be really useful
  • Should we scaffold SiteTree? classes as well? Or too much customization to start with a scaffold?

i18n

i18n Unit Testing and Refactoring - 2.3.1?

  • Unit Testing Pre-Requirement for deep API changes and refactorings, but hard to test in its current stateful form
  • Implement a less stateful i18n class thats easier to test

Core

Multivalue Fields - Ingo - 2.3

  • Dependencies: None
  • State: Hardly tested outside of GIS context, still clumsy to implement with lots of manual switches

Permissions - Ingo - 2.3