-
m-relay
<dormouse:matrix.org> Branch is not a release, fuckhead.
-
m-relay
<dormouse:matrix.org> Study your git workflows.
-
m-relay
<ofrnxmr:xmr.mx> yo, dumbass
-
m-relay
<ofrnxmr:xmr.mx> A tag is a code freeze
-
m-relay
<ofrnxmr:xmr.mx> You cant "fix the tag" dumbass
-
m-relay
<dormouse:matrix.org> And the freeze is for release purposes, yes.
-
m-relay
<ofrnxmr:xmr.mx> The release branch is where tags come from, and where fixes are pushed to
-
m-relay
<dormouse:matrix.org> You can create a new one that becomes the new release.
-
m-relay
<ofrnxmr:xmr.mx> Releases dont work that that around here
-
m-relay
<dormouse:matrix.org> Using unreleased versions is bad. It creates even more schizo behavior for developers that already support fuckton of distros and whatnot.
-
m-relay
<ofrnxmr:xmr.mx> We dont just "tag a new release"
-
m-relay
<ofrnxmr:xmr.mx> Especially not for 6 commits and a cmake issue
-
m-relay
<ofrnxmr:xmr.mx> We dont have unreleased versions, we have released versions and branches for that the versions are cut from
-
m-relay
<ofrnxmr:xmr.mx> We dont have unreleased versions, we have released versions and branches that the versions are cut from
-
m-relay
<dormouse:matrix.org> Are you implying that there won't be an 18.4.1 or an 18.5.0 release?
-
m-relay
<ofrnxmr:xmr.mx> Yes
-
m-relay
<dormouse:matrix.org> And a respective tag?
-
m-relay
<ofrnxmr:xmr.mx> The next release will likely be 19, branched from master and cur from there
-
m-relay
<dormouse:matrix.org> Can somebody verify if the above is true?
-
m-relay
<dormouse:matrix.org> Seems bullshit to me.
-
m-relay
<ofrnxmr:xmr.mx> If there is another 18 release, it will be 1841, but were overdue branching from master
-
m-relay
<ofrnxmr:xmr.mx> So 19 is the way its looking
-
m-relay
<ofrnxmr:xmr.mx> Regardless, the branch that 1841 would be cut from, is already fixed. This issue should be closed. Its not actionable
-
m-relay
<dormouse:matrix.org> Now that is some sensible text for once.
-
m-relay
<plowsof:matrix.org> dormouse close as completed please thank you
-
m-relay
<r4v3r23:monero.social> anonero enforced bg sync so gotta wait for jberman to take a look
-
m-relay
<r4v3r23:monero.social> wait looks like there are changes already
-
m-relay
<r4v3r23:monero.social> ill test it this week
-
m-relay
<ofrnxmr:xmr.mx> My testing went badly
-
m-relay
<ofrnxmr:xmr.mx> tor syncs with pr 9936 were significantly slower than master
-
m-relay
<ofrnxmr:xmr.mx> Lan syncs had no difference
-
plowsof
didnt see a huge change in my background sync test
monero-project/monero #9936#issuecomment-2910844236
-
m-relay
<dormouse:matrix.org> I haven't verified new versions work, shouldn't be me then.
-
m-relay
<dormouse:matrix.org> I will do that once I have it built tho.
-
m-relay
<r4v3r23:monero.social> ok will wait then
-
m-relay
<monerobull:matrix.org> does this make syncing via node in LAN faster?
-
m-relay
<monerobull:matrix.org> i already get 10k blocks per second :D
-
m-relay
<monerobull:matrix.org> looks like it doesnt
-
m-relay
-
m-relay
<monerobull:matrix.org> the circlejerk in here is funny
-
m-relay
<monerobull:matrix.org> yeah, we are oh-so scared of the bch-ers telling everyone how much better bch is than monero
-
m-relay
<monerobull:matrix.org> to the point where we preemptively shadowban the entire subreddit :P
-
m-relay
-
m-relay
<rbrunner7:monero.social> (It got removed, but the URL tells it, doesn't it)
-
m-relay
<dormouse:matrix.org> Don't get fooled.
-
m-relay
<dormouse:matrix.org> Monero is Bitcoin as pictured by Satoshi.
-
m-relay
<dormouse:matrix.org> There is even a btc forum post by Satoshi where he talks about ring signatures.
-
m-relay
<dormouse:matrix.org> He knew BTC wasn't perfect for privacy and wanted to improve on that.
-
m-relay
<hendrick234:matrix.org> Any Cashapp? Chime ?Zelle? Skill?Apple Pay? Pay pal? Venmo? BOA? Wells Fargo? Chase? Wells Fargo? PNC? Navy federal? Credit union? M&T bank? Northwest bank? Att &t? BOA? or other local bank? JOIN THE TELEGRAM CHANNEL 👇👇👇👇
-
m-relay
<hendrick234:matrix.org>
t.me/+ioqje81ziAYyYTc0