When building projects using the Remoting SDK, one challenge I often face is managing collaboration across different developers. The SDK makes it easier to handle distributed applications, but when multiple people are working on the same project, keeping track of tasks, issues, and progress can sometimes get complicated.
I’ve been exploring different ways to organize development workflows so that everyone stays aligned and avoids duplication of work.
Clear task tracking, integration with version control, and issue management all seem essential when teams are working on complex remote services. Checked https://docs.remotingsdk.com/ guide for reference .
That’s where project management tools come in. For example, I recently looked into what is jira and how it helps teams manage software projects more efficiently.
Has anyone here tried using Jira or similar tools to improve how they organize tasks while working with Remoting SDK? Would love to hear how you integrate such tools with your development process.
Jira works for project management, but i personaly find it a bit convoluted, as it is very focused om precie Agile methodology. As Eugene stated, internally we use GitLab for version control and bug/tast tracking here at RemObjects; we also use GitHub for some version control, and i’ve personally used GitHub’s uug tracking for other projects in the past, but i find it very limited, compared to GitLab (or Jira).
These are the main three tools i can speak to for this task;
I’m afraid i don’t have any brilliant insights to using the specifically with project that use Remoting SDK. One option to consider are whether you want to version control Remoting SDK as a third prty dependency or not.
In the first case, after instaling it you’d copy the relevant distributable .dlls to, e.g., .\Dependencies folder in your project, and include them in Git; that way everyone on the team gets the same copies, and you can manage the versions with your branches. (remember you still need a license for every team member ;). One downside is, that you can run into merge confllicts if teo branches update to different versions – Git isn’t really made for binary files.
I’ve never found that sort of approach necessary for me or projects i assisted on, so for the second case its easy – jsut have everyone install Rmeoting SDK from the installer and use that copy – and make sure everyone stays more or less up to date.
The SDK makes it easier to handle distributed applications, but when multiple people are working on the same project, keeping track of tasks, issues, and progress can sometimes get complicated.
