<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Once, there was a plan to implement similar system, which was proposed in this thread. /experimental was supposed to be something /hipster is. Things from /experimental would move to /dev. </div><div><br></div><div>So, we should be careful and not start doing something, which could have worked, but never did because of confusion about which development branch should be used, lack of man power and interest from developers. </div><div><br></div><div>Adam</div><div><br>On 12 Jul 2013, at 21:18, G B <<a href="mailto:g_patrickb@yahoo.com">g_patrickb@yahoo.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">/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.<br><br>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.<br><br>But I do have a question about another branch. What is /experimental for and how often is it updated and how is it updated?<br><div><span><br></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b>
Erol Zavidic <<a href="mailto:erolms@gmail.com">erolms@gmail.com</a>><br> <b><span style="font-weight: bold;">To:</span></b> OpenIndiana Developer mailing list <<a href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a>> <br> <b><span style="font-weight: bold;">Sent:</span></b> Friday, July 12, 2013 10:42 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [oi-dev] Release engineering // planing<br> </font> </div> <div class="y_msg_container"><br><div id="yiv9374786607"><div dir="ltr">On 12 July 2013 13:49, G B <span dir="ltr"><<a rel="nofollow" ymailto="mailto:g_patrickb@yahoo.com" target="_blank" href="mailto:g_patrickb@yahoo.com">g_patrickb@yahoo.com</a>></span> wrote:<br><div class="yiv9374786607gmail_extra"><div class="yiv9374786607gmail_quote"><blockquote class="yiv9374786607gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="font-size:12pt;font-family:times new roman, new york, times, serif;">/hipster should be the -current like FreeBSD<br>/dev should be -stable like FreeBSD<br>/release or /stable should be -RELEASE like FreeBSD<br>
<br>/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.<br>
<br>Thus, /dev and /release will be sunstudio, but I don't know how one can get /hipster promoted to /dev because of gcc.<br><br>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. <a rel="nofollow" target="_blank" href="http://opencsw.org/">opencsw.org</a> has many current packages available, so anyone using /dev and /release can get them from <a rel="nofollow" target="_blank" href="http://opencsw.org/">opencsw.org</a>.<br>
<br></div></div></blockquote></div><br></div><div class="yiv9374786607gmail_extra">Important question over here:<br><br></div><div class="yiv9374786607gmail_extra">Are we ever going to promote hipster to /dev or /release then? This is question in particular due to gcc/sunstudio differences.<br>
<br></div><div class="yiv9374786607gmail_extra">Cheers,<br>Erol<br></div></div></div><br>_______________________________________________<br>oi-dev mailing list<br><a ymailto="mailto:oi-dev@openindiana.org" href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br><a href="http://openindiana.org/mailman/listinfo/oi-dev" target="_blank">http://openindiana.org/mailman/listinfo/oi-dev</a><br><br></div> </div> </div> </div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>oi-dev mailing list</span><br><span><a href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a></span><br><span><a href="http://openindiana.org/mailman/listinfo/oi-dev">http://openindiana.org/mailman/listinfo/oi-dev</a></span></div></blockquote></body></html>