Context Navigation

The intention of this page is to classify features and their place with respect to R1. Once every feature is classified, the releases up to and including R1 can then be scheduled. This schedule will help to serve as inspiration to contribute to features that are required for a particular release.

Procedure

Define the R1 feature set. Features should be organized in three groups:

must-have features

nice-to-have features (which shouldn't hold off the release)

definitely-post-R1 features

Define a rough estimation/schedule for the implementation of the missing

features.

Create the R1 roadmap. This includes all releases we want to do until R1, tagged with preliminary release dates.

Features

Locale

Reasons For

more polished impression

despite a non-public API, it has stirred many contributions and is important even in its current state

Reasons Against

need to update bundled third party applications

locale kit not ready to be public API

layout kit not ready to be public API

including it in Pre-R1 & not in R1 Final, may cause false hopes

SubTasks

Make Layout Kit public

make it FragileBaseClass safe

adding a whole bunch of padding virtuals and padding data to each class as needed.