Hello,
This is what I understand from what I have read here. I have to say
personally I find it quite annoying as well as the latest in dev (b134)
doesn't work on my laptop (its a video issue and prevents X from
loading), and I don't have the desire to build from source particularly
when I am uncertain whether the video issue is even fixed, so don't know
whether I could use the result of the time, etc spent on building it.
Anyway the explanation as I understand it is that dev will not be
updated beyond b134 until after the release as the next release will be
based on b134. If the dev repository were updated beyond b134 then a
situation may occur where a user has updated to b135 or higher before
the release and so would not be able to easily switch to the release as
they would need to downgrade.
Now my question would be, is the existing view of dev correct
considering the time the outside community has been waiting for the
release? May be there is a need for dev as it is (I am unsure, I would
have thought if you are following dev but want to move to stable
releases you probably will be following announcements and so would know
where not to update beyond, or you are just always wanting the latest
and so would never want to switch to release, but may be I have missed a
group), so may be there is a third group who need a repository,
something like current to reflect the current state of development at
the very leading edge.If for the rest of this I call it current just for
simplicity, I know there may be concerns on it leading to much more
work, etc, well may be it could be considered a try it entirely at your
own choice, no quality is guaranteed, it may not even boot, its been
given very minimal testing, etc.
Michael Whapples
On 01/-10/-28163 08:59 PM, Hillel Lubman wrote:
As we know, the last public update of dev repo was build 134, which was
published almost three month ago. Assuming that OpenSolaris still plans (is
it?) to follow half year release schedule, the period of dev repo freezing is
now comparable to the release period itself. This makes one wonder whether
current dev repo release policy makes any sense for general OpenSolaris user
base, those outside Oracle inner circle.
While discussions and threads like "problems with snv_14x" pop up here and
there, it is frustrating for global OpenSolaris community, since those builds are not
available from the repo anyway (unless someone likes always to use sources as a starting
point). While those within Oracle refer to secrecy and non disclosure issues regarding
the upcoming release dates, there is no reason to keep in secret the policy regarding dev
repo updates. If the plan is to release updates for some time, and then to freeze the
repo for more than a half of release period - let it be clearly specified somewhere for
the benefit of OpenSolaris community (or is it clearly stated somewhere already?). This
way everyone will know what to expect and it will help avoiding unnecessary frustrations.
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
