Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-cloud-dev] CDT.Cloud Blueprint Community Release

Actually added Paul/Colin to CC list this time.

Paul, Colin, please see below and sorry if you receive this in duplicate if you are already subscribed to the dev list.

Jonah Graham
Kichwa Coders

On Wed, 5 Oct 2022 at 14:32, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
Hi Philip,

I seem to have left this a little late, but I pushed the code to update cdt-gdb-vscode to 0.0.93 and tested that the blueprint works with it*.

However, I am stuck as I have never uploaded a new version to open-vsx. It has long been on my todo list and I think I was granted permission(?) a while ago, but never did a release.

I believe Colin or Paul did the previous pushes (based on this PR)? I have cc'ed them on this email for advice.

I'm just not sure what I should be doing here and any advice is most welcome.

* The way I did this was run a local webserver so I could serve up cdt-gdb-vscode-0.0.93.vsix from my local machine and update the package.json(s) files to have this: 


Jonah Graham
Kichwa Coders

On Wed, 28 Sept 2022 at 13:51, Philip Langer <planger@xxxxxxxxxxxxxxxxx> wrote:
Hi everyone,

The Theia Community Release will be available by tomorrow (Sep 29th, 2022) [1].

Thus, I'd like to ask you to do the following steps for your component until *Oct 6th*:

[ ] Run a final test of your components with the Thea Community Release to ensure it is compatible
[ ] Publish a release of your component (unless a currently published release is already compatible)
[ ] Reply to this message *by Oct 6th* indicating the published version of your component that is compatible
[ ] Get your component listed as compatible on the Theia release page [2]

As soon as we have your component versions, we'll upgrade blueprint and start testing.
If all goes well, we'll publish a new blueprint version based on the Theia Community Release soon after that.

The list of dependencies in blueprint that need to be updated can be found in the package.json [3].

If there are any obstacles or issues with that plan, please contact me anytime!

Thank you very much for your effort!


On Mon, Aug 29, 2022 at 7:05 PM Philip Langer <planger@xxxxxxxxxxxxxxxxx> wrote:
Hi everyone,

The 1.29.0 "August release" of Theia [1] is available and we can start using it as a release candidate for the upcoming Community Release of Theia [2] to prepare the components.

Please make sure you test your components with this version ahead of time and be prepared to provide a release of your component that is compatible by the end of September.
This will not only make sure the components are compatible with the first Community Release of Theia for convenient consumption by adopters, but it is also a prerequisite for publishing a Blueprint version based on the Theia Community Release.

Therefore, I suggest the following process:
  1. Each component starts testing with the Theia Release Candidate and fix potential issues during September
  2. Once the Theia Community Release is available (end of September), run a final test and release a version that is compatible with the Theia Community Release
  3. I'll send out a mail on this mailing list end of September asking for the versions of each component to be consumed by Blueprint
  4. We'll update Blueprint to those versions and do some integration testing
  5. If all goes well, we'll publish a Blueprint version based on the Theia Community Release and all updated components in the course of October
Also, please also consider adding your component to the Theia Community Release page [3] for enhanced visibility of your component and for strengthening the Theia Community Release.

I'm looking forward to this collaborative release which we can celebrate at EclipseCon! :-)

Thanks and best wishes,


On Wed, Aug 17, 2022 at 4:14 PM Philip Langer <planger@xxxxxxxxxxxxxxxxx> wrote:
Hi everyone,

As discussed in our previous community meeting, we would like to encourage all components to participate in the first Theia Community release, which will be released in September [1]. Basically that means releasing a version of your component or extension that is compatible and has been tested with the Theia community release (release candidate to be released in the end of August).

If you plan to participate with your component, please add your component as a participating project on the Theia releases page [1] by opening a PR at the Theia website repo [2] beforehand. This already increases the visibility of every participating component.

Once the release candidate is available, I'll send another email to collect the component releases so that we can include them in the next blueprint release.

Thanks and best wishes,


cdt-cloud-dev mailing list
To unsubscribe from this list, visit

Back to the top