Tuesday, 2018-10-09

*** eernst has joined #kata-dev02:54
*** marcov has quit IRC03:05
*** eernst has quit IRC03:52
*** sjas_ has joined #kata-dev04:51
*** sjas has quit IRC04:54
*** coolsvap has joined #kata-dev06:38
*** marcov has joined #kata-dev06:59
*** marcov__ has joined #kata-dev07:01
*** marcov has quit IRC07:04
*** marcov__ is now known as marcov07:13
*** marcov__ has joined #kata-dev07:33
*** marcov has quit IRC07:37
*** marcov has joined #kata-dev07:39
*** marcov__ has quit IRC07:42
*** jodh has joined #kata-dev07:44
*** jodh has quit IRC07:47
*** jodh has joined #kata-dev07:48
*** gwhaley has joined #kata-dev07:58
*** davidgiluk has joined #kata-dev08:02
*** marcov has quit IRC08:02
*** marcov has joined #kata-dev08:02
*** gwhaley has quit IRC11:01
*** fuentess has joined #kata-dev11:48
*** devimc has joined #kata-dev11:58
*** gwhaley has joined #kata-dev12:17
*** lpetrut has joined #kata-dev12:58
kata-irc-bot<graham.whaley> hey @bergwolf @jose.carlos.venegas.m @eric.ernst I noticed something 'odd' about github release pages that I'd not realised before. It looks like the releases page is sorted by reverse date, only, so the 'latest release' appears at the top. What that means is for any project with stable branches (like kata), it is not uncommon for the last stable branch update to appear at the top, even if that is not the 'latest release'. For13:20
kata-irc-botinstance, we have 1.2.2 at the top right now, and not 1.3.0. It threw me for a minute :( https://github.com/kata-containers/runtime/releases13:20
kata-irc-bot<bergwolf> ouch, any idea how to reverse that?13:22
kata-irc-bot<graham.whaley> I think the only way we can manage it is to ensure we make the 'latest best release' the last one we push:-(13:22
kata-irc-bot<graham.whaley> I don't see any other options on github.13:22
kata-irc-bot<bergwolf> Then maybe we should schedule a new release ASAP ;)13:23
kata-irc-bot<graham.whaley> heh :slightly_smiling_face:13:24
kata-irc-bot<bergwolf> Maybe just v1.3.1 so that we can make the master release on the top13:24
kata-irc-bot<graham.whaley> maybe. Let's see what Eric and Carlos think - maybe they have some ideas. We might need to codify something into the release scripts as well, or some guidance at least13:25
kata-irc-bot<bergwolf> yup, defly13:25
kata-irc-bot<jose.carlos.venegas.m> @graham.whaley @bergwolf I notice that too, there is not a way to mark a release as latest in github so the latest will be the last tag we push yes another release may work but would be first 1.2.x. and then 1.3.1 if not we will have the same issue13:35
kata-irc-bot<jose.carlos.venegas.m> that or ignore the "latest" tag from github as they dont have the notion of multiple branch release13:36
kata-irc-bot<jose.carlos.venegas.m> I do  `hub release | sort -n`13:36
kata-irc-bot<jose.carlos.venegas.m> if you are looking that for some automation13:37
*** mugsie has joined #kata-dev14:12
*** annabelleB has joined #kata-dev14:16
*** lpetrut has quit IRC14:56
*** devimc has quit IRC15:15
*** devimc has joined #kata-dev15:19
*** jodh has quit IRC15:30
*** coolsvap has quit IRC16:23
*** gwhaley has quit IRC16:44
*** zerocoolback has quit IRC17:09
*** marcov has quit IRC17:27
*** gwhaley has joined #kata-dev17:41
*** jugs has quit IRC18:01
*** jugs has joined #kata-dev18:01
*** eernst has joined #kata-dev18:38
*** gwhaley has quit IRC19:15
*** davidgiluk has quit IRC19:18
*** sjas_ has quit IRC19:45
*** eernst has quit IRC20:04
*** devimc has quit IRC22:09
*** fuentess has quit IRC22:09
*** annabelleB has quit IRC23:07
*** annabelleB has joined #kata-dev23:35
*** annabelleB has quit IRC23:49
*** annabelleB has joined #kata-dev23:56

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!