Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Updating release engineering documentation

Hi Johna,

Thanks for doing this. There are a lot of new steps I didn’t know about. I like the GitHub checkboxes for this. It would be interesting to see if some of those steps could be automated or dropped eventually. Like:
- Do we still need Oomph? It’s broken most of the time and it’s a drag to maintain. I’ve never really been comfortable with generating the .target file from .setup file either. I would rather prefer doing it the other way around and not have the CDT build depend on Oomph.
- Can we configure eclipserun to use the same target platform as the rest of the build now? (Well it actually used to be like that at the very beginning but it got changed in Tycho)
- etc...


On Dec 11, 2019, at 12:03 PM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:

Hello folks,

I have started updating CDT's release engineering documentation to properly reflect what I am doing and to make sure I don't forget anything. It has become significantly more complicated in the past few years as we have added additional plug-in projects (launchbar and tools.template) and the more recent addition of Node & VS Code plug-ins.

I have done an experiment that I want to share with you. I created a new wiki for all of CDT's Infra on github and, for each release, I will be creating endgame bugs in that repo ( BTW I am using github issues because of the check boxes and placing it cdt-infra because of the cross-project concerns these cover.

Please let me know if this works for you all or if you have any concerns.

Thank you,

Jonah Graham
Kichwa Coders
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top