3.0.0 overhaul and plan of action

[justintadlock]

View the 3.0.0 milestone for a list of all tickets.

Release date

I've got a tentative release date set for March 31, 2019. That's actually a Sunday, when I'd never do a release. I wanted to set a deadline and not leave it open ended. As I move through the process of the update, I'll get a better feel for when the real date will be.

Code overhaul

The biggest part of 3.0 is going to be a complete code overhaul. Before even tackling other tickets, I'll need to handle this aspect of the release first. Otherwise, we'll end up redoing a lot of work

I've already been working on this a bit at a time over the past few months and laying out some ideas.

I want Members to be a shining example of what modern plugin development should look like. It should be the plugin that other plugin developers look at for best practices.

PHP version

There's a 100%-carved-in-stone minimum of at least PHP 5.6+.

Depending on how things go, we may even jump to 7+. That will come down to more about whether we need a particular feature. But, return type declarations are a pretty strong reason though because they'd increase security in some areas and make things a lot easier. We'll see what happens, but I lean pretty heavily to going 7+ for this reason alone.

I still need to weigh this decision against real-world users too. It'd be nice to have more specific stats for folks using this plugin.

Components/Packages

Kind of a separate goal of this overhaul is going to be looking at what features, if any, could possibly be separated out into standalone repositories. Having some reusable Composer packages for other plugin projects would be nice.

This is not the "big" goal of this release. However, anything that we identify that can be separated, let's look at doing that.

[justintadlock]

@theo-ct - There's a ticket for that: #36

I haven't tagged it for the 3.0.0 release, but if we can get some movement on how to best handle the issues I listed, it's possible it could make it in.

[theo-ct]

OK, will contribute to the discussion there.

[andremacola]

@justintadlock is this plugin still in development? I was thinking making a fork if not.

[justintadlock]

This is a ticket that is specifically talking about the next stage of development.