Anyone else skips build numbers that ends with 9 or is it just me 😅

@ThatDude lol just noticed that, I just skipped version code 169 in favor of 170 😅

@ThatDude I hate it since I was a kid,have no clue why 🙄

@ThatDude is it a disease that needs to be cured 🤔

@Alice lol yup everyone keeps skipping it lol
@ThatDude @gitblame 9 😛

I think I'll begin to set version numbers in octal in my projects. Problem solved.

@cafecortado or in binary 😅🤔

@gitpush imagine. Your second build release will have v10. And by the time you reach 4, it's gonna be v100. Just wondering Devs using this module.

You weirdos :D

@github ya thats the down side of it, but later on the app will be released under different package name, we will be resetting counter anyways

@gitpush keep changing the package name. Like PackageV100 next edition is PakageV1 😂😂
People may get confused which one is real and which one is fake. Virus Devs gonna love it coz no one will be clear which one is the real package.

@github @gitpush just use binary versioning :D

@olezhka we are talking about binary versioning only..

@github I'm sorry, I'm potatoing today

@olezhka btw, did you created xmlrant?

@github yeah

@olezhka awesome dude. Great to meet you. You made a simple yet cool stuff using devrant. Kudos for your efforts.

@github thanks, man, glad you liked it! Tbh, I really liked jsrant so got inspired from it, and this proved a perfect opportunity to explore asp.net core + ci ^_^

@olezhka ya. Implementing a project with a technology we want to earn is the best way I think. Recently, I got interested in learning python to make libraries that can be installed using pip and have proper unit tests and ended up writing devrant api wrapper in Python. It's a great way to learn realtime.

@github sounds cool! Devrant will end up being a testground for all the things we developers might want to try! :D

@olezhka lol. Hahaha. So true.

@github no bro what I meant is, the one I'm publishing now is demo hence package name ends with .demo
While full version has a different one

@gitpush oh. I interpreted it differently. It make sense now, a package for devo/test release and later another for prod release makes more sense..
Though I am more interested in how people takes it if the versions roll out in binaries..

@github they won't 😅😂