02:25:27 <luigi1112> .merges
02:25:27 -xmr-pr- 8250 8344 8662 8747 8850 8854 8888 8892 8894 8895 8899 8900 8901 8902 8903 8904 8905 8908 8909 8916 8917 8919
13:01:41 <sech1> .merges
13:01:41 <xmr-pr> Merge queue empty
13:01:47 <sech1> .3 release soon?
15:07:33 <selsta> sech1: .3.0 or .2.3? we have quite a lot of changes and could do .3.0
15:08:04 <sech1> .2.3 but I don't mind about .3.0
15:48:47 <Lyza> .3.0 sounds exciting ;P
15:57:18 <ofrnxmr[m]> .3.0 perhaps, since its a "recommended update" right?
17:54:44 <kantisan[m]> <detherminal[m]> "Hey, welcome to the community..." <- Hello, I was looking into this repo. I'm curious what this does differently than go-monero.
18:01:34 <jeffro256[m]> @woodser I released a fix here: https://github.com/monero-project/monero/issues/8932
18:01:46 <jeffro256[m]> Sorry here lol: https://github.com/monero-project/monero/pull/8937
18:02:08 <jeffro256[m]> There was like 3 different problems with that method 
18:41:21 <KVANT> Hey guys, maybe any MLSAG realization on Java?
18:42:02 <KVANT> if not, it would be fine to find the docs of tx signing realization in monero, cause it seems that there is not so much information about it
19:18:02 <woodser[m]> jeffro256: great, thanks!
19:23:14 <selsta> jeffro256[m]: can you check if the description in https://github.com/monero-project/monero/pull/8937 makes the issue auto close? maybe change it to "Resolves #8937 and:"
19:35:49 <jeffro256[m]> I changed the description and it added "Successfully merging this pull request may close these issues.
19:35:50 <jeffro256[m]> wallet2 fails to save to disk if first created in-memory " to the sidebar 
19:36:02 <jeffro256[m]> Is that what it should do?
20:22:40 <selsta> yes, looks good now