![]() because he trusted the distributor which was not mozilla. user got 116.0.3 RC1 which contains bugs and not the bugfree 116.0.3 RC2. users may think oh great, v117 (117.0-1) is ready, but indeed they got a buggy RC, maybe start ranting against mozilla.Īnd the example with 116.0.2 -> 116.0.3 in #5078 is one of those. but that has the underlying problem which i wrote above - no one can be sure that the compiling dude is releasing this early build as the final build. The github link shows another one - there exists a "-1" build, probably based on the RC1, i dont know if it was distributed. and even when not you can extract both and compare hashes of files. for windows - you can compare the hashes for EXE for RC2 and release, if they are same, so the result is that RC2 got final. if there is no other RC then it may be the final. the code to get compiled lies within that folder. ![]() ![]() ![]() RC2 may not buggy, but its not the released stage. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |