[DiscordArchive] <@160857905879449600> I can do a dirty hack to make the parser work again, but it is not gonna be do
[DiscordArchive] <@160857905879449600> I can do a dirty hack to make the parser work again, but it is not gonna be do
Archived author: Marlamin • Posted: 2018-11-04T20:17:03.520000+00:00
Original source
so a range of 3.1.3-3.3.5 would not contain 3.2.1
Archived author: Marlamin • Posted: 2018-11-04T20:17:08.852000+00:00
Original source
i think that was the thinking back then
Archived author: Marlamin • Posted: 2018-11-04T20:17:23.912000+00:00
Original source
spoke about this at length with barney a few months ago
Archived author: Marlamin • Posted: 2018-11-04T20:17:46.031000+00:00
Original source
major always increases on an expansion basis
Archived author: Marlamin • Posted: 2018-11-04T20:17:59.256000+00:00
Original source
and build always increases too
Archived author: Marlamin • Posted: 2018-11-04T20:19:27.691000+00:00
Original source
we weren't able to come up with usecases where it would fail
Archived author: Marlamin • Posted: 2018-11-04T20:19:33.078000+00:00
Original source
but doesn't mean they don't exist
Archived author: Marlamin • Posted: 2018-11-04T20:20:02.181000+00:00
Original source
1.13 is a nice challenge but will work as long as we keep it separated
Archived author: schlumpf • Posted: 2018-11-04T20:25:20.977000+00:00
Original source
tbh, unless we do a manual total ordering of all builds, ranges across even minor versions automatically are dangerous, unless we literally do `VERSION 3`.
Archived author: schlumpf • Posted: 2018-11-04T20:25:38.418000+00:00
Original source
You know that I spent a lot of time trying to get this shit right