Are there any blockers? DEV seems working...!?

Comments

dww’s picture

Assigned: Unassigned »

I'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

hass’s picture

I do not like to create a beta. This should be a final 1.0. Will update the case soon.

dww’s picture

So 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).

dww’s picture

p.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?

hass’s picture

Status: Active » Reviewed & tested by the community

We 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. :-)

klonos’s picture

Title: Create D7 release » Create D7 release of Update status advanced settings
Issue tags: +port to d7, +d7 ports

...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.

hass’s picture

Assigned: » dww

@dww: Are you able to create the release, please?

hass’s picture

@dww: Are you able to create the release, please?

dww’s picture

Assigned: dww » Unassigned
Status: Reviewed & tested by the community » Needs work

Ugh, 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

dww’s picture

Version: 7.x-1.x-dev » 7.x-1.0-rc1
Status: Needs work » Fixed

Sorry for the delay. RC1 is now published: update_advanced 7.x-1.0-rc1

Automatically closed -- issue fixed for 2 weeks with no activity.

Chris Charlton’s picture

Issue summary: View changes

What about RC-2? :) It's been *some* time.