-
Notifications
You must be signed in to change notification settings - Fork 12
Milestones and release planning
Milestones in the issue tracker generally correspond to releases. They are named after the intended version number when that is planned/predictable (e.g. v1.2.1). Otherwise they are given a codename, and the version number will be whatever we've got to when that release is ready (e.g. lhs-2).
A milestone like v1.x indicates "we want this issue in a future release of the v1 line, but we haven't prioritised it into a specific release yet".
Issues without milestones indicate that we haven't decided yet whether or not we actually want to resolve that issue. For example, feature requests start with no milestone, and if we decide that we do want that feature then it gets assigned to a milestone.
-
v1.x Releases of the associations platform with new features.
-
v1.x.y Maintenance (bug-fix) releases of the associations platform.
-
lhs-1 Support for virtual Proceedings of the Board for the Hackspace Foundation CLG.
-
lhs-2 Virtualise additional portions of the Hackspace Foundation CLG.
-
clg Full support for general CLGs.
-
coop Support for co-operatives (specifically, Industrial and Provident Societies)