-
ruaok
reosarevok: agreed, but we're hoping to get there too
2019-12-16 35057, 2019
-
reosarevok
If you want to do what we do, you should release every 2 weeks or 1 mo even if it's just one small patch :)
2019-12-16 35010, 2019
-
ruaok
1 mo is what I would like.
2019-12-16 35012, 2019
-
reosarevok
(tiny improvements > no improvements anyway!)
2019-12-16 35023, 2019
-
iliekcomputers
reosarevok: how do you deal with incomplete stuff? Just not merge it?
2019-12-16 35039, 2019
-
iliekcomputers
Like stuff thats basically done but has small things that need to be fixed
2019-12-16 35010, 2019
-
ruaok
or "get this merged, so this PR can go away. smaller fixes PR coming very soon."
2019-12-16 35016, 2019
-
reosarevok
Usually not merge it until it's fixed, but depends on what "fixed" means
2019-12-16 35031, 2019
-
iliekcomputers
Yeah, I think that makes sense to me.
2019-12-16 35034, 2019
-
reosarevok
Is it "this is an improvement but we could improve it even more with X"? Merge, send second PR
2019-12-16 35043, 2019
-
ruaok
hmmm. maybe we should approve PRs and then make a new branch off the approved branch for the fixes PR
2019-12-16 35057, 2019
-
reosarevok
Is it "this is kind of a mess but we can improve it"? Then fix before merge :p
2019-12-16 35007, 2019
-
ruaok
but not merge into master until follow up PR is complete.
2019-12-16 35008, 2019
-
iliekcomputers
Let's merge stuff to master only when we're completely ready to release it next cycle.
2019-12-16 35022, 2019
-
ruaok
which is what I am trying with the lb-labs tests with pristine__ right now
2019-12-16 35032, 2019
-
ruaok
agreed.
2019-12-16 35052, 2019
-
iliekcomputers
And aim for monthly releases?
2019-12-16 35059, 2019
-
ruaok
oh, that brings about a natural next question: what is the least amount of stuff we need to do in order do do a release?
2019-12-16 35006, 2019
-
ruaok
that should inform the goal of our next release.
2019-12-16 35052, 2019
-
iliekcomputers
I think having a schedule and not caring about the amount of work done is a better way to go here.
2019-12-16 35021, 2019
-
ruaok
I dont think the two are mutually exclusive.
2019-12-16 35029, 2019
-
iliekcomputers
Keeping goals independent of releases.
2019-12-16 35033, 2019
-
ruaok
my point is more "lets not start more stuff, but push a release soon"
2019-12-16 35047, 2019
-
iliekcomputers
That I agree with
2019-12-16 35000, 2019
-
ruaok
that was my main point there.
2019-12-16 35043, 2019
-
iliekcomputers
Hmm.
2019-12-16 35050, 2019
-
ruaok
but lets just agree on the "if it aint release for release, do not merge to master" right now, shall we?
2019-12-16 35058, 2019
-
iliekcomputers
+1
2019-12-16 35037, 2019
-
ruaok
then we work towards the first release with the goal of soon thereafter doing monthly releases.
2019-12-16 35057, 2019
-
iliekcomputers
Yep, sounds like a plan.
2019-12-16 35059, 2019
-
ruaok
which also means that 1 release = 2 work periods.
2019-12-16 35005, 2019
-
ruaok
nice cadence, I think.
2019-12-16 35043, 2019
-
iliekcomputers
So right now, I have two things incomplete.
2019-12-16 35050, 2019
-
iliekcomputers
Stats and Incremental dumps
2019-12-16 35014, 2019
-
ruaok ponders priorities
2019-12-16 35017, 2019
-
iliekcomputers
Incremental dumps is a cron job that we can just stop until we get around to fixing it.
2019-12-16 35025, 2019
-
iliekcomputers
So it isn't exactly blocking
2019-12-16 35039, 2019
-
ruaok
what is the problem with the incremental dumps?
2019-12-16 35048, 2019
-
ruaok
how broken are they?
2019-12-16 35002, 2019
-
iliekcomputers
There were some listens missing/more in a dump.
2019-12-16 35022, 2019
-
ruaok
yes. anything else?
2019-12-16 35027, 2019
-
iliekcomputers
That's it.
2019-12-16 35038, 2019
-
ruaok
I mean, this is a needle in a hackstack problem, but just tyring to get the scope.
2019-12-16 35046, 2019
-
iliekcomputers
Yeah
2019-12-16 35053, 2019
-
iliekcomputers
I spent a few days looking at it
2019-12-16 35058, 2019
-
iliekcomputers
But didn't really find anything
2019-12-16 35025, 2019
-
ruaok
let take another evening and have you talk me through the process.
2019-12-16 35029, 2019
-
iliekcomputers
Plus it's a PITA to debug because it needs actual dumps which are created really slowly.
2019-12-16 35039, 2019
-
ruaok
and I'll look at code as we go. I think a second set of eyes might make this a lot easier.
2019-12-16 35044, 2019
-
iliekcomputers
Yeah, having a new set of eyes on it would be good.
2019-12-16 35048, 2019
-
iliekcomputers
++
2019-12-16 35005, 2019
-
ruaok
I hear that -- the MSID mapping has been frustrating because each full run takes 1-2 hours.
2019-12-16 35029, 2019
-
ruaok
and there are a lot of little things to try -- at least now I can use partial data sets that run much faster.
2019-12-16 35052, 2019
-
ruaok
ok, lets plan to do that walk through in the comings days.
2019-12-16 35010, 2019
-
ruaok
user stats. lots of open items in the doc.
2019-12-16 35036, 2019
-
ruaok
shall we make a Week of Dec 16 section and start looking for things to toss in?
2019-12-16 35010, 2019
-
iliekcomputers
Or put in trello?
2019-12-16 35026, 2019
-
ruaok
I see bugs, completing features and needed features as three categories.
2019-12-16 35051, 2019
-
ruaok
my brainpower is dwindling TBH -- that flight home was rough.
2019-12-16 35007, 2019
-
ruaok
let's make a new section and then tomorrow I'll move them to trello.
2019-12-16 35033, 2019
-
iliekcomputers
sure, sounds good.
2019-12-16 35042, 2019
-
ruaok
(50 screaming teenagers caused 20 babies to freak out, causing teenagers to scream louder because they couldn't hear each other)
2019-12-16 35058, 2019
-
ruaok
I think I found a new worst case scenario for noise cancelling head-phones.
2019-12-16 35027, 2019
-
iliekcomputers
if you want, we can just stop here. the process discussion was really helpful and I could easily prioritize work for these 2 weeks myself.
2019-12-16 35013, 2019
-
iliekcomputers
noise cancelling headphones are ⭐⭐
2019-12-16 35018, 2019
-
ruaok
that would be nice, but it feels incomplete to me. shall we do more tomorrow?
2019-12-16 35028, 2019
-
ruaok
and pick a time that is earlier?
2019-12-16 35045, 2019
-
ruaok
noise cancelling headphones were only so effective!
2019-12-16 35020, 2019
-
SothoTalKer
but what about noise as music genre?
2019-12-16 35046, 2019
-
iliekcomputers
hmm. sure! we can pick it up tomorrow. would 7-ish work?
2019-12-16 35017, 2019
-
ruaok
might be closer to 8 for me, but round then, yeah.
2019-12-16 35042, 2019
-
iliekcomputers
that works better for me too, tbh. :D
2019-12-16 35025, 2019
-
iliekcomputers
thanks ruaok, the process discussion has been really helpful
2019-12-16 35007, 2019
-
ruaok
for both of us!
2019-12-16 35018, 2019
-
ruaok
oh, did a new volunteer pop in over the weekend?
2019-12-16 35040, 2019
-
ruaok
if not, I'll follow up. did you see his email to support@?
2019-12-16 35002, 2019
-
iliekcomputers
Don't think I did
2019-12-16 35009, 2019
-
sbvkrishna has quit
2019-12-16 35004, 2019
-
n1tr0maverick joined the channel
2019-12-16 35028, 2019
-
rahul24 joined the channel
2019-12-16 35038, 2019
-
BrainzGit
2019-12-16 35039, 2019
-
BrainzBot
2019-12-16 35031, 2019
-
n1tr0maverick has quit
2019-12-16 35002, 2019
-
rahul24 has quit
2019-12-16 35052, 2019
-
n1tr0maverick joined the channel
2019-12-16 35039, 2019
-
thomasross_ joined the channel
2019-12-16 35039, 2019
-
thomasross has quit
2019-12-16 35039, 2019
-
thomasross_ is now known as thomasross
2019-12-16 35044, 2019
-
yvanzo
reosarevok: sure :)
2019-12-16 35053, 2019
-
thomasross has quit
2019-12-16 35016, 2019
-
rahul24 joined the channel
2019-12-16 35054, 2019
-
thomasross joined the channel
2019-12-16 35001, 2019
-
sarthak_jain has quit
2019-12-16 35016, 2019
-
rahul24 has quit
