| 03:46.51 | *** part/#asterisk-dev sh_smith (~sh_smith@cpe-172-88-21-24.socal.res.rr.com) |
| 08:26.46 | *** join/#asterisk-dev AsteriskRoss (~AsteriskR@37.157.48.2) |
| 09:47.30 | *** join/#asterisk-dev AsteriskRoss (~AsteriskR@37.157.48.2) |
| 10:05.02 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.110) |
| 10:05.02 | *** mode/#asterisk-dev [+o jkroon] by ChanServ |
| 10:55.11 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.110) |
| 10:55.11 | *** mode/#asterisk-dev [+o jkroon] by ChanServ |
| 11:04.55 | jkroon | https://gerrit.asterisk.org/c/asterisk/+/15628 - any chance we can still sneak this in for the upcoming release? doesn't fix a bug with the release candidates, however, it would be of benefit for packaging purposes. |
| 11:05.18 | file | release candidates were already created |
| 11:05.32 | jkroon | i'm aware, so i'm taking that as a no? |
| 11:05.51 | file | correct, it would be a no |
| 11:06.01 | jkroon | (don't mind, just need to action my planning accordingly) |
| 11:07.14 | jkroon | so rc => release, only changes allowed are those fixing a specific targeted issue on the rc. got it. |
| 11:07.24 | file | yes. |
| 11:07.34 | file | any changes then trigger another rc |
| 11:08.03 | jkroon | that's a good process. |
| 11:08.27 | jkroon | i'll apply locally then for the next revision. |
| 11:15.44 | jkroon | thanks file |
| 11:18.00 | jkroon | and the build failure there captures exactly why I'm looking for the non-zero exit code :$ |
| 18:03.52 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.107) |
| 18:03.52 | *** mode/#asterisk-dev [+o jkroon] by ChanServ |
| 18:07.37 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.107) |
| 18:07.37 | *** mode/#asterisk-dev [+o jkroon] by ChanServ |
| 18:08.27 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.107) |
| 18:08.27 | *** mode/#asterisk-dev [+o jkroon] by ChanServ |
| 18:13.31 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.107) |
| 18:13.31 | *** mode/#asterisk-dev [+o jkroon] by ChanServ |
| 19:47.38 | *** join/#asterisk-dev infobot (ibot@96-86-209-99-static.hfc.comcastbusiness.net) |
| 19:47.38 | *** topic/#asterisk-dev is Take the March 2019 Asterisk User Survey! https://goo.gl/forms/xL1VUHRsf95saly13 -- Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Check out our blog! blogs.asterisk.org -=- Follow on Twitter at @AsteriskDev |