-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release version 1.9.0 #313
Comments
In testing the final release zip here, I'm noticing a handful of issues that all seem to stem from the player enhancements we did in #272. I think we need to investigate these a bit more before we proceed here cc / @jeffpaul Here are issues I'm seeing:
![]()
![]()
I'm not flagging this as an issue or a blocker for release but I do wonder if we could come up with a better approach for all the new settings we added. Right now it's just a long list of toggles, which works but feels like there may be a better approach: ![]() |
@dkotter Raised #320 to fix the first issue of list from here: #313 (comment) |
Thanks to @iamdharmesh and @sudar, most of these have been addressed. Here's the things I still see as outstanding:
![]()
![]()
|
It seems that the podcast transcript shows with proper spacing. Could you please let me know which theme you are using? So, I can check with that.
I am able to reproduce this and raised WIP PR #322 to fix this
I believe this feature was added to improve the user experience (see GitHub issue), but I'm fine with displaying it only once, either at the post level or the block level. Perhaps @jeffpaul might have a better suggestion for this. Additionally, the behavior of the two panels is currently inconsistent. The post-level panel does not display the hierarchical term selector view, while the block-level panel does. The post-level panel opens the modal for adding a podcast, whereas the block-level panel uses the default core functionality for adding podcasts. We need to match behavior on both or need to display this only once.
Thank you |
Checked again and not able to reproduce with any of the themes I have installed locally 🤷🏻 So I think we're good on this one
Hmm.. that's interesting, didn't even test all that functionality. I think this was something that just wasn't done entirely correct, especially considering the differences between the two. I really like the modal that shows so my suggestion would be to leave this at the post level and not have it at the block level at all. But I wasn't involved in the decisions around these UI improvements so @jeffpaul can chime in with his thoughts |
Once seems better and less confusing. My expectation is that a post has a 1:1 relationship with a podcast episode and thus to keep the settings at the post level and not the block level though not sure if the display in the podcast player infers from the block settings so if so we'll need that to update to infer from the post settings.
I think the hierarchical podcasts seems wildly unlikely to be currently or ever used, so I'm fine with the handling of the post-level display. Also fine with the modal approach. So post-level is in, block-level is out. |
Thanks for sharing thoughts on this @jeffpaul. @dkotter I have updated PR #322 to address the remaining issue from comment #313 (comment). Could you please help with review it once and verify the issues you were facing are fixed now. Thank you. |
This issue is for tracking changes for the 1.9.0 release. Target release date: November 2024
Release instructions
develop
, cut a release branch namedrelease/1.9.0
for your changes.simple-podcasting.php
,package-lock.json
,package.json
, andreadme.txt
if it does not already reflect the version being released. Update both the plugin "Version:" property and the pluginPODCASTING_VERSION
constant insimple-podcasting.php
.CHANGELOG.md
andreadme.txt
.CREDITS.md
with any new contributors, confirm maintainers are accurate..distignore
.README.md
is geared toward GitHub andreadme.txt
contains WordPress.org-specific content. The two are slightly different.develop
(or merge the pull request), then do the same fordevelop
intotrunk
, ensuring you pull the most recent changes intodevelop
first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop
).trunk
contains the latest stable release.trunk
branch to GitHub (e.g.git push origin trunk
).trunk
todevelop
to ensure no additional changes were missed.trunk
branch. Paste the changelog fromCHANGELOG.md
into the body of the release and include a link to the closed issues on the milestone.Due date (optional)
field) and link to GitHub release (in theDescription
field), then close the milestone.1.9.0
do not make it into the release, update their milestone to2.0.0
orFuture Release
.The text was updated successfully, but these errors were encountered: