A new path to Pods 3.0
We recently announced that we were parting ways with CMB2 from Pods 3.0, and with that, revisiting our Pods 3.0 code to see what we could do to get things back on track. We’re happy to announce that after some long discussions, we landed on splitting up what we currently know as Pods 3.0 into smaller releases.
There are a number of benefits in splitting up the huge Pods 3.0 release into smaller releases including:
- Easier to test / release smaller features and not have them interacting in a way that could potentially hold up those working features from getting to you sooner
- Faster release cycles 🙂
- Some changes early on in the Pods 3.0 release cycle by some of our contributors have made it difficult to efficiently merge bug fixes and small enhancements in Pods 2.x releases back into Pods 3.0 — this created a lot of extra strain and delay for both Pods 2.x and Pods 3.0 releases themselves
- When we release a feature, then future bug fixes and enhancements in that code aren’t so hard to deal with on their own
- By splitting up the features from Pods 3.0, we can work on multiple features at the same time, but not have to worry about huge conflicts when merging each individual release into a feature branch
So what does our roadmap look like now? Well, just so you know — Loop Fields (or Loop Field Groups) are our end goal, but we need to get some things out first so we can get the prerequisites out of the way for it’s inclusion. Loop Fields require some big features to be completed and working in order for it to be finished and released, but if we work on those and release those parts individually then we’ll be able to keep our code moving forward and reduce strain overall on our developers and testers alike.
The new Pods Roadmap
We are introducing a new feature that our core developer Phil Lewis was able to prototype quickly with help from new contributor extraordinaire Nic Ford — and we know you will love it: Flexible Relationships
Flexible Relationships offer the ability to add new items straight from within the form you’re in, when you’re using a Relationship field.
It’s the logical cousin to what Loop Fields are, but for relational data that can be re-used, and we’re excited to see how this feature gets better as we finish the new Loop Field Type.
In addition to Flexible Relationships, we’re also bringing in our Pods WP-CLI commands so you can interact with Pods and our API directly from the Command Line.
In Pods 2.8, we are focusing on backporting our Field Groups management that we have in Pods 3.0.
With everything lined up and any prerequisite changes into Pods core that we need to make Pods 3.0 happen, we’ll be able to finally introduce a new and improved interface from what we previously planned for the Loop Field Type. More details on our plans and screenshots to come as time goes on.