Idea - CI/CD Pipeline about agopengps HOT 2 CLOSED

Hey @farmerbriantee I'm looking for some thoughts on branching strategy.

Currently how it seems to me the path to get into master is through the Development branch. Is this something you would like to persist going forward?

If we have a CD/CD pipeline I'm not sure that it would be necessary. I would recommend just having the master branch then everybody can pull request into master. We would nightly release all merges into master but but would only stable release tagged master commits.

Since I have the releases working my next step is to remove the compiled source out of the repository since it will no longer be needed.

Thoughts?

from agopengps.

The master branch of my fork has been updated to rip out the compiled build directory. All but 2 dll's were able to be pulled in via nuget package.

The following dll's were not able to be pulled in via nuget:

1. RepeatButtonControl.dll
2. Common.dll

I'm not exactly sure that common.dll is actually used anywhere but the repeatButtonControl is defiantly used. In the meantime I have moved them into the dependencies folder with the GPS project.

For the references I pulled in via nuget we should be able to now see where we can bump versions. It looks like we are a couple major versions behind on some packages.

from agopengps.