1206575 - SeaMonkey 2.40* and 2.41* versions missing from AMO

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Administration, defect)

Description

[Robert Kaiser]

For a long time now, new SeaMonkey versions apparently have been added together with Firefox etc. version but that apparently stopped, and the current Nightly version 2.40a1 and the upcoming-this-week Nightly version 2.41a1 (as well as their variants for later stages of the trains) are missing from AMO, even though their parallel Firefox versions for the 43 and 44 trains do exist.

I found that today when I wanted to upload theme versions that were marked compatible up to current Nightly, and ran into errors because of invalid versions (I adjusted my install.rdf to only go up to 2.39 for now).

Can we get that fixed and the newer versions added? Thanks!

Comment 1

[Mathieu Agopian [:magopian]]

:jorgev, :jason, we usually rely on the "update_product_details" management command to update those versions, right? Do we need to do anything else?

Is it an issue with the https://github.com/mozilla/django-product-details library?

Comment 2

[Robert Kaiser]

Hmm, does that mean you get the info from the SeaMonkey website? If so, can you point me to the URL it checks just so I can check if the team needs to correct something there? May very much be possible. ;-)

Comment 3

[Robert Kaiser]

The URL I know is http://www.seamonkey-project.org/seamonkey_versions.json and it at least has the current versions right.

Comment 4

[Robert Kaiser]

That said, the file above was stalled for some time on older versions and only was updated to the correct versions on September 8 by https://hg.mozilla.org/SeaMonkey/seamonkey-project-org/diff/c3431eb49d4b/lib/config.tmpl

Comment 5

[Mathieu Agopian [:magopian]]

I'm not sure where django-product-details gets the information, I think from mozilla central? Maybe we simply need to run it manually on prod to make sure it's updated with the information from the 8th of sept?

Jason, could you give it a try?

Comment 6

[Robert Kaiser]

hmm, https://hg.mozilla.org/comm-central/log/default/suite/config/version.txt did get all the updates on time (and probably will get another one today when the merge happens, being bumped to 2.41a1).

Comment 7

[Jorge Villalobos [:jorgev] (he/him)]

Version numbers are added somewhat manually. I file a bug like bug 1196410 so the new versions are added. I stopped adding SeaMonkey versions a while ago since I found out the versions being added were way ahead and the release process had slowed down. It would be useful for me if I knew what the expect release cadence is, since it isn't in sync with Firefox. Alternatively, someone can prod me when I should add new versions :)

Comment 8

[Jorge Villalobos [:jorgev] (he/him)]

Filed bug 1206791 to do the version bumps.

Comment 9

[Robert Kaiser]

The expected release cadence is still 6 weeks, but the team had issues with the build machines (and is not completely out of the woods yet, but far enough to produce releases again).

Comment 10

[Jorge Villalobos [:jorgev] (he/him)]

Okay, the new versions have been added, and it sounds like I should just continue adding a new version per release cycle as before. I think we're done here.

Comment 11

[Robert Kaiser]

Thanks a lot!

And I can confirm that the versions are there now :)