[oi-dev] Release engineering // planing

Erol Zavidic erolms at gmail.com
Fri Jul 12 15:42:04 UTC 2013


On 12 July 2013 13:49, G B <g_patrickb at yahoo.com> wrote:

> /hipster should be the -current like FreeBSD
> /dev should be -stable like FreeBSD
> /release or /stable should be -RELEASE like FreeBSD
>
> /hipster can keep having its breakage, that is fine.  But what I'd see is
> /dev get illumos-gate updates and tested and when no problems are found and
> it is stable, then get promoted to /release, and keep this cycle.
>
> Thus, /dev and /release will be sunstudio, but I don't know how one can
> get /hipster promoted to /dev because of gcc.
>
> I guess it could be that /hipster always stays out there as a -current
> while /dev and /release stay with sunstudio because right now /dev is most
> rock-solid and that should not be taken away.  While /hipster has newer
> packages available, if someone is on /dev or /release there are other
> options rather than trying to get what is in /hipster.  opencsw.org has
> many current packages available, so anyone using /dev and /release can get
> them from opencsw.org.
>
>
Important question over here:

Are we ever going to promote hipster to /dev or /release then? This is
question in particular due to gcc/sunstudio differences.

Cheers,
Erol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20130712/73c3acec/attachment-0005.html>


More information about the oi-dev mailing list