No UI changes for 1.9 / Feature Freeze? / 2.0

We'd like for almost all 1.8 plugins, including themes, to just work on 1.9, so we're trying to make as few front end changes as we can get away with, and definitely the pressure to get 1.9 out makes it harder to spend the time evaluating these changes. So please don't be offended if your pull request(s) gets bumped to the 1.10 milestone. (You can get a decent picture of 1.9 in the CHANGES file. We're trying to keep this more up-to-date as we go along.)

I think we should consider a cut-off date for new 1.9 features/APIs or any minor bugfixes that have the potential to cause regressions/other problems. This is going to bum out some of us, but otherwise we're going to continue the cycle of adding features/fixing the resulting regressions.

There's a lot of pent up demand for a UI/UX overhaul and 1.10 has the potential to more radically change Elgg in ways that will not be very BC for front-end heavy plugins. By the rules of semantic versioning this makes think 1.10 should actually be 2.0.

Feedback and Planning

Feedback and Planning

Discussions about the past, present, and future of Elgg and this community site.