Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-release, 2016-01-22

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
07:45 FROGGS joined #perl6-release
09:30 ely-se joined #perl6-release
09:30 ely-se left #perl6-release
09:36 masak joined #perl6-release
14:53 FROGGS joined #perl6-release
15:05 MadcapJake joined #perl6-release
15:11 MadcapJake I think we should release stable 2016.n and dev 2016.n+1 every month
15:12 MadcapJake Rakudo, spec, and roast would all have to maintain the same release pattern, right?
15:13 MadcapJake Even doc could follow and then we could have a dropdown to select which version of spec you're looking for docs from.
15:14 jnthn No, langauge versions != Rakudo versions
15:15 jnthn I'm planning to work on a draft of a user-facing doc on how this stuff works for us to review on this channel
15:16 jnthn (Was way too busy this week doing things at $dayjob, mostly 'cus I spent the first half of January recovering from 2015... :))
15:16 [Coke] jnthn: thank you. I think our first release in 2016 will avoid that by just being 6.c bugfixes, but we will need a plan by the march rakudo release. (that we start cleaning up in february)
15:16 jnthn [Coke]: Yes, indeed
15:17 jnthn I think we can make more of a push on the 2016.01 or so next week when nine++ and TimToady++ are back from vacation, and I may have a few more tuits.
15:17 jnthn It'll be Feb before I'm reasonably well tuited again though.
15:17 [Coke] I will as well; dayjob project finishing up next week.
15:17 jnthn :)
15:17 [Coke] jnthn: yup. january's just a bad month for the team, esp. after december. :)
15:18 jnthn Well, it's a good month in so far as we probably *needed* to slow down a bit after December. :)
15:22 MadcapJake though i do understand that rakudo != language, I still feel that new rakudo releases will be adding new things to spec, either for new features or to handle newly fixed bugs.  So there should at least be some kind of match up.  Like 6.c-2016.01 or something (kind of long but still)
15:23 MadcapJake not will be adding, but should be adding
15:35 [Coke] MadcapJake: the plan is to segregate out dev stuff with use statements
15:36 MadcapJake ahh i see
15:36 [Coke] rakudo will, if plan continues, have a single compiler release that includes a 6.c stable default and a 6.d developmental track available with a "use"
15:37 MadcapJake ok, then we'd have a 6.d version of spec too?
15:38 jnthn Yeah, and there may be a few 6.c.1, 6.c.2, etc. which will be more minor fixes.
15:39 jnthn But to give people a language version they can depend on.
15:40 MadcapJake yeah agreed, so the letter signifies major interface changing/breaking releases, while the number would signify new but non-breaking functionality?
15:41 jnthn Well, more likely fixes you can rely on having 'cus the spec (that is, tests) include them
15:41 jnthn Generally, I expect 6.d, 6.e, etc. to be the things we focus marketing around (more likely under names like Christmas, Divali, etc.)
15:41 MadcapJake ah ok, so could be a slight difference in interface, but only (I assume) to solve some bug/technical problem
15:42 jnthn Right. It's *really* tricky in many cases to classify something as "clearly a bug fix" vs "clearly a breaking change".
15:42 MadcapJake maybe there should be a clear set of guidelines for what constitutes entry into a number release and what constitutes entry into a letter release
15:43 jnthn Yes, that's what I was planning to try and write down :)
15:43 MadcapJake ok! Well sounds like you got this! :P
15:44 jnthn We'll see :)
15:44 jnthn No plan survives contact with the enemy. :)
15:44 jnthn But we can set off in a direction we feel is decent, and tweak it as we learn.
15:44 MadcapJake unless we bomb them first!
15:46 * MadcapJake notices he's the only American in the room
15:47 MadcapJake yeah, i think having a set of questions like "does this feature require more than one change to spec?" or "does this feature significantly change the interface to said problem area?" and so on
15:48 MadcapJake heck let's get a working group at the ISO! :D
15:54 [Coke] MadcapJake: I also from and in the US. :)
15:54 [Coke] *am
15:55 MadcapJake [Coke]: oh good so you can appreciate a good bomb dropping! ;)
15:56 MadcapJake totally kidding, i'm not a hawk in the slightest.  Not very good at sarcasm, I guess :)
16:01 MadcapJake hey was wondering, what is preventing R* being released? Feel like that's a biggy that's kind of been missed (esp since 2015.12 didn't happen). I wish I was equipped to help with that :( if there's anything anyone needs an intermediate-level programmer's time on, let me know!
16:04 stmuk MadcapJake: its in scrollback .. available from web interface if you don't have that
16:06 stmuk maybe testing nine's candidate branch 2016.01-preparation might help
16:07 MadcapJake stmuk: never heard of it, how do i find it?
16:07 stmuk it's a git branch under the main rakudo repo
16:08 MadcapJake oh no, i know where to find that, i meant the scrollback communitt
16:08 MadcapJake nothing under perl6, rakudo
16:10 stmuk http://irclog.perlgeek.de/perl6-release/2016-01-22#i_11925893
16:11 MadcapJake ahh so just lots of people out on vacation right now
16:24 [Coke] not just, but that doesn't help
16:25 [Coke] 1) some bugs in 2015.12 release that need fixing before an R* 2) commits on nom that are spec-breaking 3) trying to come up with a dev/release mechanism that lets us have spec breaking and spec preserving modes 3) realizing that's a ton to bite off when right now we just need a bugfix release  (more)
16:26 [Coke] 4) trying to figure out how to make just a bugfix release 5) everyone is really busy with stuff after Christmas.
16:28 PerlJam 6) we don't want to accidentally make the situation worse by rushing to cut a release  :)
16:59 MadcapJake Ok, that all makes sense for sure.  I think the rakudo.org site should have a new post made discussing 2015.12 release of compiler, status on next R*, and maybe some discussion of how the release schedule will be going forward.  The last entry on rakudo.org is from november for 2015.11 beta release.  Feels completely left out of the release hubbub.
17:00 [Coke] it was
17:50 TimToady joined #perl6-release

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary