Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Are there any blockers? DEV seems working...!?
Are there any blockers? DEV seems working...!?
Comments
Comment #1
dwwI'm not sure if there are any blockers, I haven't had a chance to review the queue (and don't now, either).
Please update the summary with anything you think needs to be done before a beta1 release. Hopefully rcross can/will help out, too.
Cheers,
-Derek
Comment #2
hass CreditAttribution: hass commentedI do not like to create a beta. This should be a final 1.0. Will update the case soon.
Comment #3
dwwSo long as it's well tested, we don't have to do a beta (although in that case, I'd like to wait a few days after all the commits are in -dev to give other sites a chance to help with testing, too).
Comment #4
dwwp.s. Actually, an "rc1" would be more what I had in mind. I agree we don't need beta. What do you think about an rc1, followed by 1.0 a week or so later?
Comment #5
hass CreditAttribution: hass commentedWe may should fix #1713276: Doesn't list all modules / lists random modules upon refresh soon, but it's not a show stopper.
Committed all stuff that was ready. All lights green, also the coder lights... something I have never seen myself yet. :-)
Comment #6
klonos...better title for our dashboards + tags ;)
Let me also just say that I've been using the d7 version of the module for quite some time now (actually since Pasqualle's initial/unofficial dev version from #454368-33: Port update_advanced module to D7 back in mid-2011) in a number of sites and other than #1713276: Doesn't list all modules / lists random modules upon refresh, I've had no issues with it. Now, I'm always using dev versions of modules where available (#750352: Provide an option to also offer dev builds as updates if they are newer - for advanced users & beta testers / #745816: Offer dev versions as updates (if they are newer) even if a stable release is installed), so normally I shouldn't be bothered with this at all, but if you're looking for stability confirmation as a "go" for a stable release, then a +1 from me too.
Comment #7
hass CreditAttribution: hass commented@dww: Are you able to create the release, please?
Comment #8
hass CreditAttribution: hass commented@dww: Are you able to create the release, please?
Comment #9
dwwUgh, sorry. This once again feel off my radar. I *finally* had a chance to play with the D7 update_advanced on a test site and discovered this:
#1951408: Core Update manager doesn't correctly handle "status" UPDATE_NOT_CHECKED
I don't want to create a release until we do *something* with that. Bare minimum is documenting that update_advanced and update manager aren't (yet) compatible in D7. Let's discuss there.
Thanks/sorry,
-Derek
Comment #10
dwwSorry for the delay. RC1 is now published: update_advanced 7.x-1.0-rc1
Comment #12
Chris CharltonWhat about RC-2? :) It's been *some* time.