On Wed, Dec 02, 2015 at 12:43:16AM +0100, Michael Lotz wrote:
At some point there will be a point release updating that particular Haiku
version (i.e. R1.1). What happens then depends on our support strategy. It
either means the original release remains supported, which would imply a new
branch for R1.1 is created and new builders running R1.1 would build
packages for that release while the old builders still running R1 would
continue to build packages for R1. If we stop support for R1 as soon as R1.1
is released (which would make sense to me) the builders could be update to
R1.1 and start building for the new version.
What should happen for the nightlies? Obviously it's not feasible (or
desirable) to have a branch and a set of builders for each new hrev. Since
nightlies don't come with any support, this isn't necessary either. But how
is a given hrev matched with a given HaikuPorts package repo? Do they need
to be matched at all or is it enough to start matching them once
(pre-)releases happen (with the process above)? Which packages end up in the
nightlies would then just be decided by when they are built and therefore
what packages are available at that point in time. What hrev of Haiku is
used on the builders (and therefore is encoded as the required version) is
another question. Should they simply always update to the newest available
nightly? Keeping them at a certain hrev for a certain time could be sensible
if some particular hrev proofs to be stable. Then again that would mean
someone would have to regularly decide what hrev to use, which would
introduce manual labour.
