<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
As I have a few servers deployed in production with OI I am happy
to see the ball rolling again. I use OI as a virtualization host
with VBox. <br>
<br>
How do we get it so there are "checkpoints" in the release cycle
that you can target a specific point in time? Something that
doesn't cause too much burden to manage from a developer point of
view. When I am deploying an OI server I can target that
date/version. <br>
<br>
thanks,<br>
<br>
Geoff <br>
<br>
<br>
On 13-07-11 09:58 AM, <a class="moz-txt-link-abbreviated" href="mailto:hugo@myhomeemail.co.uk">hugo@myhomeemail.co.uk</a> wrote:<br>
</div>
<blockquote
cite="mid:2045047787.287226.1373561929485.open-xchange@email.1and1.co.uk"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div> Strongly agree on all notes Alisdair has made. </div>
<div> </div>
<div> Furthermore, if people are using OI in production, they
should have their own suitable testing procedures in place to
avoid the majority of (if not all) upsets. </div>
<div> </div>
<div> Regards </div>
<div> </div>
<blockquote style="position: relative; margin-left: 0px;
padding-left: 10px; border-left: solid 1px blue;" type="cite">
On 11 July 2013 at 17:53 Alasdair Lumsden
<a class="moz-txt-link-rfc2396E" href="mailto:alasdairrr@gmail.com"><alasdairrr@gmail.com></a> wrote: <br>
<br>
<div dir="ltr"> Hi All,
<div> </div>
<div> Back in the days of oi-build, we tried to have a
process, and enforce quality, and it just resulted in super
slow progress followed by near-death. Andrzej didn't
contribute at all as he didn't like the bureaucracy, he just
wants to hack-and-go. </div>
<div> </div>
<div> So after all that, I basically think Andrzej is
completely right with his current approach - breaking things
should be allowed. You can't make an omelette quickly and
easily without breaking a few eggs. </div>
<div> </div>
<div> Hipster is an experimental development branch for making
rapid progress. If you break something, you can fix it
after, no big deal. </div>
<div> </div>
<div> I do think that /dev should get moved to /release, and
/hipster should go to /dev. Not many know about hipster
beyond the oi-dev list. It would show people in the outside
world that progress is being made on OI. </div>
<div> </div>
<div> And on an unrelated note, someone motivated enough
should do something about <a moz-do-not-send="true"
href="http://www.openindiana.org">www.openindiana.org</a>
- it's ugly and out of date :-) </div>
<div> </div>
<div> Regards, </div>
<div> </div>
<div> Alasdair </div>
<div> </div>
</div>
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>