You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest_version field on Addon points to, well, the latest (non-disabled) version. It's used by reviewer tools to figure out which version to review, and internally so set a few things.
With the introduction of version channels, it won't be as useful, since you need to figure out the latest version available in the same channel you're interested in. We could add latest_unlisted_version and latest_listed_version fields, but that's probably overkill and won't scale if we decide to add more channels later.
I want to try to get rid of that field, replacing it with a method that takes a channel and maybe an optional argument to ignore disabled versions. To do this safely, my plan is to do this in 3 steps:
Keep the field and the methods that sets it, but stop using it directly, instead using latest_version property to emulate it, and modifying reviewer tools queries that directly hit the database
Then, replace latest_version property with a method using the channel
Then, stop setting the (now obsolete) field
Then, remove the column entirely.
The text was updated successfully, but these errors were encountered:
Part of #3751
The column is kept for now because the migration is costly, but
since it's NULLable it should not be a problem. Deleting the
column is a follow-up task in the same issue.
Splitt from #3529
The
latest_version
field onAddon
points to, well, the latest (non-disabled) version. It's used by reviewer tools to figure out which version to review, and internally so set a few things.With the introduction of version channels, it won't be as useful, since you need to figure out the latest version available in the same channel you're interested in. We could add
latest_unlisted_version
andlatest_listed_version
fields, but that's probably overkill and won't scale if we decide to add more channels later.I want to try to get rid of that field, replacing it with a method that takes a
channel
and maybe an optional argument to ignore disabled versions. To do this safely, my plan is to do this in 3 steps:latest_version
property to emulate it, and modifying reviewer tools queries that directly hit the databaselatest_version
property with a method using the channelThe text was updated successfully, but these errors were encountered: