/dev is solid, but /hipster is ripe with breaking. The only way to do that is
to move /dev to /release and when /hipster is "mostly" stable, then move it to
/dev to work out the rest of the problems before moving to /release.
This would have to be done on a mostly conservative schedule like NetBSD
instead of more quickly so the stability of OI doesn't change.
But I do have a question about another branch. What is /experimental for and
how often is it updated and how is it updated?
________________________________
From: Erol Zavidic <[email protected]>
To: OpenIndiana Developer mailing list <[email protected]>
Sent: Friday, July 12, 2013 10:42 AM
Subject: Re: [oi-dev] Release engineering // planing
On 12 July 2013 13:49, G B <[email protected]> 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
_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev
_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev
