02-02-2018, 10:38 PM
02-02-2018, 10:46 PM
Does it really matter that much? It was probably due to a merge.
02-02-2018, 10:47 PM
(02-02-2018, 10:38 PM)teots Wrote: [ -> ]The last update was 1.5 dev 2267, why is this latest update jump twice to 1.5 dev 2269 ?
Because someone's been a naughty boy so Santa had to skipĀ 2268 delivery.
02-03-2018, 12:57 AM
same as rpcs3 they mostly jumps that build numbers
https://rpcs3.net/compatibility?b
https://rpcs3.net/compatibility?b
02-03-2018, 01:05 AM
Because it added both the new build by bositman(who merged the latest commit) and the original commit(which is a no build) as created by altiereslima.
02-03-2018, 03:57 AM
the rpcs3 builds page is very "oriented" they put their +s and -s of their builds as well as pull requests but no comment logs.
hope they do the same in pcsx2 buildbots..
hope they do the same in pcsx2 buildbots..
02-03-2018, 03:26 PM
(02-03-2018, 03:57 AM)smartstrike Wrote: [ -> ]the rpcs3 builds page is very "oriented" they put their +s and -s of their builds as well as pull requests but no comment logs.
hope they do the same in pcsx2 buildbots..
I prefer the comment logs on buildbot. Saves me from having to open github to see what was actually changed.