Welcome to jdm-java Discussions!

[jamesmarkchan]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[jamesmarkchan]

Hello @SebastianCerquera Hope you are well, I am restarting the jDiskMark project with the goal to add the ability for users to share their benchmarks on a web portal. Wondering if it might be interesting enough for you to join me for some development. Planning to use the MERN stack for the web portal. The last build has some overdue upgrades for the client like automatically dropping the disk cache before a read and loading of benchmark information when they are selected in the saved benchmark table.

https://sourceforge.net/projects/jdiskmark/

[SebastianCerquera]

Hi @jamesmarkchan, it sounds great, I haven't seen nice UI tools for this task.

[jamesmarkchan]

Welcome aboard and looking forward to working with you. Is there a feature or area that you have interest in? I know that there is the IOPS feature that you have some experience with already. Do you use discord?

[jamesmarkchan]

JDiskMark General Workflow

I'm used to the traditional gitflow but looks like there is also this simpler approach where features are created off of main and then merged back into it instead of having a dev and release branch. Right now I'll just keep with gitflow unless there is a case to simplify to githubflow.
https://docs.github.com/en/get-started/using-github/github-flow

Branches to be familiar with
master - our production branch
dev - the main development branch, features are branched and merged back into this
release - branched from dev when we want to stabalize and build a release, after a release is made, release is merged back into master and then master is merged back into dev.
[feature | bug]/<description> - branches created off of dev or release to implement a feature or fix a bug, these should be merged back into dev

[jamesmarkchan]

@lane1995 here is a quick tip on preserving history during file relocations:

use visual studio code! one thing you'll notice is that if you move a folder the changes might look like this before they are staged:

but if you stage them both and there are not any changes to the file at the same time, it will recognize the file as a rename and marks the single file as an "R"

if it does not usually because there are too many changes we want minimize the changes to the file so that git / vs code will be able to recognize that the file is the same entity but just relocated.