pepperdash/PepperDashCore
1
0
Fork 0
mirror of https://github.com/PepperDash/PepperDashCore.git synced 2026-04-12 03:57:08 +00:00
Code Issues Projects Releases Packages Wiki Activity
No description
153 commits 12 branches 447 tags 37 MiB
Find a file
Joshua Gutenplan 229723b50f Moved on ready to call on connect callback if shared key not required and connected. Moved text received event to else to get called on first message if shared key is off
2019-06-10 02:07:00 -07:00
CLZ Builds Updates CLZ Builds for release 2019-05-23 14:14:37 -06:00
Pepperdash Core Moved on ready to call on connect callback if shared key not required and connected. Moved text received event to else to get called on first message if shared key is off 2019-06-10 02:07:00 -07:00
.gitignore Post-merge sseclient compile for release package 2017-08-30 08:42:52 -05:00
Readme.md Updated Assembly version to 1.0.20. 2019-05-23 14:06:43 -06:00

Readme.md

Pepperdash Core

Workflow process

  • Create a Jira issue for the feature/bugfix. If you know you're targeting this update to coincide with a new release of Core, specify that release (or create a new one) as the Fix Version for the Jira issue
  • Branch from development using the syntax [feature/bugfix]/[pdc-x] (where x is the Jira issue number)
  • Modify code to suit and test. Make commits to the branch as you work.
  • Log a Pull Request on www.bitbucket.org and tag Heath and Neil as reviewers

Pull Request process

  • Check out the branch for the PR and review.
  • If necessary, merge the latest Development branch into the PR branch. Resolve any conflicts.
  • Increment the appropriate Assembly version number to match the next release in Jira
  • Build the project
  • Copy PepperDash_Core.cpz and PepperDash_Core.dll from the bin folder to the CLZ Builds folder in the repo root. Commit.
  • Merge the PR in Bitbucket