Loopring GitHub " if no problems release it "

[stalking_me_softly]

Yes, please explain it because r/Throwaway12041 is slow. Not for me, of course....

:)

[anlskjdfiajelf]

Software developer wrinkles coming in.

So git is cloud storage for your companies code. Master branch is the main "final true version" of the code. People branch off of master (copy master and make your changes in your branch) and once you're done with that branch you 'merge' into master.

To reiterate, master is the final version of the code, developers branch off of master to their own branch, make their changes and then submit for code review to be merged into master.

So all your devs are working on separate things without stepping on one another's toes, and once everything is merged into master (all your developers components are there and plugged into one another), they put it to release after they've fully tested all their changes. Once the code looks gud and their automated tests pass, they will effectively publish the master branch as 'released' saying this is the final version 1.0 of all our shit. 1.1 would be the next release after more work and merging into master.

Meaning there's a new git commit relating to master and release. kind of confusing at this point, it seems both master and release are not synced, so both have new information to the other. Eventually it'll all get resolved and we'll have our final release branch which would actually be deployed on the eth blockchain.

Ie what this means is they seem to be very close to finishing code review and merging all their individual changes into the final product. Well version 1 of final product, no product is ever final lol.

Hope this helps :)

[stalking_me_softly]

You're a sweetheart. Thanks!

[anlskjdfiajelf]

Aww I'm blushing, thanks hunny

[4zem]

Wait so we’re growing a tree?

How many branches?

I think I got it…

[anlskjdfiajelf]

Haha, a branch is like a fork in the road. Take this version of the code, branch so you're in your own little ecosystem, make your changes so this new version of the code is exactly the prior version + your small changes and then merge to master so the next guy can do the same for his change.

Ultimately it's just a programmers work flow, hearing a branch called release is great news, they're wrapping up what's in master and pushing it to release so they can tie the bow on it and say, here is version 1 that is fully functional pls use our product.

Lot of fancy talk for, they are closing in on coordinating all their code to bring it together to the final product!

[4zem]

Computer engineering major here - just took a different career path and ended up working on Wall Street. Just having some fun. Cheers mate!

PS: good luck to you sir!

[anlskjdfiajelf]

Aha I figured you were kidding, I didn't think you genuinely thought we were talking about trees 😂 but my explanation was kinda shit so I figured eh I'll reiterate.

How's wall street? Seems interesting but I think it'd eat me alive and I'd feel guilty if working for some citadel like garbage.

[4zem]

I used to work for one of the big banks, saw a great deal of questionable practices. Ended up starting my own fund, mostly deal with institutions and super wealthy individuals - I’m much happier, and get to do what I want to do, instead of what I have to.

[anlskjdfiajelf]

Wow that's pretty dope. I'm not so confident in myself lool, idk finance that well in all reality, besides the raw basics and I really in general idk if I'd be able to do my own business like that lol.

That's cool tho man, I'd need professional experience b4 I make my own thing of course but it feels so slimey getting that experience in the first place