Acorn ArcadeGaming news and viewsUpdated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125506
This is true, but a bad strategy if this phase takes a long time: you queue up merge requests, making merge conflicts much more likely. And you end up with a release that is not easily fixable. And you make the next publishable development version much more unstable because you introduce so many changes at once. Bad news for your testers.Updated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125505
I think it's pretty simple for ROOL to control what ends up in the build. They are in control of what gets merged, so they don't even need to faff about with branches: they can simply only merge things which are important and/or safe enough to include in the release.Updated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125504
Interesting. I somehow assumed that there is a more usual release candidate/rampdown phase strategy employed, like creating a branch where only showstopper fixes are applied and normal development continues on the main branch.Updated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125503
You have been able to use Git on RISC OS with RISC OS Pyromaniac for quite some time. Although the client was first envisioned about 3 years ago - https://asciinema.org/a/305986 shows the very first prototypes - the current implementation is reasonably fully featured and can be used as a regular client.Updated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125502
I'm not sure we're not all missing the fact that there is a candidate for a 25 year old machine, (and a nearly 20 year old machine) and nothing for probably the most ubiquitous ARM board in the world, that is still in production, and will be for a few more years.Updated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125501
At the time of issue the contents of OS5.31 RC4 and the beta OS5.29 were identical except for the UtilityModule version numbers.Updated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125500
OK, now go to the downloads page. Follow the link to download RC4. What is a "Stable release candidate" - something else than a "Release Candidate"? And note that it says it is "Preview RC4 of the forthcoming RISC OS 5.3x stable release" - so not for the RISC OS 5.30 version? Because it says 5.31 in the next column? And what is a "Preview RC4"? Will it be followed by the "Real RC4" soon?Updated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125499
Well, I don't think that's fair at all. There was this...Updated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125498
Yeah, it is all a bit cloak-and-dagger, isn't it? It's like RISC OS Developmnents and/or R-Comp are showing ROOL the way.Updated RISC OS Git client sent to beta testers
http://www.acornarcade.com/forums/viewthread.php?threadid=13132&page=1#125497
Did I miss the announcement that the Git client reached beta state?