Create new track for "data-science-stack"

store-requests tracks
1

Hi,

I would kindly request to get a new track created for the data-science-stack snap. Right now we are currently using latest, but this is not appropriate as we would like to release to a stable risk with a proper track naming.

We have discussed between engineering and product (being this snap a product natively originated in Canonical), and it seems appropriate to both teams to start to go for the following track name:

  • 1/<risk>

Do not hesitate to reach out, should there be any further question.

Thanks, Enrico

2

Hi,

The 1 track has been created as requested.

Thanks,

Odysseus

1 Like
3

Thanks you for the help, @odysseus-k !!

Best, Enrico

4

Hi @odysseus-k

After some thought and consideration with product, we would like to also create major.minor tracks under the 1/ track, namely:

  • 1.0/
  • 1.1/

Can we also enable the track-creation-guardrails (TCG )to allow us to manage major.minor track versions without dedicated request?

Let me know if you need any further information to move this request forward

Thanks Enrico

5

create major.minor tracks under the 1/ track

Could you clarify what you mean by this? The new tracks would be separate from the existing 1 track. In other words, after this change, the data-science-stack would have the 1, 1.0 and 1.1 tracks available.

Can we also enable the track-creation-guardrails (TCG )to allow us to manage major.minor track versions without dedicated request?

Of course! Do you have a specific guardrail in mind, or would a simple \d+\.\d+ pattern work?

Thanks,

Odysseus

6

Hi @odysseus-k

Thanks for the prompt reply!

In other words, after this change, the data-science-stack would have the 1 , 1.0 and 1.1 tracks available.

yes, yes, that’s fine. I just meant that we wanted to support 1.0 and 1.1. Of course we will take care of making sure that 1/ align with the correct subtrack, but yes, from a store perspective, the are separate tracks.

Of course! Do you have a specific guardrail in mind, or would a simple \d+\.\d+ pattern work?

Yes, that’s fine! Your proposal looks great to me! Let me know when the TCG is in place such that I can rollout the creation of 1.0 and 1.1

Thanks!!

7

Hi,

The guardrails have been created as requested.

Thanks,

Odysseus

1 Like
8

thank you @odysseus-k !!!

9

Actually, @odysseus-k , I have tried to create the tracks myself using the API but I’m not sure how. I tried to follow this, this or this (which I have found in the net), but these refer to charmhub, not snapstore, and the API/CLI tooling seems a bit different (e.g. export is replaced by export-login, macaroon token has a slight different format, the API don’t fully comply).

Do you have a reference on how to do this self served? Or should you create the track? Also the UI does not seem to have the “Request track” feature/option anymore

Any guidance on how to proceed is very much appreciated

Thanks Enrico

10

Hmm, that’s strange. Maybe @Lukewh can help here?

In the meantime, I’ve gone ahead and created both tracks for you. I’ll also try to find the documentation for the process.

Br,

Odysseus

11

Here is the snapshot of what I see. I believe I used to see also “Request track”. Anyhow, let me know if you need any further info

Screenshot from 2025-02-14 19-12-01

12

Hi @deusebio!

For the Add/Request track option on the UI, can you make sure you are logged in and also clear your cookies and try again? If this is still not working, can you check if there are any errors in the console?

Thanks!

13

Oh, now it works! Probably the cookie cleanup did that. I’m sure I was already correctly logged in, as the view of the tracks is a private one, and I’m sure I cannot log to that view for other SNAPs apart from the one I own.

Anyhow, I believe it is now resolved. Attached a snapshot of what I see in my UI.

Thanks for the help Enrico

Screenshot from 2025-02-19 13-42-47