This is an overview issue for the release of version 2.0 of Timber. If you find questions about the release of Timber 2.0, guide them here.
Roadmap
The next steps for a 2.0 release are:
The past has shown us that it’s difficult to predict an exact ETA. And with our limited resources, we don’t want to make promises we can’t keep. But let’s work towards a 2.0 release by being strict about what we really need for a 2.0 release and what we can postpone for later.
Help is welcome from everyone, also developers who are not maintainers. If you can provide insights, spot issues in the pull requests and comment on these, you’ll help us move the project forward.
Pull requests
The following pull requests need to be reviewed and resolved.
For each of these pull requests we should decide whether we can solve them in the future or whether we really need to solve them for a first 2.0 release. By "future", we mean that we can decide whether:
- The issue can be resolved in a minor version of Timber 2.x, so 2.1 or 2.2, etc.
- The issue will have to wait for Timber 3.x.
Postponed issues and pull requests
Outstanding issues
Issues with patches
This issues have patches and will be resolved when their corresponding pull requests are resolved.
After release
Example for 1.x branch:

Example for main (2.x) branch:

This is an overview issue for the release of version 2.0 of Timber. If you find questions about the release of Timber 2.0, guide them here.
Roadmap
The next steps for a 2.0 release are:
2.0.0-beta.2by the end of this week2.0.0-rc.1by June/July 2023🚀 Check out the Release notes.
The past has shown us that it’s difficult to predict an exact ETA. And with our limited resources, we don’t want to make promises we can’t keep. But let’s work towards a 2.0 release by being strict about what we really need for a 2.0 release and what we can postpone for later.
Help is welcome from everyone, also developers who are not maintainers. If you can provide insights, spot issues in the pull requests and comment on these, you’ll help us move the project forward.
Pull requests
The following pull requests need to be reviewed and resolved.
PostFactory::is_imageincorrectly usingwp_check_filetype#2730Post#2750For each of these pull requests we should decide whether we can solve them in the future or whether we really need to solve them for a first 2.0 release. By "future", we mean that we can decide whether:
Postponed issues and pull requests
2.x Future)2.x Future)2.x Future)2.x Future)Outstanding issues
Issues with patches
This issues have patches and will be resolved when their corresponding pull requests are resolved.
After release
Example for 1.x branch:

Example for main (2.x) branch:
