#Go SDK 0.1.0 release

1 messages · Page 1 of 1 (latest)

winter ivy
#

.

#

Summary:

  • @turbid rock is release owner. He's implementing the plan we discussed last week for go modules, repo layout etc.

  • @wise rock is launch owner. She's tracking elements of this release + other releases to fit them into the overall launch, make sure it all makes sense end to end

Please check with these two 👆🏻 before doing anything, to avoid crossing beams

WHERE WE NEED HELP (possibly incomplete list):

  • Go examples are broken by recent changes in import path and API

  • Examples by @balmy meadow are also broken for the same reason. He is at Kubecon and may not have the time to fix this today.

  • .. that's it for now but not for long I think 🙂 Just staying nearby and ready to help with the release if need be, would be great.

Thanks!

balmy meadow
#

As soon as the new repo structure is set I can go through and update the examples and guide!

hollow bough
#
  • Go examples are broken by recent changes in import path and API
    As in the extensions under examples in the repo? Just double checking
winter ivy
#

In the new Go SDK docs primarily. But yes, probably that too

turbid rock
#

welcome back @hollow bough 🙂

hollow bough
winter ivy
hollow bough
#

I'm timeboxing myself to 12:30 to fix the cache import issue so David can be unblocked (literally never been so mystified in my life, buildkit is just ignoring cache imports, I'm at the point where I am rebuilding buildkit locally and adding println debugging to it).

I will take a look at fixing examples at that time if no one else has. Or if the timing means we need that ASAP I'll just do it right now

winter ivy
#

@hollow bough good plan

balmy meadow
turbid rock
hollow bough
#

Synced up with Andrea, I'll go through the examples and update them now. There will also be an update to import paths needed after andrea finishes the separate repo tooling but he has a script to update all import paths so I'll just focus on any API updates needed

sweet knoll
#

nice. I'm mostly on standby atm, tending to my garden of PRs none of which block release, so anyone can feel free to @ me with any tasks that pop up

#

I can pick up @balmy meadow 's examples if you're doing the SDK docs ones @hollow bough

hollow bough
wise rock
#

thank you both!

hollow bough
#

is the final import url going to be go.dagger.io or just dagger.io? In our go.mod it's just dagger.io

sweet knoll
#

@hollow bough last I heard, dagger.io/dagger

#

we figured out how to make that work

hollow bough
wise rock
#

@balmy meadow 👆

winter ivy
#

If anyone has spare cycles, one way to possibly improve the launch experience: if there's an easy way of inserting little examples directly in the go docs... That would be sweet

#

not sure how easy that is, or if it causes problems elsewhere... But I don't see how we can go wrong making or go docs more useful out of the box

#

also @turbid rock can anyone help on the release heavy lifting?

turbid rock
#

Yes -- can someone help @floral lance with the reviews on the CUE side? I'm stuck on the Go side

winter ivy
#

Sure

turbid rock
#

current status -- can't push to a different repo from gh action, if anyone has a clue on that

winter ivy
#

Is it a permission issue?

winter ivy
turbid rock
#

push with inlined "password" (token) has been deprecated in august

#

as in it's no longer working

#

other than that, pretty close

#

@winter ivy also, any idea on the SDK repo name? dagger/dagger-go? dagger/dagger-sdk-go?

sweet knoll
turbid rock
#

except their workaround isn't working out

balmy meadow
turbid rock
#

yep, just don't know how to use that PAT

balmy meadow
#

Ahh I see. I haven’t done this more recently than august so I’m no help 🙂

shell tinsel
#

any help still needed on GHA issue?

winter ivy
#

now dealing with a whole new set of problems 😁