Perl 6 - the future is here, just unevenly distributed

IRC log for #pdl, 2015-08-15

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

All times shown according to UTC.

Time Nick Message
01:29 jberger joined #pdl
13:04 mohawk sivoais, glad to see 2.013 is out
13:04 mohawk now where's PDL::IO::GD?
15:06 mohawk .012 -> .013 exactly 2 months' gap
15:07 mohawk if the release manager is too busy then he needs to share the duty
15:07 mohawk there are people who depend on PDL and need bug-fixes in actual released code, not just on git master or a dev release
15:09 opkick [devops] mohawk2 commented on issue #1: If I run all of this, will I have a working Solaris vm?... http://git.io/v3Qoe
18:28 opkick [devops] zmughal commented on issue #1: More or less. I need to clean it up some more. Or I could package up my VM. :-P http://git.io/v374C
18:59 chm joined #pdl
19:00 chm mohawk: you haven't missed my email re PDL development (not just maint/co-maint)
19:01 chm mohawk: please as the people needing bug fixes to contact us via the PDL mailing list A
19:01 chm mohawk: please as the people needing bug fixes to contact us via the PDL mailing list ASAP
19:02 chm As you know, the PDL support is provided through that channel.
19:02 chm Please point out any bug reports/problems I may have missed.
19:02 chm mohawk: If anyone is "slowing things down for user problems" it was me for PDL-2.013
19:04 chm mohawk: the git model we're using does not allow for dev releases to meet user needs
19:04 chm mohawk, sivoais: we need to figure out something that can support PDL stability for users
19:05 chm and let major development continue more aggressive/agilely
19:05 mohawk chm, dev releases are not for that purpose
19:05 chm mohawk: I know that is the problem---they aren't being used but there is no alternative either.
19:06 mohawk i have no idea what you're saying
19:06 chm Maybe we could make a PDL bundle that is the way for generic PDL users to get a "good" PDL
19:06 mohawk that is what i am trying to achieve
19:06 mohawk that is what i have advocated a large number of times on pdl-devel
19:07 mohawk you haven't taken the first step towards that: release PDL::IO::GD out of the PDLPorters repo
19:07 mohawk or give me and sivoais co-maint on it
19:07 mohawk i am getting bored of saying the same thing over and over
19:08 chm The first step was to get a stable PDL-2.013 out.
19:09 chm I'm catching up with some PDL now.  You're saying that PDL::IO::GD is ready for an outside release to CPAN?
19:10 chm I'll take a look and let you know if I have problems on my end.
19:10 chm Personally, I would like to see a CPAN dev release with all the test fixes and low hanging fruit.
19:11 chm Now that PDL-2.013 is out it would be nice to take the opportunity for that.
19:12 chm Regarding an in-depth discussion, I'll write up something for pdl-devel for group discussion.
19:13 chm mohawk: If I missed your advocacy for a PDL bundle or other solution, I apologize.
19:15 chm mohawk: re: "dev releases are not for that purpose" in your opinion.
19:15 chm My opinion is that we need a way to maintain stability for PDL to avoid pushing broken official releases.
19:16 chm Admittedly, we've [ab]used the CPAN dev releases to allow for better testing and robustness.
19:16 chm I think it may make sense to reconsider the current git model.
19:17 chm What if the master became devel with the rebase workflow as currently with master.
19:17 chm Then devel gets pushed to master when there is an official CPAN release.
19:18 chm That would allow for fast updated to PDL in the dev releases and more time for stability for PDL official ones.
19:22 sivoais sorry, I'm on a slow network connection now and kind of busy. Makes it difficult to participate in the convo
19:22 chm sivoais: that's ok, my cable internet is dropping in and out...
19:28 sivoais I think I understand what you mean. There is a very well-known development workflow at <http://nvie.com/posts/a-successful-git-branching-model/> which does what you propose, if I understand correctly
19:29 sivoais it might be worth bringing this up on the list
19:29 sivoais I think at this point we are familiar with the "branch -> PR -> code review -> merge to master" workflow
19:30 mohawk on reflection, i'm sure i could have communicated better and more clearly
19:30 mohawk can the 3 of us have a google hangout / skype video call tomorrow?
19:30 sivoais and we can move towards this slightly more involved workflow
19:30 mohawk please set up a time (i have to step afk) and remember i'm in uk timezone :-)
19:38 sivoais I should be able to. There's scheduling tool called Doodle that I've used that helps [I'll be at my lab tomorrow, so I'll have a better connection :-P]
19:42 chm I don't have skype or hangout capability.  I will write up some ideas for the list.
20:12 sivoais yeah, my Skype/Hangout is limited to my phone. I don't know of any other easy conference call
23:37 mohawk i think a short reminder email to pdl-devel with hyperlinks to the several previous emails sivoais or i have sent on the "roadmap" might be useful
23:37 mohawk but on the evidence before us, probably not
23:54 opkick [devops] mohawk2 commented on issue #1: The position I'd like to be in is with a process to take the vagrantbox.es image, and build it into a dev box for us. That will ensure we have a clean box. If we then package that as an even easier way in, that's a separate step. http://git.io/v35EE

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