| --- Log opened Sun Mar 17 00:00:13 2013 | ||
| -!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout] | 00:26 | |
| -!- heiko [~heiko@5ac1f59f.bb.sky.com] has joined #shogun | 01:32 | |
| -!- heiko [~heiko@5ac1f59f.bb.sky.com] has left #shogun [] | 01:50 | |
| -!- shogun-notifier- [~irker@7nn.de] has joined #shogun | 02:18 | |
| shogun-notifier- | shogun: Sergey Lisitsyn :master * ce73ba2 / src/shogun/lib/tapkee/ (19 files): https://github.com/shogun-toolbox/shogun/commit/ce73ba244b96ffdf01f132184f53c831df8197ff | 02:18 |
|---|---|---|
| shogun-notifier- | shogun: Last update of tapkee before release | 02:18 |
| shogun-notifier- | shogun: | 02:18 |
| shogun-notifier- | shogun: - Much more doc | 02:18 |
| shogun-notifier- | shogun: - Various code improvements (better naming, less warnings) | 02:18 |
| -!- heiko [~heiko@5ac1f59f.bb.sky.com] has joined #shogun | 02:28 | |
| -!- heiko [~heiko@5ac1f59f.bb.sky.com] has left #shogun [] | 02:52 | |
| shogun-buildbot_ | build #358 of rpm1 - libshogun is complete: Failure [failed test] Build details are at http://www.shogun-toolbox.org/buildbot/builders/rpm1%20-%20libshogun/builds/358 blamelist: Sergey Lisitsyn <lisitsyn.s.o@gmail.com> | 03:33 |
| -!- votjak [~votjak@host-46-241-3-209.bbcustomer.zsttk.net] has joined #shogun | 03:50 | |
| -!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout] | 05:18 | |
| -!- hoijui [~hoijui@dslb-088-074-124-160.pools.arcor-ip.net] has joined #shogun | 06:40 | |
| @sonney2k | blackburn, make prepare-release ran through here! | 08:11 |
| @sonney2k | blackburn, so we could release - but question is if we don't better fix the label bug in static interfaces? | 08:11 |
| @sonney2k | always returning real valued outputs is important | 08:12 |
| -!- wiking [~wiking@huwico/staff/wiking] has joined #shogun | 09:00 | |
| -!- shogun-notifier- [~irker@7nn.de] has joined #shogun | 09:47 | |
| shogun-notifier- | shogun: Soeren Sonnenburg :master * 731cbde / src/ChangeLog: https://github.com/shogun-toolbox/shogun/commit/731cbde006d6cf9ee7f8d6c188b211de26a3d986 | 09:47 |
| shogun-notifier- | shogun: updated changelog | 09:47 |
| shogun-notifier- | shogun: Soeren Sonnenburg :master * b97829a / doc/pages/ (4 files): https://github.com/shogun-toolbox/shogun/commit/b97829a764ec077b07169939382bc9ae30e301d4 | 09:47 |
| shogun-notifier- | shogun: updated reference documentation | 09:47 |
| shogun-notifier- | shogun: Soeren Sonnenburg :master * cc2410f / src/shogun/ui/SGInterface.cpp: https://github.com/shogun-toolbox/shogun/commit/cc2410f56db398e71e34ffd651645682fc9905b9 | 09:47 |
| shogun-notifier- | shogun: support various label types in static interface | 09:47 |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has joined #shogun | 10:02 | |
| -!- sidi_ [~sidi@14.139.122.114] has joined #shogun | 10:10 | |
| -!- zxtx [~zv@75-59-238-10.lightspeed.sntcca.sbcglobal.net] has joined #shogun | 10:10 | |
| shogun-buildbot_ | build #815 of deb2 - static_interfaces is complete: Failure [failed test octave_static] Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb2%20-%20static_interfaces/builds/815 blamelist: Soeren Sonnenburg <sonne@debian.org> | 10:12 |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has quit [Quit: leaving] | 10:26 | |
| shogun-buildbot_ | build #816 of deb2 - static_interfaces is complete: Success [build successful] Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb2%20-%20static_interfaces/builds/816 | 10:37 |
| shogun-buildbot_ | build #359 of rpm1 - libshogun is complete: Failure [failed test] Build details are at http://www.shogun-toolbox.org/buildbot/builders/rpm1%20-%20libshogun/builds/359 blamelist: Soeren Sonnenburg <sonne@debian.org> | 10:58 |
| blackburn | sonney2k: I finally managed to wake up | 11:22 |
| blackburn | sonney2k: so we can release? | 11:23 |
| @sonney2k | blackburn, I think so | 11:58 |
| @sonney2k | blackburn, and good morning russia :) | 11:58 |
| blackburn | sonney2k: heh I was having fun with cmake whole night so it is not morning already | 11:59 |
| * sonney2k runs make release | 11:59 | |
| blackburn | okay I've got to write a mail | 11:59 |
| blackburn | sonney2k: is it late to update news? | 12:00 |
| @sonney2k | make data-release fails :/ | 12:00 |
| @sonney2k | blackburn, ohh what do you want to do? | 12:00 |
| blackburn | sonney2k: I forgot to mention that last bug | 12:01 |
| blackburn | sonney2k: ah it is already here hah | 12:01 |
| blackburn | sonney2k: I tried to fix that, but failed to do that right | 12:01 |
| @sonney2k | blackburn, oh #*$#YH! | 12:01 |
| blackburn | sonney2k: what's up? | 12:01 |
| @sonney2k | we forgot to increase data counter | 12:01 |
| @sonney2k | in NEWS | 12:01 |
| blackburn | ahm | 12:01 |
| @sonney2k | blackburn, so add whatever you need to NEWS | 12:02 |
| @sonney2k | and change data to 0.5 | 12:02 |
| blackburn | sonney2k: what about parameter version? | 12:02 |
| @sonney2k | I would say doesn't matter | 12:03 |
| @sonney2k | we screwed that anyways | 12:03 |
| @sonney2k | ohh and please mention that bug I hopefully fixed | 12:03 |
| @sonney2k | about sg('lclassify') returning -1/+1 labels | 12:03 |
| blackburn | got it | 12:03 |
| shogun-buildbot_ | build #360 of rpm1 - libshogun is complete: Failure [failed test] Build details are at http://www.shogun-toolbox.org/buildbot/builders/rpm1%20-%20libshogun/builds/360 blamelist: Soeren Sonnenburg <sonne@debian.org> | 12:04 |
| blackburn | sonney2k: done | 12:05 |
| shogun-notifier- | shogun: Sergey Lisitsyn :master * a0e0d95 / src/NEWS: https://github.com/shogun-toolbox/shogun/commit/a0e0d95f03d03528e89e5b56bc7767846c9a064e | 12:05 |
| shogun-notifier- | shogun: Updated NEWS | 12:05 |
| @sonney2k | blackburn, SGString is not based on SGReferencedData | 12:11 |
| @sonney2k | news is still telling this | 12:12 |
| blackburn | sonney2k: yes | 12:12 |
| blackburn | ahhhh | 12:12 |
| blackburn | oops | 12:12 |
| blackburn | sonney2k: string list is though | 12:12 |
| @sonney2k | yeah | 12:13 |
| shogun-notifier- | shogun: Sergey Lisitsyn :master * 89d073b / src/NEWS: https://github.com/shogun-toolbox/shogun/commit/89d073bcdcbb14cbec897f632d6585969ed3a467 | 12:13 |
| shogun-notifier- | shogun: SGString is not based on SGReferencedData | 12:13 |
| @sonney2k | blackburn, ohh and the date is 03-17 :) | 12:13 |
| blackburn | ahah | 12:14 |
| @sonney2k | blackburn, do you fix it? | 12:14 |
| blackburn | sonney2k: yes | 12:14 |
| shogun-notifier- | shogun: Sergey Lisitsyn :master * 9702994 / src/NEWS: https://github.com/shogun-toolbox/shogun/commit/970299480069e165da69e6dae5a32e0aad7ae116 | 12:14 |
| @sonney2k | or shall I | 12:14 |
| shogun-notifier- | shogun: Fixed date of release | 12:14 |
| @sonney2k | ok | 12:14 |
| * sonney2k runs make-prepare-release again | 12:15 | |
| @sonney2k | blackburn, look at this... http://shogun-toolbox.org/buildbot/builders/rpm1%20-%20libshogun/builds/360/steps/test/logs/stdio | 12:15 |
| @sonney2k | something weird is going on | 12:15 |
| blackburn | sonney2k: I am quite sure it is a heisenbug | 12:16 |
| blackburn | sonney2k: all libshogun examples pass on my machine - so we play with probabilities haha | 12:16 |
| @sonney2k | blackburn, it is real on this machine - fails for some time now... | 12:21 |
| @sonney2k | no idea tough | 12:21 |
| @sonney2k | it works everywhere else | 12:21 |
| @sonney2k | blackburn, anyway prepare the announcement email in an hour so so we should be ready | 12:21 |
| blackburn | sonney2k: alright | 12:21 |
| @sonney2k | blackburn, argh _ don't really know how to properly udpate the website | 12:29 |
| blackburn | sonney2k: what do you mean? | 12:30 |
| @sonney2k | previously make release did fully take care of this | 12:30 |
| @sonney2k | make update-website | 12:30 |
| blackburn | ahh | 12:30 |
| blackburn | heh | 12:30 |
| @sonney2k | but now NEWS is not automatically parsed :/ | 12:30 |
| -!- heiko [~heiko@5ac1f590.bb.sky.com] has joined #shogun | 12:30 | |
| @sonney2k | blackburn, I need n4nd0 I guess or bern4rd | 12:31 |
| blackburn | sonney2k: asked him to join #shogun | 12:31 |
| @sonney2k | heiko, soon soon | 12:32 |
| heiko | sonney2k: release? :) | 12:32 |
| @sonney2k | heiko, yeah - we would have one if NEWS was upto-date | 12:32 |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has joined #shogun | 12:32 | |
| heiko | sonney2k: blackburn fixed another bug yesterday, that could go in there | 12:33 |
| @sonney2k | heiko, already in | 12:33 |
| @sonney2k | heiko, release date was wrong too :) | 12:33 |
| @sonney2k | n4nd0, I am lost again with the website | 12:34 |
| heiko | sonney2k: haha :) | 12:34 |
| @sonney2k | n4nd0, we need to change it to 2.1 and NEWS too | 12:34 |
| n4nd0 | sonney2k: what? | 12:34 |
| n4nd0 | was does it imply to change it to 2.1 and what do you want to change of the NEWS? | 12:34 |
| @sonney2k | n4nd0, we have that new version available and 2.0 on the website | 12:39 |
| @sonney2k | I am trying to figure out how to cahgne it to 2.1 | 12:40 |
| @sonney2k | the news file I figured out by now | 12:40 |
| @sonney2k | n4nd0, sigh it is an image! | 12:43 |
| n4nd0 | sonney2k: like everything in the webpage :D | 12:44 |
| @sonney2k | n4nd0, except the text :D | 12:44 |
| @sonney2k | n4nd0, now I would wish I knew the font | 12:45 |
| @sonney2k | blackburn, let us introduce version subtiles | 12:47 |
| blackburn | sonney2k: subtiles? | 12:47 |
| @sonney2k | like 'mighty iceberg' | 12:47 |
| blackburn | hah | 12:47 |
| blackburn | +1 | 12:47 |
| @sonney2k | any suggestions? | 12:48 |
| blackburn | sonney2k: borsch | 12:48 |
| -!- heiko [~heiko@5ac1f590.bb.sky.com] has quit [Quit: Leaving.] | 12:48 | |
| blackburn | sonney2k: vodka | 12:48 |
| @sonney2k | blackburn, I don't know if "In vodka we trust" will gain us users :D | 12:49 |
| @sonney2k | wiking, n4nd0, what do you guys drink over there | 12:49 |
| @sonney2k | blackburn, "Powered by Vodka, Beer and Mate" | 12:50 |
| blackburn | sonney2k: girls and vodka | 12:50 |
| blackburn | sonney2k: if I didn't make any mistake there were ~8900 commits since last release | 12:53 |
| blackburn | I am afraid I did | 12:54 |
| blackburn | :D | 12:54 |
| blackburn | yeha 9705 totally | 12:55 |
| blackburn | I got wrong | 12:55 |
| blackburn | 805 | 12:55 |
| @sonney2k | blackburn, not good | 12:57 |
| -!- sidi_ [~sidi@14.139.122.114] has quit [Read error: Connection reset by peer] | 12:57 | |
| @sonney2k | too much between releases | 12:57 |
| blackburn | sonney2k: not good what? | 12:57 |
| blackburn | ah | 12:57 |
| @sonney2k | lets release more often | 12:57 |
| blackburn | sonney2k: I did count that to impress people | 12:58 |
| blackburn | :D | 12:58 |
| wiking | sonney2k: palinka | 12:58 |
| wiking | sonney2k: mmm do we have tag? | 12:59 |
| wiking | blackburn: which one is the release commit? | 12:59 |
| blackburn | wiking: palyonka in russian is a slang name for pirate vodka made of some shit like acetone | 12:59 |
| @sonney2k | blackburn, wiking n4nd0 - current subtitle is (for real!) Powered by Vodka, Beer and Mate. | 12:59 |
| @sonney2k | I could still exchange beer (as I dont' drink any) | 13:00 |
| blackburn | wiking: I don't know, put any commit made on 1st of sept | 13:00 |
| blackburn | :D | 13:00 |
| wiking | :>> | 13:00 |
| wiking | and 2.1? | 13:00 |
| blackburn | wiking: I hope 2.1 will be tagged now | 13:00 |
| wiking | oookeey | 13:01 |
| wiking | lets see | 13:01 |
| wiking | when is it coming? :) | 13:01 |
| * sonney2k is uploading the release | 13:01 | |
| wiking | woohooo | 13:01 |
| wiking | ok so then we have a commit version already | 13:01 |
| @sonney2k | (make update-webpage) | 13:01 |
| wiking | sonney2k: can u copy-paste here | 13:01 |
| @sonney2k | $ git branch | 13:01 |
| @sonney2k | master | 13:01 |
| @sonney2k | * shogun_2.1 | 13:01 |
| wiking | is that pushed? | 13:02 |
| wiking | seems not yet | 13:02 |
| @sonney2k | git tag | grep shogun_2. | 13:02 |
| @sonney2k | shogun_2.1.0 | 13:02 |
| @sonney2k | wiking, not yet | 13:02 |
| wiking | ok so shall we create a dev branch? | 13:02 |
| @sonney2k | uploading first | 13:02 |
| wiking | called dev or development | 13:03 |
| @sonney2k | yes dev is long enough | 13:03 |
| wiking | cool | 13:03 |
| wiking | let's go with that then | 13:03 |
| wiking | so from now on all the stuff go into dev | 13:03 |
| wiking | and keep master as stable..? | 13:04 |
| wiking | or the other way round | 13:04 |
| wiking | keep master as development branch | 13:04 |
| wiking | and create a stable? | 13:04 |
| @sonney2k | blackburn, do you recall that email from ?#?$# on the mailinglist about proper git development? | 13:04 |
| wiking | anyhow the default branch on github should be the stable branch | 13:04 |
| blackburn | sonney2k: yes | 13:04 |
| @sonney2k | he suggested a scheme that we figured woudl be very useful | 13:04 |
| @sonney2k | I cannot find it | 13:05 |
| blackburn | hmm | 13:05 |
| -!- sidi_ [~sidi@14.139.122.114] has joined #shogun | 13:05 | |
| @sonney2k | (as usual) | 13:05 |
| blackburn | sonney2k: he was mentioned in news I think | 13:05 |
| blackburn | sonney2k: evan shelhamer | 13:05 |
| wiking | https://github.com/diaspora/diaspora/wiki/Git-Workflow | 13:06 |
| wiking | it's with git flow | 13:06 |
| wiking | pretty handy tool | 13:06 |
| wiking | we could start using that | 13:07 |
| shogun-buildbot_ | build #361 of rpm1 - libshogun is complete: Failure [failed test] Build details are at http://www.shogun-toolbox.org/buildbot/builders/rpm1%20-%20libshogun/builds/361 blamelist: Sergey Lisitsyn <lisitsyn.s.o@gmail.com> | 13:18 |
| wiking | ok dev branch is there | 13:24 |
| wiking | i'll try start using git-flow | 13:25 |
| blackburn | sonney2k: writing mails is pain sometimes haha | 13:36 |
| @sonney2k | blackburn, releases etc should be uploaded | 13:37 |
| @sonney2k | doc is still uploading | 13:37 |
| blackburn | sonney2k: mail is not yet ready anyway | 13:37 |
| @sonney2k | http://shogun-toolbox.org/ | 13:41 |
| @sonney2k | doc is still uploading though | 13:42 |
| wiking | hehe: https://github.com/vigsterkr/shogun/tree/feature/ChangeReleaseHash | 13:45 |
| wiking | with git flow | 13:45 |
| wiking | but afaik in this case PR-ing our code is useless | 13:47 |
| wiking | i mean if we choose to go with git-flow | 13:48 |
| wiking | then we should directly work on shogun.git | 13:48 |
| wiking | because in that case PR is an unecessary overhead | 13:48 |
| wiking | i mean this for the developers who has write access to the shogun.git | 13:48 |
| wiking | as fetching around from other developers' repos features | 13:49 |
| wiking | is really just a painful overhead | 13:49 |
| blackburn | wiking: I do believe PRs for core devs is overhead | 13:51 |
| shogun-notifier- | shogun: Soeren Sonnenburg :master * 6ce4431 / src/ChangeLog: https://github.com/shogun-toolbox/shogun/commit/6ce44315fdc21bfee6876d006201530c3c28d885 | 13:51 |
| shogun-notifier- | shogun: updated changelog | 13:51 |
| shogun-notifier- | shogun: Soeren Sonnenburg :master * 1b1130d / doc/Doxyfile: https://github.com/shogun-toolbox/shogun/commit/1b1130d2ca8f48e97737caa405ede519abe70253 | 13:51 |
| shogun-notifier- | shogun: Preparing for new Release shogun_2.1.0 | 13:51 |
| shogun-notifier- | shogun: Soeren Sonnenburg :master * e6138dd / src/ChangeLog: https://github.com/shogun-toolbox/shogun/commit/e6138ddfb06ea1ad193a2a3c0f941a7bfadff26b | 13:51 |
| shogun-notifier- | shogun: Preparing for new Release shogun_2.1.0 | 13:51 |
| shogun-notifier- | shogun: Soeren Sonnenburg :shogun_2.1 * 96e8031 / src/shogun/lib/versionstring.h: https://github.com/shogun-toolbox/shogun/commit/96e803197bed1d1253060e4050f7e4791e302315 | 13:51 |
| shogun-notifier- | shogun: Tagging shogun_2.1.0 release | 13:51 |
| shogun-notifier- | shogun: Soeren Sonnenburg :shogun_2.1 * 463c42b / doc/ (5 files): https://github.com/shogun-toolbox/shogun/commit/463c42b49e9b35e274379217b85b0e3faef283f6 | 13:51 |
| shogun-notifier- | shogun: update example list | 13:51 |
| @sonney2k | blackburn, any update on the release email? | 13:54 |
| blackburn | sonney2k: just a few minutes | 13:54 |
| blackburn | sonney2k: want to read it before? | 13:57 |
| @sonney2k | blackburn, send it | 13:57 |
| wiking | email sent | 13:58 |
| wiking | btw: sorry for my shitty explanation, but i'm a bit hangover :P | 14:00 |
| blackburn | wiking: palinka? | 14:02 |
| blackburn | sonney2k: n4nd0: wiking: see the mail | 14:02 |
| @sonney2k | http://mloss.org/software/ | 14:03 |
| @sonney2k | announcement is on mloss.org | 14:03 |
| @sonney2k | n4nd0, please twitter about the release! | 14:03 |
| blackburn | sonney2k: I'll do | 14:03 |
| wiking | blackburn: yes :) | 14:03 |
| wiking | blackburn: where's the email | 14:04 |
| blackburn | wiking: sent minute ago | 14:04 |
| wiking | on the list? | 14:05 |
| blackburn | wiking: I am afraid it was send by russian post | 14:05 |
| @sonney2k | blackburn, didn't see it | 14:05 |
| blackburn | haha alright lets wait | 14:05 |
| @sonney2k | blackburn, did you sent it out? | 14:06 |
| @sonney2k | d | 14:06 |
| blackburn | sonney2k: yes | 14:06 |
| @sonney2k | blackburn, to which address? | 14:06 |
| blackburn | sonney2k: I just forwarded it to you | 14:06 |
| blackburn | sonney2k: did you receive? | 14:07 |
| blackburn | sonney2k: may be something is wrong with @shogun-toolbox.org address | 14:08 |
| @sonney2k | blackburn, yes arrived | 14:08 |
| @sonney2k | oscar winning email :D | 14:08 |
| blackburn | sonney2k: a glitch of mailing list? | 14:08 |
| n4nd0 | sonney2k: will tweet and put something in g+ | 14:09 |
| n4nd0 | when it appears in the webpage | 14:09 |
| -!- votjak [~votjak@host-46-241-3-209.bbcustomer.zsttk.net] has left #shogun [] | 14:09 | |
| blackburn | n4nd0: ok let you do it :) | 14:09 |
| blackburn | sonney2k: I am afraid - what should I do, re-send? | 14:12 |
| blackburn | :D | 14:12 |
| @sonney2k | blackburn, relax and wait? | 14:14 |
| @sonney2k | blackburn, I send some news blob to freshmeat too | 14:14 |
| blackburn | sonney2k: ok lets wait then | 14:17 |
| @sonney2k | posted to G+ | 14:18 |
| @sonney2k | posted to blog and thus debian planet | 14:22 |
| shogun-buildbot_ | build #362 of rpm1 - libshogun is complete: Failure [failed test] Build details are at http://www.shogun-toolbox.org/buildbot/builders/rpm1%20-%20libshogun/builds/362 blamelist: Sergey Lisitsyn <lisitsyn.s.o@gmail.com> | 14:22 |
| wiking | sonney2k: if we start using dev branch, shouldn't we switch buildbots to use that? | 14:23 |
| @sonney2k | wiking, we need to discuss how we do things | 14:23 |
| blackburn | sonney2k: I could send it again may be | 14:23 |
| @sonney2k | maybe this evening? | 14:23 |
| wiking | kk | 14:23 |
| wiking | any idea when heiko will be around again? | 14:24 |
| @sonney2k | too bad he left | 14:24 |
| @sonney2k | I figured some issues in the relese Makefile | 14:26 |
| @sonney2k | where how do I fix this? | 14:26 |
| @sonney2k | wiking, btw is it properly tagged now? | 14:26 |
| blackburn | sonney2k: https://github.com/shogun-toolbox/shogun/tags | 14:26 |
| blackburn | sonney2k: https://mloss.org/software/viewstats/372/ can you view that? | 14:27 |
| wiking | sonney2k: seems so | 14:29 |
| @sonney2k | blackburn, yes why? | 14:31 |
| blackburn | sonney2k: strange peak :D | 14:31 |
| blackburn | sonney2k: still don't understand what happened | 14:31 |
| blackburn | sonney2k: its tapkee downloads | 14:31 |
| @sonney2k | blackburn, is that tapkee? | 14:31 |
| @sonney2k | ahh | 14:31 |
| blackburn | err views | 14:31 |
| @sonney2k | same date as http://mloss.org/software/viewstats/2/ ? | 14:32 |
| @sonney2k | no | 14:32 |
| @sonney2k | whatever | 14:32 |
| blackburn | sonney2k: near | 14:32 |
| @sonney2k | blackburn, wiking n4nd0 - so now we need to a) decide about future development process (maybe even with irc meetings from time to time!) b) workshop announcement / advertisement c) gsoc planning | 14:34 |
| @sonney2k | application | 14:34 |
| blackburn | sonney2k: next week is to *finish* proposal and ideas for me | 14:35 |
| blackburn | sonney2k: I'll let you all know how can you help | 14:35 |
| blackburn | where the heck the mail is | 14:41 |
| shogun-buildbot_ | build #363 of rpm1 - libshogun is complete: Failure [failed test] Build details are at http://www.shogun-toolbox.org/buildbot/builders/rpm1%20-%20libshogun/builds/363 blamelist: Soeren Sonnenburg <sonne@debian.org> | 15:29 |
| -!- sidi_ [~sidi@14.139.122.114] has quit [Read error: Connection reset by peer] | 16:07 | |
| -!- sidi_ [~sidi@14.139.122.114] has joined #shogun | 16:13 | |
| -!- heiko [~heiko@5ac1f590.bb.sky.com] has joined #shogun | 16:28 | |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has quit [Ping timeout: 264 seconds] | 16:33 | |
| heiko | sonney2k: blackburn, wiking, just saw the update! :) | 16:36 |
| blackburn | heiko: we are still waiting the mail to come | 16:36 |
| heiko | blackburn: who writes it? S?ren? | 16:36 |
| blackburn | heiko: I did and sent it.. | 16:36 |
| blackburn | ohhh | 16:37 |
| blackburn | it arrived! | 16:37 |
| blackburn | :D | 16:37 |
| heiko | ah | 16:37 |
| heiko | ! | 16:37 |
| heiko | seeing it :) | 16:37 |
| blackburn | http://permalink.gmane.org/gmane.comp.ai.machine-learning.shogun/3325 | 16:37 |
| heiko | blackburn: yeah! :) well done! | 16:39 |
| -!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout] | 16:51 | |
| wiking | heiko: yo | 17:09 |
| wiking | heiko: check gitflow | 17:09 |
| wiking | heiko: and the mail i wrote about it | 17:09 |
| -!- hoijui [~hoijui@dslb-088-074-124-160.pools.arcor-ip.net] has quit [Ping timeout: 252 seconds] | 17:10 | |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has joined #shogun | 17:11 | |
| n4nd0 | blackburn: nice work with the mail! | 17:25 |
| blackburn | n4nd0: heh thanks | 17:26 |
| n4nd0 | Shogun 2.1 powered by vodka, beer and mate haha | 17:26 |
| blackburn | n4nd0: it took a few hours for mail to arrive | 17:26 |
| wiking | heheeh yeah blackburn thnx for the mail! :) | 17:26 |
| blackburn | wiking: I am still failing to use clang analyzer haha | 17:29 |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has quit [Quit: Reconnecting] | 17:29 | |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has joined #shogun | 17:30 | |
| blackburn | wiking: that's what I always get: scan-build: Removing directory '/tmp/scan-build-2013-03-17-1' because it contains no reports. | 17:30 |
| -!- heiko [~heiko@5ac1f590.bb.sky.com] has quit [Quit: Leaving.] | 18:58 | |
| -!- sidi [~sidi@14.139.122.114] has joined #shogun | 19:14 | |
| -!- sidi_ [~sidi@14.139.122.114] has quit [Read error: Connection reset by peer] | 19:14 | |
| -!- kishan [1883ef0b@gateway/web/freenode/ip.24.131.239.11] has joined #shogun | 19:35 | |
| -!- heiko1 [~heiko@5ac1f590.bb.sky.com] has joined #shogun | 19:44 | |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has quit [Ping timeout: 246 seconds] | 19:52 | |
| heiko1 | wiking, I read quickly and will do in more detail | 19:56 |
| heiko1 | wiking, my main point is to have a sophisticated dev-process of some form (eg the one you proposed) | 19:57 |
| heiko1 | and more importantly, hake tests madatory, and check whether tests pass before merging | 19:57 |
| heiko1 | so that it is not possible to commit code which breaks tests/examples | 19:57 |
| heiko1 | (at least on same basic level - not all configurations) | 19:57 |
| heiko1 | and another thing I would like to have is auto-rejects | 19:58 |
| blackburn | heiko1: autorejects of? | 19:58 |
| heiko1 | these should happen when tests fail /leak, warnings, missing documentation, incomplete examples, 0% test coverage | 19:58 |
| heiko1 | blackburn: of pull requests | 19:58 |
| heiko1 | blackburn: so that we can only merge if things work | 19:58 |
| blackburn | heiko1: travis already does that | 19:59 |
| heiko1 | there should be a hotfix branch to avoid this in emergencies, but in general it should not be possible to merge code which doesnt work | 19:59 |
| heiko1 | blackburn: even the core-devs should not be allowed to merge | 19:59 |
| heiko1 | blackburn: currently, we only get the info, but still can press merge | 19:59 |
| heiko1 | which is what we do | 19:59 |
| heiko1 | should not be possible | 19:59 |
| heiko1 | this way we force ourselves to do proper patches | 19:59 |
| blackburn | you must have been in army :D | 20:00 |
| heiko1 | blackburn: no, just talked to some friends who work in software engineering | 20:01 |
| heiko1 | :) | 20:01 |
| heiko1 | if you merge a patch in a company and it doesnt work, you basically get killed :) | 20:01 |
| blackburn | heiko1: oh really? :D | 20:01 |
| heiko1 | but also increases discipline (warnings/documentation) etc | 20:01 |
| heiko1 | one can also do other cool things with such a process | 20:02 |
| blackburn | heiko1: I pulled in a crazy number of breakers during doing my job actually | 20:02 |
| blackburn | that could be true for some companies but in general it is not such disciplined | 20:02 |
| heiko1 | blackburn: I know | 20:03 |
| heiko1 | ideally | 20:03 |
| heiko1 | defining the ideal here | 20:03 |
| heiko1 | blackburn: one could to some other cool things with that | 20:03 |
| blackburn | heiko1: such discipline requirements should have a reason | 20:04 |
| heiko1 | eg only accept examples if they come with a description and produce a screenshot | 20:04 |
| heiko1 | blackburn: well I can argue | 20:04 |
| heiko1 | so what happens before a release=? | 20:04 |
| heiko1 | big bug hunt | 20:04 |
| heiko1 | very annoying | 20:04 |
| heiko1 | how are warnings fixed? | 20:04 |
| heiko1 | by empty doxygen comments | 20:04 |
| heiko1 | example descriptions? never done | 20:04 |
| blackburn | heiko1: that's true but there should be an explanation | 20:05 |
| heiko1 | but we have to do these things *anyway* | 20:05 |
| heiko1 | so why not immediately | 20:05 |
| heiko1 | its actually less work if you do it when you write the code | 20:05 |
| heiko1 | same with tests | 20:05 |
| @sonney2k | heiko1, blackburn, wiking - so whats going on? | 20:06 |
| blackburn | sonney2k: heiko1 wants to walk around with a rifle :D | 20:06 |
| heiko1 | sonney2k: we are raving about the release :) | 20:06 |
| blackburn | and shoot ya leg! | 20:06 |
| heiko1 | blackburn: its not more work, we have to remove warnings anyway | 20:06 |
| heiko1 | and its so annoying to do this before release | 20:07 |
| blackburn | heiko1: it is a question of motivation (for me too) | 20:07 |
| heiko1 | indeed | 20:07 |
| blackburn | heiko1: that's a great motivation that is needed to have such restricted thing | 20:07 |
| heiko1 | its just a matter of getting used to it | 20:07 |
| heiko1 | for me, it costs way more motivation to do all these pain in the a** things | 20:07 |
| heiko1 | I just want to minimise the time spent on stupid things | 20:08 |
| blackburn | heiko1: I am still lost with what do we do | 20:08 |
| @sonney2k | heiko1, blackburn alright lets discuss this | 20:08 |
| blackburn | sonney2k: discussion time? | 20:08 |
| @sonney2k | heiko1, the biggest issue I see is that people don'tlike to write doxygen comments | 20:08 |
| heiko1 | sonney2k: true | 20:09 |
| @sonney2k | look at wiking - his CCSOSVM is still not well documented | 20:09 |
| @sonney2k | and we are admittedly no better | 20:09 |
| blackburn | look at me, my code is not documented at all :D | 20:09 |
| heiko1 | sonney2k: what is the point of writing code if you dont tell people how to use it? | 20:09 |
| @sonney2k | blackburn, documenting code is not what I meant | 20:09 |
| heiko1 | sonney2k: agreed | 20:09 |
| @sonney2k | I meant API doc | 20:09 |
| heiko1 | writing documentation is annoying | 20:09 |
| heiko1 | thats why we should have a process that ensures it is done anyway | 20:09 |
| heiko1 | sonney2k: but documentation is not my main concern in fact | 20:10 |
| @sonney2k | yes true but heiko1 we cannot do it with a black / white approach | 20:10 |
| blackburn | heiko1: the only way i see is metrics computation | 20:10 |
| @sonney2k | we have to find something we can all somehow live with | 20:10 |
| heiko1 | sonney2k: agreed, but I totally dont like this postponing forever | 20:10 |
| blackburn | heiko1: we should know weak points | 20:10 |
| heiko1 | sonney2k: my biggest point actually is the fact that we loose code | 20:10 |
| blackburn | we don't know them now | 20:10 |
| @sonney2k | heiko1, well one way would be to turn on warning -> error | 20:10 |
| heiko1 | streaming for example | 20:10 |
| heiko1 | json another one | 20:10 |
| blackburn | sonney2k: warnings are rather useless | 20:11 |
| @sonney2k | we all the time fix warnings before a release be it doxygen or in code | 20:11 |
| @sonney2k | blackburn, they helped me a lot | 20:11 |
| heiko1 | sonney2k, blackburn thing is we have to fix this stuff anyway | 20:11 |
| @sonney2k | heiko1, yes sure I agree ... but if we had integration tests turned on from 1.1 on we would have catched this | 20:11 |
| heiko1 | sonney2k: yes | 20:11 |
| heiko1 | so make it madatory | 20:12 |
| @sonney2k | so my take on this is to *gradually* improve the situation | 20:12 |
| heiko1 | then these things dont happen | 20:12 |
| @sonney2k | i.e. step 1) make integration test pass mandatory | 20:12 |
| heiko1 | sonney2k: yeah of course, as said, I describe the "ideal situation" | 20:12 |
| heiko1 | sonney2k: good idea. | 20:12 |
| blackburn | sonney2k: heiko1: I still want to define what do we develop | 20:12 |
| @sonney2k | 2) force people to *repair* the tests | 20:12 |
| @sonney2k | heiko1, ^2 is what we also sometimes suck with | 20:12 |
| heiko1 | how? | 20:12 |
| @sonney2k | we had tests failing for 1 week or so | 20:13 |
| heiko1 | sonney2k: this is another things which *has* to be done, so why not forbid to merge without passing tests? | 20:13 |
| @sonney2k | and heiko1 there is no way to force people to do it before submitting - otherwise you would have to compile *all* interfaces | 20:13 |
| @sonney2k | and need all shogun deps & compile time is like 1hr | 20:13 |
| heiko1 | sonney2k: good point, so lets just do it for libshogun | 20:13 |
| heiko1 | no interfaces | 20:13 |
| heiko1 | main thing is the unit-tests should pass | 20:13 |
| @sonney2k | heiko1, libshogun is already taken care of by travis | 20:14 |
| heiko1 | sonney2k: yeah, but Id like to change the ability to merge | 20:14 |
| @sonney2k | heiko1, but we usually don't struggle with libshogun stuff but the more involved code we have in all the *modular interfaces | 20:14 |
| @sonney2k | examples | 20:14 |
| heiko1 | sonney2k: this will change | 20:14 |
| heiko1 | unit tests are way more important for us | 20:14 |
| heiko1 | examples catch errors on the very last bit of the code | 20:15 |
| @sonney2k | heiko1, ok I don't mind having libshogun unit tests to pass as a precondition to git commit | 20:15 |
| heiko1 | this is not sufficient for fixing things | 20:15 |
| heiko1 | unit tests (which should be madatory for new things) will be able to tell you exactly what fails | 20:15 |
| heiko1 | and I agree, building everything takes too long, so yeah this sounds good | 20:15 |
| @sonney2k | heiko1, so we could add a git pre-commit hook like here http://mark-story.com/posts/view/using-git-commit-hooks-to-prevent-stupid-mistakes | 20:16 |
| heiko1 | let me have a look | 20:16 |
| @sonney2k | heiko1, so lets implement these 2 things for now - that should already help *a lot* | 20:16 |
| heiko1 | sonney2k: yes | 20:16 |
| heiko1 | sonney2k: I would also like to have a rejection if one has 0% unit-test coverage on code one commits | 20:17 |
| heiko1 | this forces at least to think about one test | 20:17 |
| heiko1 | we dont need a vast coverage | 20:17 |
| @sonney2k | heiko1, no idea how to do this | 20:17 |
| heiko1 | sonney2k: me neither, more talking about the idea | 20:17 |
| @sonney2k | computing code coverage I mean | 20:17 |
| heiko1 | sonney2k: its probably possible to compute this, I have seen it in the gnunet project | 20:17 |
| heiko1 | they use buildbot too and have this, I could ask them | 20:18 |
| heiko1 | sonney2k: what do you think of the general idea? | 20:18 |
| blackburn | heiko1: I am not sure that would work for us | 20:18 |
| heiko1 | blackburn: what exactly? | 20:19 |
| blackburn | heiko1: computing test coverage on commit.. | 20:19 |
| heiko1 | blackburn: you mean techinally? | 20:19 |
| blackburn | heiko1: yeah | 20:20 |
| @sonney2k | heiko1, yeah why not ask them | 20:20 |
| @sonney2k | anyway I think this is good enough for the start: the other big change would be the way we develop | 20:20 |
| heiko1 | sonney2k: yeah gradually change things | 20:21 |
| @sonney2k | and I don't really know how we can do this | 20:21 |
| @sonney2k | if we introduce a dev and feature branches etc | 20:21 |
| @sonney2k | what does the buildbot build | 20:21 |
| -!- kishan [1883ef0b@gateway/web/freenode/ip.24.131.239.11] has quit [Ping timeout: 245 seconds] | 20:22 | |
| heiko1 | sonney2k, do we really need the feature branches? | 20:23 |
| heiko1 | since small number of developers | 20:23 |
| @sonney2k | heiko1, sometimes I would think so - e.g. some big underlying change like we had with SGVector | 20:24 |
| blackburn | heiko1: would be better if you develop not through PRs but your own branch | 20:24 |
| blackburn | (I think so) | 20:24 |
| heiko1 | ok agreed | 20:24 |
| @sonney2k | heiko1, blackburn - what is the minimal thing we want? | 20:25 |
| @sonney2k | a dev branch and a stable master? | 20:25 |
| heiko1 | sonney2k: yes | 20:25 |
| heiko1 | they should have slightly different tests I guess | 20:26 |
| heiko1 | stable should be compiled with warnings as errors for example | 20:26 |
| blackburn | sonney2k: master is stable, and feature branches | 20:26 |
| heiko1 | blackburn: general dev branch would be good | 20:26 |
| blackburn | okay | 20:26 |
| heiko1 | master should be "production ready" | 20:26 |
| blackburn | master (stable) development and feature branches | 20:26 |
| heiko1 | so our current release is master | 20:26 |
| blackburn | I wish we could allow commits to specific branches | 20:27 |
| blackburn | like to feature branch but not master | 20:27 |
| @sonney2k | just FYI - if we create a release we do create a release branch | 20:27 |
| @sonney2k | and can put in bugfixes in there | 20:27 |
| heiko1 | sonney2k: good idea | 20:27 |
| @sonney2k | there is also one particular issue | 20:28 |
| @sonney2k | heiko1, that already is like this! | 20:28 |
| @sonney2k | we autogenerate the lib/versionstring.h file | 20:28 |
| heiko1 | sonney2k: I see | 20:28 |
| @sonney2k | that file is generated on configure/make | 20:28 |
| @sonney2k | and contains the current git version | 20:28 |
| heiko1 | sonney2k: ok understoof | 20:28 |
| @sonney2k | we use this git version when people send us bug reports | 20:28 |
| heiko1 | what would be really good if we had a stable branch that is always in the condition that we could release | 20:29 |
| @sonney2k | we cannot generate this file in a release shogun version | 20:29 |
| heiko1 | with just one click | 20:29 |
| @sonney2k | heiko1, it cannot be 1 click | 20:29 |
| @sonney2k | heiko1, the release script is already very simple | 20:29 |
| heiko1 | sonney2k: not to be taken literal | 20:29 |
| heiko1 | sonney2k: I mean more the code is in the condition to release | 20:29 |
| @sonney2k | heiko1, look at the toplevel makefile | 20:30 |
| heiko1 | we dont have to spend days in fixing things like removing warnings | 20:30 |
| @sonney2k | # * To make a release (and tag it) run | 20:30 |
| @sonney2k | # | 20:30 |
| @sonney2k | # make prepare-release | 20:30 |
| @sonney2k | # make git-tag-release | 20:30 |
| @sonney2k | # make release | 20:30 |
| @sonney2k | # make data-release | 20:30 |
| @sonney2k | # make update-webpage | 20:30 |
| heiko1 | sonney2k: ok cool didnt know that | 20:30 |
| blackburn | ha, mikio twitted about shogun | 20:30 |
| @sonney2k | but then you will need to a) send out announcement to mailinglist, g+, twitter, mloss.org, freshmeat, my blog | 20:30 |
| @sonney2k | blackburn, link? | 20:31 |
| blackburn | https://twitter.com/mikiobraun/status/313371488839405568 sonney2k | 20:31 |
| heiko1 | sonney2k: will write a tweet later today | 20:31 |
| heiko1 | sonney2k: ok these are non-automatic things | 20:31 |
| blackburn | heiko1: twitt is already here if you mean @ShogunToolbox | 20:31 |
| @sonney2k | heiko1, and the biggest concern is make prepare-release to actually go through | 20:31 |
| @sonney2k | heiko1, yeah n4nd0 did it :) | 20:32 |
| heiko1 | cool! | 20:32 |
| heiko1 | good | 20:32 |
| @sonney2k | heiko1, make prepare-release can take ~1 hour | 20:32 |
| @sonney2k | it compiles all interfaces / updates doc / runs all examples & tests | 20:33 |
| @sonney2k | the rest is fast but can take 30 mins too just to upload data etc | 20:33 |
| heiko1 | ok, so this is already there then | 20:33 |
| heiko1 | question, how to make sure that we dont have this huge pile of work before release? | 20:34 |
| @sonney2k | heiko1, more or less ... there were some bugs in the scripts I would like to fix | 20:34 |
| @sonney2k | heiko1, release more often! | 20:34 |
| @sonney2k | heiko1, we have 6-12 months between releases | 20:34 |
| @sonney2k | no wonder that lots of stuff breaks | 20:34 |
| heiko1 | how do releases prevent things from breaking? | 20:34 |
| @sonney2k | if we release every 1-2 months not so many features enter | 20:34 |
| @sonney2k | -> less testing needed | 20:34 |
| @sonney2k | -> faster release | 20:35 |
| heiko1 | sonney2k: we dont do testing currently | 20:35 |
| @sonney2k | heiko1, impossible even integration / unit tests won't help | 20:35 |
| @sonney2k | heiko1, I do | 20:35 |
| heiko1 | sonney2k: I mean we have no systematic way of doing it | 20:35 |
| @sonney2k | heiko1, I run some example code and check if things are still ok | 20:35 |
| @sonney2k | heiko1, is there any? | 20:35 |
| blackburn | heiko1: you are a pure german ;) | 20:36 |
| heiko1 | in my eyes this problem can only be solved if writing unit/integration is part of the development process | 20:36 |
| heiko1 | we currently have no mechanism to ensure that things work | 20:36 |
| heiko1 | we only detect if things crash | 20:36 |
| heiko1 | so catching problems earlier I think would help a lot | 20:37 |
| heiko1 | if one realised that an example crashes its usually too late | 20:37 |
| heiko1 | take the GP stuff | 20:37 |
| heiko1 | was implemented - worked fine | 20:37 |
| @sonney2k | heiko1, let me tell you that 100% unit / integration test coverage won't help you | 20:37 |
| @sonney2k | (from experience) | 20:38 |
| heiko1 | then was extended - which broke the first working part | 20:38 |
| heiko1 | but no detection | 20:38 |
| heiko1 | later on detected in example by pure chance | 20:38 |
| heiko1 | sonney2k: I know | 20:38 |
| @sonney2k | you change sth and voila your cool unit/integration test exactly did not test for that borderline thing | 20:38 |
| heiko1 | sonney2k: but *having* tests helps | 20:38 |
| @sonney2k | happens to me all the time | 20:38 |
| @sonney2k | heiko1, yes sure | 20:38 |
| heiko1 | sonney2k: you are right, I am not saying this solves everything | 20:38 |
| heiko1 | but my experience is that almost all bugs I fix can be catched by unit testing | 20:39 |
| heiko1 | the multiclass SVm bug yesterday another example | 20:39 |
| heiko1 | if there was a test that actually *ran* the code once, we would not have had this bug | 20:39 |
| blackburn | I tell that each minute but - do our users care so much about bugs? that's the question | 20:39 |
| blackburn | if we are striving for quality - what for? | 20:39 |
| heiko1 | blackburn: if you install shogun, and try an example, and all you get is sefault, you instantly delete | 20:40 |
| @sonney2k | heiko1, but we have to face reality too - if we don't want any future contributions we require 100% unit tests & 100% dyxgen api doc | 20:40 |
| @sonney2k | we need some tradeoff | 20:40 |
| heiko1 | not 100% | 20:40 |
| @sonney2k | fun <-> stability | 20:40 |
| heiko1 | but not zero % | 20:40 |
| heiko1 | thats my point | 20:40 |
| @sonney2k | heiko1, yes sure! | 20:40 |
| heiko1 | at least think of *some* things to test | 20:40 |
| heiko1 | that was my point, forbid 0% coverage | 20:40 |
| -!- sidi [~sidi@14.139.122.114] has quit [Read error: Connection reset by peer] | 20:40 | |
| heiko1 | not aim for 100 | 20:40 |
| heiko1 | we dont need that | 20:40 |
| heiko1 | but at least *think* of it | 20:40 |
| heiko1 | which we currently dont do | 20:40 |
| heiko1 | especially important for the gsoc project to be suistainable | 20:41 |
| blackburn | heiko1: then some verbal pushes is what we can do | 20:41 |
| @sonney2k | blackburn, heiko1 - the most important thing is to nicely respond to bug reports on the mailing list - and I mean not like - ahh don't use that interface or I look at this when I find some time in a few weeks | 20:41 |
| @sonney2k | just fix the bug and notify the user that it is fixed | 20:41 |
| @sonney2k | heiko1, yeah but it was our fault not requiring unit tests back then | 20:42 |
| @sonney2k | heiko1, but we were in no shape to have that a few years back | 20:42 |
| @sonney2k | heiko1, situation of shogun gradually improved over years | 20:42 |
| blackburn | sonney2k: yeah we weren't that wise we are now | 20:42 |
| blackburn | I feel ok about that | 20:42 |
| heiko1 | my gf just started a fire in the kitchen | 20:42 |
| @sonney2k | heiko1, look - we had no unit tests not build bots no integration test no doc no nothing back then | 20:42 |
| heiko1 | sonney2k: yes, we are on a good way | 20:43 |
| blackburn | heiko1: yikes | 20:43 |
| @sonney2k | heiko1, hand her some fire extinguisher | 20:43 |
| heiko1 | *done* | 20:43 |
| @sonney2k | then continue chatting | 20:43 |
| heiko1 | actually the l?schdecke | 20:43 |
| @sonney2k | hehe | 20:43 |
| heiko1 | haha :) | 20:43 |
| blackburn | oh these german words make me crazy | 20:43 |
| @sonney2k | we just have pretty well buildbot infrastructure since last gsoc | 20:44 |
| @sonney2k | this gsoc we will have integration / unit tests | 20:44 |
| heiko1 | sonney2k: just want to push this test thing, I think we have to make ourselves change our habits | 20:44 |
| @sonney2k | and we will require students to write both or fail them | 20:44 |
| heiko1 | sonney2k: yes thats really good | 20:44 |
| heiko1 | exactly thats my goal :) | 20:44 |
| @sonney2k | but we need to tell them upfront! | 20:44 |
| heiko1 | sonney2k: yes, that was the point of the guidelines | 20:45 |
| @sonney2k | heiko1, we have README.developer in src | 20:45 |
| @sonney2k | lets add the part about unit/integration tests | 20:45 |
| heiko1 | good, lets merge it | 20:45 |
| @sonney2k | not all of it | 20:45 |
| heiko1 | maybe after some reviewing | 20:45 |
| @sonney2k | yesh | 20:45 |
| @sonney2k | yeah | 20:45 |
| heiko1 | sonney2k: what do you think of making examples fail if they do not return things or do not create a screenshot? | 20:46 |
| blackburn | sonney2k: heiko1: a good thing would be - all PRs should be 'ok' from all committers | 20:46 |
| @sonney2k | we are not there yet | 20:46 |
| heiko1 | blackburn: that would be good, but too much work | 20:46 |
| blackburn | heiko1: why? | 20:46 |
| @sonney2k | blackburn, everyone wouldhave to do code reviews -> impossible | 20:47 |
| heiko1 | rahter make the system do as much as possible | 20:47 |
| blackburn | sonney2k: no I mean we three | 20:47 |
| @sonney2k | that doesn't scale | 20:47 |
| blackburn | (four) | 20:47 |
| @sonney2k | no | 20:47 |
| @sonney2k | one of us | 20:47 |
| blackburn | I don't like that - there should be a few reviewers | 20:47 |
| @sonney2k | and if sth breaks we punish the merging guy :D | 20:47 |
| heiko1 | student patches should not be merged if anything is missing :) | 20:48 |
| heiko1 | guys, as you probably already thought, diner is ready soon here, | 20:48 |
| heiko1 | its roast :) | 20:48 |
| heiko1 | I gotta buy some things and then eat. | 20:48 |
| heiko1 | so sorry, gotta go | 20:48 |
| blackburn | heh alright | 20:48 |
| @sonney2k | heiko1, blackburn btw are you ok with the slogan on the website? | 20:48 |
| blackburn | sonney2k: hah sure | 20:48 |
| heiko1 | sonney2k: sure :) | 20:49 |
| @sonney2k | hehe | 20:49 |
| blackburn | sonney2k: I like crazy things - being serious is a fault | 20:49 |
| heiko1 | sonney2k: you should add coffee and almonds for my part :) | 20:49 |
| heiko1 | bye! | 20:49 |
| -!- heiko1 [~heiko@5ac1f590.bb.sky.com] has quit [Quit: Leaving.] | 20:49 | |
| @sonney2k | heiko1, chocolate here | 20:49 |
| @sonney2k | bye | 20:49 |
| @sonney2k | blackburn, so I guess we agree on the unit test stuff but how do we do it with the git branches etc? | 20:50 |
| blackburn | sonney2k: good q | 20:50 |
| @sonney2k | blackburn, it is really pressing for me to fix some erros in the release scripts while I still remember what they were | 20:50 |
| @sonney2k | I am totally clueless what the buildbot should then check | 20:51 |
| blackburn | sonney2k: both.. | 20:51 |
| blackburn | :D | 20:51 |
| blackburn | development and stable | 20:51 |
| blackburn | sonney2k: need advice | 20:53 |
| @sonney2k | blackburn, and feature branches? | 20:54 |
| blackburn | https://dl.dropbox.com/u/10139213/SS/lisitsyn12a.pdf sonney2k plots, page 3 | 20:54 |
| blackburn | sonney2k: no, feature branches should not be builded I think | 20:54 |
| -!- sumit [73f91219@gateway/web/freenode/ip.115.249.18.25] has joined #shogun | 20:55 | |
| @sonney2k | blackburn, IIRC there is subfix or sth where you can have >1 fig | 20:55 |
| blackburn | sonney2k: I don't get it - what is it for? | 20:56 |
| @sonney2k | to have the figures name a) b) c) | 20:56 |
| blackburn | sonney2k: ahh | 20:57 |
| blackburn | sonney2k: but figures? are they ok? | 20:57 |
| @sonney2k | blackburn, btw I like evan shelhamers suggestion | 20:57 |
| @sonney2k | blackburn, yes | 20:57 |
| @sonney2k | to create a release branch to stabilize things | 20:57 |
| blackburn | sonney2k: I don't know what to do with faces though - they are not visible, too small.. | 20:58 |
| @sonney2k | a long time before we release | 20:58 |
| blackburn | sonney2k: yes that's a good way | 20:58 |
| @sonney2k | so we could even do sth like this: | 20:58 |
| blackburn | sonney2k: kernel do the same? | 20:58 |
| @sonney2k | release every month | 20:58 |
| @sonney2k | with a delay of one month | 20:58 |
| @sonney2k | we just create a shogun_2.2 branch in one month | 20:58 |
| @sonney2k | then fix things for 1 month and release | 20:59 |
| @sonney2k | and at the same time develop in master | 20:59 |
| @sonney2k | dev branch | 20:59 |
| blackburn | sonney2k: looks good but don't know how well in practice | 20:59 |
| @sonney2k | blackburn, what I dont' understand though is how we do it all with github. I mean w/ github we have these pull requests | 21:00 |
| @sonney2k | which are branches itself right? | 21:00 |
| @sonney2k | so these are feature branches? | 21:00 |
| @sonney2k | we intend to merge to the dev branch - correct? | 21:01 |
| blackburn | sonney2k: it is ok to PR to some branch | 21:01 |
| blackburn | sonney2k: why not to feature branch? | 21:01 |
| @sonney2k | blackburn, don't you have to create a branch to even do a PR? | 21:02 |
| @sonney2k | so isn't that then the same like a feature branch? | 21:02 |
| blackburn | sonney2k: well you can do a PR from a master | 21:02 |
| blackburn | sonney2k: selective rights would be awesome | 21:03 |
| @sonney2k | blackburn, you mean from your fork's master right? | 21:03 |
| blackburn | sonney2k: yes | 21:03 |
| @sonney2k | blackburn, yeah well ok but that kind of is a feature branch ... | 21:04 |
| @sonney2k | but only a local one | 21:04 |
| blackburn | sonney2k: yes | 21:04 |
| @sonney2k | we probably don't need shared feature branches (at least not often) | 21:04 |
| blackburn | sonney2k: it is not really relevant for us actually | 21:04 |
| @sonney2k | so all that we want to change is have a dev branch & a master branch | 21:05 |
| blackburn | sonney2k: yeah I think dev+master would be enough for now | 21:05 |
| @sonney2k | the only problem I have is that we cannot git tag the released version in the master branch | 21:05 |
| @sonney2k | because we include lib/versionstring.h in the release | 21:05 |
| @sonney2k | which we *never* put in the git repo in master/dev | 21:06 |
| @sonney2k | blackburn, btw our shogun2.1 announcement has 14 +1's on g+ & 3 reshares | 21:07 |
| wiking | yoyo | 21:07 |
| blackburn | sonney2k: quite cool | 21:07 |
| @sonney2k | blackburn, wiking so what do we do? we cannot git tag in dev/master but have to do it in a release branch | 21:08 |
| @sonney2k | can we live with that? | 21:08 |
| blackburn | sonney2k: I don't know | 21:09 |
| @sonney2k | blackburn, anyway no matter what - let me create a dev branch and then I can commit my fixes there | 21:13 |
| blackburn | sonney2k: sure | 21:14 |
| @sonney2k | blackburn, and you do the gsoc stuff otherwise we won't make it | 21:14 |
| blackburn | sonney2k: yeah I'll spend some time tonight on that | 21:14 |
| blackburn | sonney2k: so I should not expect real help from mentors, right? | 21:17 |
| blackburn | sonney2k: I asked cheng to write some descriptions but no answer at all :D | 21:18 |
| @sonney2k | blackburn, no you should get some push them as much as you can but prepare at least 1 example to give them something they can base their stuff on! | 21:18 |
| blackburn | sonney2k: I gave them 2012 ideas | 21:18 |
| @sonney2k | blackburn, I see you created a dev branch on github | 21:18 |
| blackburn | sonney2k: I? | 21:18 |
| @sonney2k | blackburn, how do I get that pulled? | 21:18 |
| blackburn | ahh | 21:18 |
| @sonney2k | I don't see it locally not with git branch -a (as remote branch) | 21:19 |
| blackburn | sonney2k: I don't get the question | 21:19 |
| blackburn | sonney2k: did you create your branch? | 21:19 |
| @sonney2k | blackburn, no | 21:19 |
| blackburn | do that | 21:19 |
| @sonney2k | what? | 21:20 |
| @sonney2k | at github there is a dev branch | 21:20 |
| blackburn | sonney2k: you wanted a branch? | 21:20 |
| @sonney2k | for shogun | 21:20 |
| blackburn | sonney2k: where? :D | 21:20 |
| blackburn | https://github.com/shogun-toolbox/shogun/branches | 21:20 |
| @sonney2k | dev | 21:20 |
| @sonney2k | Last updated 9 hours ago by lisitsyn. | 21:20 |
| blackburn | sonney2k: ehmmm - where do you see it? | 21:21 |
| blackburn | interesting | 21:21 |
| @sonney2k | blackburn, I just type dev into branches | 21:22 |
| blackburn | sonney2k: the thing is that I didn't create any branch | 21:22 |
| blackburn | I just pulled and what I saw is | 21:22 |
| blackburn | From github.com:shogun-toolbox/shogun | 21:22 |
| blackburn | 9702994..e6138dd master -> origin/master | 21:22 |
| blackburn | * [new branch] dev -> origin/dev | 21:22 |
| @sonney2k | huh? | 21:23 |
| @sonney2k | it is there now!? | 21:23 |
| @sonney2k | wtf | 21:23 |
| blackburn | sonney2k: wiking may be? | 21:24 |
| @sonney2k | maybe | 21:24 |
| wiking | just a sec | 21:24 |
| wiking | i just came back | 21:24 |
| @sonney2k | so how do I work on this? | 21:24 |
| blackburn | wiking: is that you who created 'dev'? | 21:24 |
| wiking | es | 21:24 |
| @sonney2k | it is a remote branch so I can only push to this right? | 21:25 |
| wiking | yes | 21:25 |
| wiking | i even told here | 21:25 |
| wiking | :)))) | 21:25 |
| blackburn | wiking: yeah | 21:25 |
| wiking | check logs | 21:25 |
| wiking | about 5 hours ago i told | 21:25 |
| blackburn | wiking: I remember something :) | 21:25 |
| wiking | that there's dev branch now in git | 21:25 |
| @sonney2k | wiking, you did this before we released so we need to rebase it to master | 21:25 |
| wiking | yes | 21:25 |
| @sonney2k | so I create a dev branch locally based on that? | 21:25 |
| wiking | we need a simple repbase | 21:25 |
| @sonney2k | and then git rebase | 21:25 |
| @sonney2k | and push to the dev branch? | 21:25 |
| wiking | naaah just a sec | 21:25 |
| wiking | i'll fish it | 21:25 |
| wiking | fix it | 21:26 |
| wiking | :))) | 21:26 |
| @sonney2k | no no | 21:26 |
| @sonney2k | I want to do it | 21:26 |
| @sonney2k | and learn how to :) | 21:26 |
| wiking | hehehehe | 21:26 |
| wiking | with git flow? | 21:26 |
| wiking | btw do we agree to use that? | 21:26 |
| -!- sumit [73f91219@gateway/web/freenode/ip.115.249.18.25] has quit [Quit: Page closed] | 21:26 | |
| @sonney2k | wiking, no | 21:26 |
| wiking | so no gitflow? | 21:26 |
| wiking | no direct writing to git shogun repo? | 21:26 |
| wiking | and PRing every stuff? | 21:27 |
| @sonney2k | wiking, no idea but likely not git flow | 21:28 |
| wiking | i'm totally 4 gitflow :))) | 21:30 |
| wiking | helps a lot in branch maintaining | 21:30 |
| wiking | especially the whole release - dev branch maintaining | 21:31 |
| @sonney2k | wiking, we have the issue with our lib/versionstring.h not being part of git master/dev | 21:33 |
| wiking | yep i get it | 21:34 |
| @sonney2k | wiking, no idea what to do about it | 21:35 |
| wiking | just a sec | 21:37 |
| wiking | (eatig) | 21:37 |
| wiking | (eating) | 21:37 |
| @sonney2k | we have to think about it a bit more | 21:38 |
| wiking | sonney2k: what's against having lib/versionstring.h in the repo? | 21:49 |
| wiking | i mean we can even have like a template version of that in the repo, and have a makefile script that automagically updates it? :P | 21:50 |
| wiking | and that's just part of the actual release....? | 21:50 |
| wiking | here's an example: https://github.com/arq5x/bedtools/pull/16/files | 21:50 |
| -!- hoijui [~hoijui@dslb-088-074-124-160.pools.arcor-ip.net] has joined #shogun | 22:00 | |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has joined #shogun | 22:24 | |
| -!- zxtx [~zv@75-59-238-10.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 246 seconds] | 22:48 | |
| -!- n4nd0 [~nando@s83-179-44-135.cust.tele2.se] has quit [Quit: leaving] | 22:51 | |
| wiking | sonney2k: so actually regardless of gitflow | 23:04 |
| wiking | sonney2k: can we agree that if one has a write access on shogun-toolbox/shogun.git repot then he can push commits directly into dev branch w/o doint the PR->merge cycle? | 23:05 |
| -!- hoijui [~hoijui@dslb-088-074-124-160.pools.arcor-ip.net] has quit [Ping timeout: 252 seconds] | 23:43 | |
| --- Log closed Mon Mar 18 00:00:14 2013 | ||
Generated by irclog2html.py 2.10.0 by Marius Gedminas - find it at mg.pov.lt!