I got my answers on IRC: [i](19:27:22) Kush-: so if 2009.06 is based on b111, does that mean if I go install b112 (when it releases) from /dev that I can't go upgrade to the official 2009.06 copy? (19:33:31) e^ipi: yes (19:33:54) svcadm: the way I look at it is there is the choice to track dev "unstable" or release "stable" .. it's a mutually exclusive choice (19:35:34) Zikla: Could you boot to a b110 BE and then upgrade? (19:35:35) Kush-: ok, bummer. (19:35:52) Kush-: but having to wait like 6 months for some of these cool features to come out is too long. :) (if I were going with a "release") (19:36:42) Kush-: what happens if I were on b111 now and then change my repository to be /release (when 2009.06 comes out). what happens then? (19:36:45) svcadm: it's not for me on systems that I'm concerned about stability with (19:36:59) shaneoo [[email protected]] entered the room. (19:37:02) svcadm: give it a whirl, and let us know ;) (19:37:25) Kush-: ah, ok. :) (19:38:16) Kush-: yup, i understand about stability. i was under some impression that the /dev is semi-frozen until/upto the release date. (19:38:32) svcadm: what gave you that impression? (19:39:14) Kush-: thought thats what happened with 2008.11 (seem to recall some specific emails about things being frozen...) but maybe it was something else. maybe it was before all of this /dev, /release branches. (19:39:34) e^ipi: nope (19:39:47) e^ipi: dev/ is repackaged every couple weeks (19:40:15) e^ipi: release/ is frozen, bugfixed, polished, and released (19:40:20) Kush-: ok (19:40:28) e^ipi: the very nature of "stable" is that you can't have the latest and greatest right now (19:40:49) e^ipi: and it doesn't change often (19:40:53) Wild_Gees left the room (quit: Remote closed the connection). (19:41:53) Kush-: *nod* maybe there should be some other branch that can help with going from /dev to /release during these releases e.g. specific branches like 2009.06 etc.. i do'nt know. :) (19:42:44) e^ipi: why? (19:42:59) svcadm: I get the feeling you've never been on the receiving end when those kind of things are attempted ... it's usually unpleasant. e1kg echelog edvil e^ipi e-jat eklof elektronkind enderst epitaphredux erfgs esposj estibi_ eviljames evocallaghan Excedrin (19:43:16) e^ipi: if you want to follow the latest and greatest, follow it... if you want stability and some assurances of bugfix, then follow release/ (19:43:34) Wild_Gees [[email protected]] entered the room. (19:45:05) Wild_Gees left the room (quit: Client Quit). (19:45:20) e^ipi: i don't think the set of people who decide that they don't want stability, but then later change their mind is particularly large (19:45:27) Kush-: e^ipi: just timing. i have a beta system that is on b111 and lets say i want to promote it to "production" then i can use that branch. but i guess its the same thing like changing the repo to /release after 2009.06 comes out (and if i am on b111) (19:45:29) e^ipi: and probably doesn't encompass yourself either if you think about it (19:45:31) Wild_Gees [[email protected]] entered the room. (19:46:16) svcadm: e^ipi: that set of people may not be large, but somehow they manage to get into crazily lofty managerial positions (19:46:39) e^ipi: good managers let technical people make technical decisions (19:47:03) svcadm: Kush-: if I were you, I would build a new system based on /release, and migrate the services from the b111 system to the new one (19:47:18) svcadm: e^ipi: agreed (19:48:00) Kush-: yea, thats what i think is best. i completely agree with both of you and understand what you are saying. i was just wondering if these were some possiblities. about going from pilot -> production like server. (19:50:33) Wild_Gees left the room (quit: "Quit Nadoka 0.7.0-trunk (rev: 173) - http://www.atdot.net/nadoka/";). (19:50:52) Wild_Gees [[email protected]] entered the room. (19:52:34) derchris left the room (quit: "( www.nnscript.com :: NoNameScript 4.22 :: www.esnation.com )"). (19:52:40) Kush-: do you guys do enough testing to go from one release to another? i wonder if it'll be good idea to push the rolling code (111) into say /release before 2009.06 comes out? that could help in finding bugs going from one release toa nother. (19:52:42) derchris [[email protected]] entered the room. (19:53:04) Kush-: of course "enough" is subjective :) (19:54:43) svcadm: heh, indeed. I don't have any frame of reference for that. In my case, servers and supported workstations always run /release, and a few admin systems run dev, and never the twain shall meet.[/i]
Any idea when specifically 2009.06 will come out? Thanks! -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
