Jody here, sorry I have been a bit quiet on release automation front. I would like to shadow the upcoming 3.8.3 release and automation as many steps as I can :).
I have reviewed the release instructions, and would like to assemble a shopping list of credentials and access required:
Can I request commit access for core-release repo to manage some build scripts (is this repo still in use?). GitHub username is “jodygarnett”.
Create a “gnbuild” user or similar with GitHub credentials to tag releases.
Jody here, sorry I have been a bit quiet on release automation front. I would like to shadow the upcoming 3.8.3 release and automation as many steps as I can :).
I have reviewed the release instructions, and would like to assemble a shopping list of credentials and access required:
Can I request commit access for core-release repo to manage some build scripts (is this repo still in use?). GitHub username is “jodygarnett”.
Create a “gnbuild” user or similar with GitHub credentials to tag releases.
From a product stability standpoint making a 3.10-RC with the work from Chambéry would make sense.
Do you have any contractual/customer obligations to see this work in an official release, by a set time, etc…
For release automation I am focused on automating the release packaging and publishing.
For major releases I expect a few manual steps when creating new branches / build jobs / documentation…
From a product stability standpoint making a 3.10-RC with the work from Chambéry would make sense.
Do you have any contractual/customer obligations to see this work in an official release, by a set time, etc…
No contractual obligations, but master is already on production this morning and other projects are currently being updated to it too.
I don’t think we have customer requesting releases - So far, releases were done when someone takes the time to make it.
For release automation I am focused on automating the release packaging and publishing.
For major releases I expect a few manual steps when creating new branches / build jobs / documentation…
Jody here, sorry I have been a bit quiet on release automation front. I would like to shadow the upcoming 3.8.3 release and automation as many steps as I can :).
I have reviewed the release instructions, and would like to assemble a shopping list of credentials and access required:
Can I request commit access for core-release repo to manage some build scripts (is this repo still in use?). GitHub username is “jodygarnett”.
Create a “gnbuild” user or similar with GitHub credentials to tag releases.
From a product stability standpoint making a 3.10-RC with the work from Chambéry would make sense.
Do you have any contractual/customer obligations to see this work in an official release, by a set time, etc…
No contractual obligations, but master is already on production this morning and other projects are currently being updated to it too.
I don’t think we have customer requesting releases - So far, releases were done when someone takes the time to make it.
For release automation I am focused on automating the release packaging and publishing.
For major releases I expect a few manual steps when creating new branches / build jobs / documentation…
Jody here, sorry I have been a bit quiet on release automation front. I would like to shadow the upcoming 3.8.3 release and automation as many steps as I can :).
I have reviewed the release instructions, and would like to assemble a shopping list of credentials and access required:
Can I request commit access for core-release repo to manage some build scripts (is this repo still in use?). GitHub username is “jodygarnett”.
Create a “gnbuild” user or similar with GitHub credentials to tag releases.
