+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Discussion (https://forum.cuberite.org/forum-5.html)
+--- Thread: Giving MCServer a version number (/thread-1847.html)
RE: Giving MCServer a version number - LogicParrot - 05-09-2015
(05-09-2015, 02:55 AM)tigerw Wrote: Then why not have master as testing?
I see your point, there's no point in people testing the "testing" branch.
Perhaps the "testing" branch should be an "internal one", meaning people are not supposed to test it directly, and no official binaries exist for it. The adventurers would use the Master branch, the rest will use Stable, and when a bug is detected in Master which is related to what's in testing, stuff are pushed to testing.
In other words:
Code:
Master ---(bugfixes/rotations)---> Testing ---(rotations)---> stable ---> Binaries: Stable releases.
|
V
Binaries: "Nightlies" / call them whatever you wantEdit: Now that I think of it again, I don't see how it's better than having people test "testing", you can ignore my previous post.
RE: Giving MCServer a version number - worktycho - 05-09-2015
The reason to not have master as testing is that you don't want a big feature pull request landing on the testing branch just before a promotion. By having a testing branch, features can land on master at any time, but are only promoted to testing periodically, so that all feature code in testing has been tested for a week or two before promotion.
RE: Giving MCServer a version number - worktycho - 05-09-2015
@tiger Why did you delete the testing branch? I've given my reasoning behind it.
RE: Giving MCServer a version number - tigerw - 05-09-2015
I didn't delete anything :P
The delayed-deploy makes sense, thanks.
RE: Giving MCServer a version number - worktycho - 05-09-2015
I have evidence
.But it was probably a mistake.
RE: Giving MCServer a version number - tonibm19 - 05-09-2015
I agree with a testing branch too, and I have an idea for it, a testing server. When the testing branch is updated with new features or bugfixes, it would be fine if we had a server to test together.
It could have core dumps enabled to detect crashes or similar things.
Unfortunately, I lost my free vps
.
RE: Giving MCServer a version number - sphinxc0re - 05-09-2015
We could use mine. It's a very cheap VPS hosted in Germany.
RE: Giving MCServer a version number - worktycho - 05-09-2015
@bearbin doing builds so you just need to track that. It shouldn't be too difficult to write an auto update script.
RE: Giving MCServer a version number - sphinxc0re - 05-09-2015
I already wrote my own update script. it works very well. So I just have to wait for the builds to start
RE: Giving MCServer a version number - worktycho - 05-09-2015
The first testing build is complete http://builds.cuberite.org/job/MCServer%20Linux%20x64%20Testing/lastSuccessfulBuild/artifact/