[oi-dev] Release engineering // planing

[Geoff Nordli]

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.

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.

thanks,

Geoff


On 13-07-11 09:58 AM, hugo at myhomeemail.co.uk wrote:
> Strongly agree on all notes Alisdair has made.
> 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.
> Regards
>> On 11 July 2013 at 17:53 Alasdair Lumsden <alasdairrr at gmail.com> wrote:
>>
>> Hi All,
>> 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.
>> 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.
>> Hipster is an experimental development branch for making rapid 
>> progress. If you break something, you can fix it after, no big deal.
>> 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.
>> And on an unrelated note, someone motivated enough should do 
>> something about www.openindiana.org <http://www.openindiana.org> - 
>> it's ugly and out of date :-)
>> Regards,
>> Alasdair
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20130711/e08396b1/attachment-0005.html>