But there also exists a site called openSUSE Forums where the Pre-Release/Beta Forum claims to be for "Questions about pre-release versions of openSUSE Linux ". So without applying your spin, the repo referenced by caf4926, that doesn’t constitute a pre-release version of openSUSE, has a better fit in this forum don’t you think? 
consused wrote:
> But there also exists a site called ‘openSUSE Forums’
> (http://forums.opensuse.org) where the Pre-Release/Beta Forum claims to
> be for "Questions about pre-release versions of openSUSE Linux ". So
> without applying your spin,
i have not applied any “spin”…instead i asked a question admitting i
don’t know the answer and so i’m confused…
i thought everything in factory was to be released with the next
version of openSUSE, and was therefore by definition pre-release
software…unless of course someone (who i do not know) decides to
move it to 11.2 oss and 'release it as an update/upgrade…
because KDE (or Adobe, or SUN or anyone else) ‘releases’ a new version
it is not automatically incorporated into the oss without testing and
therefore remains pre-release, in factory (for testing), until such
time as it is released in the next version of openSUSE, or sooner by
move to oss…
> the repo referenced by caf4926, that doesn’t
> constitute a pre-release version of openSUSE, has a better fit in this
> forum don’t you think?
no, it is one small part of the next/pre-release version of openSUSE…
i think when the KDE devs release a new version to the universe (just
like a kernel released by the kernel hackers) which has not flowed to
the oss repos of any/all supported openSUSE it awaits release, after
testing…
now, those users who wish to be software testers are encouraged to do
so and report their finding via bugzilla and the other methods
mentioned in oldcpu’s into to the testing forum (which i cited)…
and, to me it seems that cite i quoted agrees with my thinking…do
you have contravening information?
if so, i would still like to know how we can users can determine which
directories in factory are ‘released’ for use with the supported
versions, and which are not…and, why they have not flowed out of
factory and into oss…
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
i thought everything in factory was to be released with the next
version of openSUSE, and was therefore by definition pre-release
software…
True. But. It was for Eg; In the repo I quoted: 4.4.2, which was not due to be released in the next release. Now it’s 4.4.3, which is due to be released.
Like I said, DD, you are a font of wisdom and essentially you have it correct, probably more so than me.
Currently I’m running 11.3 M7 with kde4.5beta1 and it’s basically solid. I could use this all day without a hitch, unusual for such a chaotic mix.
Nuff said about this released/pre-release. Just enjoy it.
caf4926 adjusted his/her AFDB on Thu 27 May 2010 12:26 to write:
>
> Forgot to mention.
> kde login manager is borked
>
> Try the Session or Menu button:)
>
>
Caf,
Is there going to be a fix for other themes?
Reason I ask is that with my “customised” theme I no longer have the ability
to resize widgets and if i want to move them around my workspace after I
unlock them there are no pop-outs to move/resize/delete them.
Or have I missed something in the docs?
There are a couple of themes that have the pop-outs but I do not want to use
them, as it is “my” desktop is b0rked 
Well not exactly B0rked I can still use it but it is a pain to change
anything.
Cheers.
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
baskitcaise adjusted his/her AFDB on Thu 27 May 2010 22:54 to write:
Scrub that caf, don`t know what I did but it seems to be working about 95%
of the time now.
Still cannot get my customised theme to look correct but at least got the
side bars now.
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
I agree that users/members, especially new ones, need a simple guideline as to where to post about different versions of let’s say DE’s for example.
We know that 11. 2 is current (+ earlier if still supported), and we know that 11.3 is definitely “pre-release”. You don’t really need to sub-divide below that, and if you do then it becomes too complex. So you can divide according to repo source as follows:
Applications forum gets anything coming from repos marked for 11.2 (or earlier versions). Some of these repos may have the word factory in the url, but must include 11.2 as well.
Pre-Release/Beta forum gets repos marked only as Factory i.e no 11.x in the url (will be in the next openSUSE release). 11.3 repos are just snapshots accumulated from the various factory repos.
I think if you look at the repository lists including the additional ones in the wiki, you will find each one should slot into only one of those forums.
consused wrote:
> Applications forum gets anything coming from repos marked for 11.2
> (or earlier versions). Some of these repos may have the word factory in
> the url, but must include 11.2 as well.
>
> Pre-Release/Beta forum gets repos marked only as Factory i.e no 11.x
> in the url (will be in the next openSUSE release). 11.3 repos are just
> snapshots accumulated from the various factory repos.
that is okay with me, if that is what is intended…but, still i
wonder why any repo path with ‘factory’ in it has a mix of released
and pre-released software…
i mean, the paths are either stable, unstable or factory…
and, imho we have enough trouble here trying to keep the n00bs from
killing their system with 25 repos so that we don’t need to encourage
them to try be beta testers–heck, they can’t recognize what is a
‘bug’ and what is exactly perfect, but not exactly like what they just
jumped off a ship to get away from…
to me it is simple: if it is in factory it is not released, and should
not be trumpeted here for all to jump into and generate another three
dozen how-do-i-solve-this-crappy-Linux-problem?
sure, we need testers…but, ‘testers’ with no understanding of what
is going on are not are not much testing help to begin with and just
clog the help fora with questions proving they are not qualified to be
factory testers…
ymmv…i’m not trying to change anything, rather just trying to
understand the why of putting released software in the factory
stream…or, ‘selling’ pre-released software to those unprepared to
test and report…
fini
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
Caf,
Is there going to be a fix for other themes?
Unfortunately I don’t have the necessary skill set to answer this question, but logic dictates the affirmative
Nothing official, just a personal guideline offered for anyone to follow, with apologies if any member of Staff doesn’t see it that way. I understand most of the concerns you expressed here. Those of us who have been in the industry a long time are comfortable with the simple distinction between released and pre-released software support. However I think openSUSE introduced at least two changes that directly impact the forum and therefore those of us choosing to provide help voluntarily:
-
Availability of sub-system repos from Factory, including repos for released versions of openSUSE. Hence any anomaly in the odd repo url that include the word “factory”.
-
The development route map and availability of openSUSE Milestones for testing.
These facilities are there and publicized in the wiki. Members will use them and ask for help, just as water flows downhill. Personally I draw the line at “unstable” and probably wouldn’t be in a position to offer help for that.