On 2015-04-14 08:52, kallisti5 wrote:
On 2015-04-14 08:38, Adrien Destugues wrote:
As for alpha / beta "release" repositories... Lets just set them to
current
by default and be done with it.
This can't work. People will keep uploading packages to haikuports
that have a $haikuVersion higher than "r1alpha5" (it includes the
hrev). So people running the alpha would not be able to install such
packages.
You could then tell them to use the haiku repo with the current
nightly packages, but then it is exactly the same as grabbing any
random nightly and installing that.
What is the point of a release then? In that case, let's just remove
alpha4 from the main page and put a "download a nightly" link there
instead, it will be exactly the same.
To make a release, we need a release-specific repo where we can upload
maintenance fixes to the OS, and new packages tested on the particular
release. I'm fine with this being done manually, but it has to be
done, and it seems to me that doing it manually is more work than
finishing the repo build system. Also, it would mean we can test the
repo build using the alpha/beta, so it is tested and refined and ready
for R1.
