Perl 6 - the future is here, just unevenly distributed

IRC log for #onionsketch, 2017-02-14

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

All times shown according to UTC.

Time Nick Message
06:42 stevan joined #onionsketch
06:46 stevan joined #onionsketch
17:10 khw joined #onionsketch
18:15 reneeb joined #onionsketch
19:00 sawyer reneeb: o/
19:00 reneeb hi sawyer
19:01 kid51 joined #onionsketch
19:01 reneeb you might be interested in http://5-25-10.perl-services.de/ ;-)
19:01 sawyer reneeb: That looks really nice.
19:02 leont_ joined #onionsketch
19:03 sawyer reneeb: So shall we begin? :)
19:03 reneeb is tomorrow close enough to the release for the first round of the "on the day" actions?
19:03 reneeb sure
19:03 sawyer reneeb: Absolutely. Let's just go over all the items.
19:03 reneeb ok
19:04 sawyer I think the first round of things to do is just email everyone you need in order to get the release rights.
19:04 sawyer This includes RT, CPAN, git, etc.
19:05 reneeb who is responsible for the git permissions?
19:05 reneeb Andk already added me to the pumpking group, so PAUSE permissions are done.
19:05 sawyer Excellent.
19:05 sawyer Dennis is on Git (Seveas), but I'll contact him.
19:06 reneeb ok, thanks
19:07 sawyer Is there anything else there that isn't clear yet? Who to contact on what?
19:07 reneeb I have to check my old RT credentials. I think I had the permission to close issues. But I'll check later and email Ask if any action is required.
19:08 reneeb The release manager guide is great. It helps a lot!
19:08 sawyer If you email Ask, CC me.
19:08 reneeb So currently there is nothing unclear. This might change when it comes to the check of Dual-life modules.
19:08 sawyer That way I can easily reply with approve.
19:08 reneeb Ok, I'll CC you
19:08 sawyer Right.
19:09 reneeb When should I build the tarballs and publish them on the website? Thursday, Friday?
19:09 sawyer You will basically spend most of your time on two things: Documenting changes and running tests.
19:09 sawyer (Well, builds and tests.)
19:10 sawyer On the day of the release.
19:10 sawyer Which is the 20th.
19:10 reneeb Ok...
19:10 sawyer Because you're going to be running a lot of builds and tests, I suggest using grindperl.
19:11 sawyer https://metacpan.org/pod/grindperl
19:11 reneeb Ah, didn't know grindperl. Should I add my experiences to the release manager guide?
19:11 sawyer If it's not mentioned there, I think that would be good to add.
19:11 sawyer dagolden wrote it for that purpose.
19:11 sawyer (AFAIK)
19:11 sawyer So run grindperl in various configurations over these days. It's really sweet.
19:11 reneeb ok. It's not mentioned there...
19:11 sawyer The second thing is to start documenting stuff.
19:12 sawyer You will need to go over *all* commits and check whether they need to be documented. This takes the most amount of time.
19:12 reneeb I will start digging the commits tomorrow. How do I know if that's something that should be added to the perldelta?
19:12 sawyer I have a small VIM key command that opens up the commit of a given ID from a list of a collapsed git log. That way I note each commit I reviewed.
19:13 sawyer If you take a look at perldelta.pod, you will see the various comments left there under each section. The sections tell whether it needs to be documented.
19:13 sawyer However, some commits are part of one big change (so 10 commits can be one issue) or you just won't really even understand what commit does (which happens).
19:13 reneeb can I create a draft and you'll have a look at it on Friday?
19:14 sawyer Sure.
19:14 sawyer But you can just commit it to perldelta, that's fine.
19:14 sawyer You can also commit them on a branch for now and we'll use it later.
19:14 reneeb ok
19:14 sawyer I end up with several emails I send people explaining "You made this commit. Should it be added to perldelta? If so, how would you phrase it?"
19:15 sawyer People usually reply within a day or two. In almost every case it was "Nope, no need to document" or "Whoops! Let me add it."
19:15 reneeb that sounds good...
19:15 sawyer I think only once I had to add it myself after being explained how it should be documented.
19:15 sawyer The trick is to do this as soon as you can, so that's out of your way.
19:15 sawyer My first release I left it for that day and crambled from morning till 3am. :/
19:16 reneeb ;-)
19:17 sawyer Most actions can only be done on the day.
19:17 sawyer In most cases it's basically "run this script. run the tests. run this script. run the tests."
19:18 sawyer Take into account, you might hit a snag with Module-CoreList update. It's frustrating and can break easily. However, people are on #p5p and will help out. Specifically, BinGOs is a treasure with it. No matter how much I mess it up, he fixes it in two keystrokes. :)
19:18 reneeb yes, it's great that all those scripts exist.
19:18 sawyer Also, people will be on #p5p to help you. kid51 tends to clean up after releasers screw up. :)
19:19 reneeb :)
19:19 sawyer Any questions?
19:20 reneeb Not yet. As I start with the hard work tomorrow, I guess I will have some on Thursday (at latest).
19:21 reneeb You mentioned a second onionsketch.
19:21 sawyer Yup.
19:21 sawyer Let's do it a day or two before?
19:21 reneeb Do you prefer Friday or the weekend?
19:21 sawyer There might be specific steps that got you stuck.
19:21 sawyer Saturday is tricky, Friday would be better.
19:21 reneeb Ok, that's fine for me.
19:22 sawyer Excellent.
19:22 sawyer I'll make a note to fix the Git stuff. Anything else I can help with?
19:22 reneeb No, not at the moment.
19:23 reneeb Thanks for the information!
19:23 sawyer No problem!
19:23 sawyer Also, feel free to ask on #p5p. People will catch you if you fall, worry not. :)
19:24 reneeb I will ask...
19:25 sawyer Cool.
19:25 sawyer So we're done?
19:25 reneeb Yes.
19:25 sawyer \o/
19:25 sawyer Cool.
19:26 sawyer Let me know how's it going.
19:26 sawyer And I love the checklist page. :))
19:26 reneeb I'll add stuff every day.
19:27 sawyer +1 !
19:27 sawyer Till next time. :)
19:27 reneeb See you on Friday. Bye.
20:11 kid51 left #onionsketch
20:36 stevan joined #onionsketch
20:44 reneeb left #onionsketch
20:46 stevan joined #onionsketch
21:23 leont_ joined #onionsketch
22:40 stevan joined #onionsketch
22:55 stevan joined #onionsketch
22:56 leont_ joined #onionsketch

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