Is there a (at least roughly) defined schedule or task list one can use to see progress on Hipster? What (or who?) would define the point for hipster to be considered usable?
Cheers Stefan ________________________________________ Von: Udo Grabowski (IMK) [[email protected]] Gesendet: Freitag, 22. November 2013 11:46 An: Discussion list for OpenIndiana Betreff: Re: [OpenIndiana-discuss] Hipster ISOs On 22/11/2013 11:38, Stefan Müller-Wilken wrote: > Well, for production I'd hope for a little more than "didn't crash" ;-) but > that's already a good indication. > > Why don't we promote Hipster ISOs more visibly on openindiana.org? ... As already discussed in another thread a few days ago, /hipster is NOT for production, but a bleeding edge testbed for transition to gcc compiled OI. It can break at any time and it can eat all you data and burn your house. Do never expect at any time that this will work without flaw. Do not even consider to use that in production. OI /dev is the current near release-quality branch for productive work. -- Dr.Udo Grabowski Inst.f.Meteorology a.Climate Research IMK-ASF-SAT www.imk-asf.kit.edu/english/sat.php KIT - Karlsruhe Institute of Technology http://www.kit.edu Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026 ________________________________ Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
