trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] R14 RC1 ready?

From: Slávek Banko <slavek.banko@...>
Date: Tue, 4 Feb 2014 18:05:46 +0100
Dne �t 4. �nora 2014 Michele Calgaro napsal(a):
> Slavek,
> can't we modify the script to build from a given tag instead?
> We could use a text file to contain either "master" or the tag name,
> then the script will read the config file and checkout the version from
> git according to the settings. This way, we can switch between master
> and other tags seemlessly and we don't need a separate PPA for building
> R14.

No, it is definitely not a good idea to change nightly-builds. First, it 
would cause confusion for users who use these apt sources and at the same 
time it would be a mess for QuickBuild. QuickBuild assumes that the 
version of the package is still increases - if it were in the same PPA 
alternated nightly-builds and stable-builds, packages version would jump 
up and down - just mess.

Look how it worked now, with v3.5.13-sru branch.
We have basically three groups of users:

1) ordinary users using only stable versions
2) testers for updates stable version - my ppa
3) testers on the edge of development - nightly-builds

Each of these users has set apt sources for the required PPA. It is not 
possible to be in 'nightly-builds' alternated packages "testing" and 
packages "updates". It would be undesirable for both users and 
maintainers.

Therefore, we 'need' new PPA, but the question is 'when'. One possibility 
is that the development in the master branch (and nightly-builds) will 
continue up to R14.0.0. The second possibility is that the finalization 
stable release after RC1 will continue in the new PPA. In this PPA will 
then continue maintanance updates.

Slavek
--