Perl 6 - the future is here, just unevenly distributed

IRC log for #onionsketch, 2016-06-10

| Channels | #onionsketch index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
12:42 sawyer joined #onionsketch
12:55 perigrin n
13:01 alh sawyer: o/
14:38 sawyer oh fuck me
14:38 sawyer we had an emergency to deal with
14:38 sawyer alh: sorry
14:38 sawyer is now good?
14:39 alh Sure, minus the fornicating
14:39 sawyer hah
14:39 sawyer alright
14:39 sawyer so, were there any thorny issues?
14:39 sawyer did you get anything done already on it?
14:39 alh To be honest, I haven't gotten into it yet, but I've briefly reviewed the RMG and my todolist, and it's looking pretty easy
14:40 sawyer i remember last time i wanted to add a few notes to the RMG
14:40 alh I'll catch up on p5p this weekend and tackle my current todos, and from there it's just making sure deltas are good
14:40 alh Do you remember what they were? :)
14:40 sawyer what i do is usually get my head sorted on the bigger issues (summaries FTW), then make a list of all the commits and go through them
14:41 alh Yeah; I just go through line-by-line of the git log. Slightly tedious but doesn't take terribly long
14:41 sawyer knowing the issues helps me realize quicker what a commit relates to and then find it in perldelta (which is often not updated even on the same day)
14:41 sawyer i have a trick i use with that, let me see...
14:42 sawyer i run somewhat the equivalent of this: git log --graph --pretty=format:'%h — %s (%cr) <%an>' --abbrev-commit --date=relative
14:42 sawyer save that in a file
14:42 sawyer in my vimrc (you use nano, right?) i have the following line: map <F3> :w !perl /home/sawyer/code/personal/p5p-summaries/bin/commit-review.pl<CR>
14:43 sawyer this basically says "when i press F3 run this script"
14:43 sawyer so i can mark a line (shift+v), then press F3
14:43 sawyer and the script fetches the commit and shows me the "git log -p" of said commit
14:43 sawyer it puts it into a pager, so when i press "q", i'm back in the browser
14:43 alh Nice
14:44 sawyer every commit i've verified as either "not important" or "is documented" i change the asterisk to bang or something
14:44 alh If I ever switch to vim I'll bug you for that script :)
14:44 alh The only other thing I want to bring up is.. don't know if you saw the conversation in p5p or not
14:44 sawyer i wouldn't be surprised if nano had a similar option
14:44 sawyer shoot
14:44 alh But one thing that would be good is if we got better at listing with Major releases and Maint releases which modules we broke at what versions
14:45 alh So... if we get a BBC for X at 1.0, and we submit a patch to their RT to fix it in 1.1, we should list with any version of Perl that we release that we broke X@1.0
14:45 alh We're okayish at this for new releases when blead is finalized, but not so much when backporting
14:45 alh I think adding something to the RMG will help, but I'm not sure what else to do about it
14:46 sawyer there is a category in perldelta for "Modules and Pragmas"
14:47 sawyer we could add a subcategory saying "CPAN Compatibility"
14:47 alh Might not be a bad idea. I think historically it's wound up in "Known Issues"
14:47 sawyer with each entry being "Module X @ 1.0 does not work, see RT#..." (and perhaps other relevant issue tracker URLs, though they should be linked in the RT ticket)
14:47 alh I wonder if I should craft an email to the list and gather opinions
14:47 sawyer oh, sorry, that would be a better place
14:47 sawyer good idea
14:48 alh Yeah, we sort of do it. The harder part is making *sure* we do it. And maybe that's just awareness
14:48 alh But aside from that, I think this release should be standard
14:48 sawyer one thing i want to start doing with RT is tagging
14:48 sawyer one tag would be "BBC"
14:49 sawyer considering we have a version entry there, plus the tag for "BCC", it should be easy for the RMG script (or a different one) to add those to the perldelta for the release manager
14:49 alh Yeah that could be nice
14:50 sawyer we can still attempt it because most BBC tickets have "Bleadperl breaks" in the title
14:50 sawyer (and that's how I write them in the summaries, too, I believe - at least I should)
14:50 * alh nods
14:51 sawyer two things that would make all of this easier was if people documented changes quickly (same commit, commit after), or at least put all the relevant commits in a branch :/
14:51 sawyer (both are not too often)
14:51 alh yeah...
14:51 sawyer also, consider that the earlier the release is in the cycle, it is more likely you will have to chase down developers for "what do these commits really do, and should they be added to the perldelta?"
14:52 sawyer i did that on every release i made
14:52 alh As our new fearless leader I'm confident you'll find a way to improve this :)
14:52 sawyer however, you're more likely to understand the commits than I am :)
14:52 alh Hardly!
14:53 sawyer I'll think of something *rubs beard*
14:53 alh But yes, I'll try to get a bunch of that going before we're too close to the deadline
14:53 alh Added an entry for the 14th to do that. Plenty of lead time
14:53 sawyer yup
14:54 sawyer also, andk and rezic could probably help out in finding all the BBC cases
14:54 alh Yeah they're good about that :)
14:57 alh Cool; anything else?
15:43 sawyer not from me
15:43 sawyer (sorry, didn't see the message until now)
15:43 sawyer alh: thank you
15:43 alh np, cheers
15:44 sawyer cheers
15:46 khw joined #onionsketch

| Channels | #onionsketch index | Today | | Search | Google Search | Plain-Text | summary