Stable 8.x-1.0 release with security coverage

News ?

@Kriss77 see: #2902872: Request to co-maintain File (Field) Paths

Is there anything new?
What are the problems that need to be resolved for a stable version?

The issue doesn't need to be related to itself.

Soon, there will be a stable release. I'll keep you updated on that.

See the release candidate https://www.drupal.org/project/filefield_paths/releases/8.x-1.0-rc1

For stable release this issue is must have #3331483: Update README.md file according to "README.md template"

#3331483: Update README.md file according to "README.md template" has been merged. Are there any other release-blocking issues? Perhaps #3121826: Image style thumbnails missing for temporary:// files would count.

The issues mentioned have been fixed and committed, so it looks like a stable release could be close?

Hi @ressa,

You can see a general roadmap/plan @ https://git.drupalcode.org/project/filefield_paths/-/milestones

I expect to get rc2 out this week and will flip it to stable after a respectable amount of testing and any last minute bug fixes.

I appreciate the patience here, open source development is real work and comes at a cost to the developers and maintainers.

Thank you for a fast answer @deciphered, and for creating and maintaining this great module!

The upcoming release plans sounds great, and good idea to use GitLab Milestones for a detailed plan for the next releases, and required issues -- an exemplary use of such a tool.

Perhaps the Milestones page could be linked to from the project page, to drive more activity into the currently most relevant issues?

And I do agree: Maintaining an Open Source project can be very energy and time consuming, and we should all try to help out, however we can: Triaging issues, helping with code fixes, reviewing existing issues, etc.

Yes, the project page will get an update as part of the upcoming stable release. And thank you for your ongoing issue triaging, it is noticed and appreciated.

RC2 is out.

I encourage everyone to test thoroughly, if there's no major blockers then I expect 8.x-1.0 to be tagged in a week or two.

Very nice, thank you @deciphered!

I'd like to get another couple issues in as well before the stable. Ideally I'd still like to release the stable this week.

If you would like to assist, please help test and review:
- #3277844: After updating image on node edit page, the final image used is wrong
- #3494240: Redirect gets created every time new media entity is created.

8.x-1.0 is out: https://www.drupal.org/project/filefield_paths/releases/8.x-1.0. It requires Drupal 10.3 or 11 and PHP 8.2, and the project is covered by the security advisory policy from this release.

Thank you to gg4 for opening this seven years ago and to everyone who kept asking. voleger carried the module to rc1 and did most of the work that made a stable release possible. ressa and liam morland chased the last blockers and triaged the queue while the release took shape. xamount, sakshi17 and cicciobat reported and fixed the three issues that landed between rc2 and the tag, and solideogloria kept the metadata straight. Thanks as well to everyone who tested rc1 and rc2 and said so.

Closing as fixed. Anything found in 8.x-1.0 goes in a new issue against the 8.x-1.x branch.

Fantastic news, thank you @deciphered and everyone else who helped make this happen! 🎉

And thanks for updating the project page as well. Perhaps it could be considered to link to the Milestones page from the project page as well, to drive more activity into the currently most relevant issues, with something along these lines?

Roadmap

Check the Milestones page for a detailed release and development plan, bugs to fix and features to be added, and the relevant issues.

1.0 takes bug fixes only, 1.1 is where the queue catch-up goes, 1.2 is the long tail, and breaking changes wait for 2.0.0.

I'm gunna hold off on that until the project is migrated over to gitlab properly, as the milestones really need the work items to exist to be of real value, but for sure when that happens it should be better utilized.

Ah yes, that makes sense.