Skip to content

release process, debug topic #2004

@sdarwin

Description

@sdarwin

An hour after importing 1.90.0 beta1, it was necessary to manually check:

"Fully imported Whether this version has been fully imported and is ready for use."

The import machinery would know if the version was fully imported. Perhaps it wasn't successful: the release notes failed? Is so, it was correct to skip "Fully Imported". That leads to the next issue: if a step in the import fails (such as release notes?) would that be included in the status email?

Below, it shows what Marshall received. It doesn't mention bugs, crashes, or problems with release notes. It says "was completed". Maybe successfully. So there are alternative issues, one or the other, not both:

Either the notification emails should report more details about a problem, or else "fully imported" should be enabled automatically after a success.

The task import_new_versions was completed. Task took: 0:00:31.780648

Progress Messages
2025-11-13 02:06:40.898717+00:00: Task start - command: import_versions, desc: importing versions...
2025-11-13 02:06:40.934968+00:00: Task done - command: import_versions, desc: importing versions
2025-11-13 02:06:40.935026+00:00: Task start - command: import_beta_release, desc: importing most recent beta...
2025-11-13 02:07:12.104381+00:00: Task done - command: import_beta_release, desc: importing most recent beta
2025-11-13 02:07:12.104422+00:00: Task start - command: import_development_versions, desc: importing development versions...
2025-11-13 02:07:12.279183+00:00: Task done - command: import_development_versions, desc: importing development versions

Metadata

Metadata

Assignees

Labels

BugSomething isn't working

Type

Projects

Status

In Review

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions