Just looking at the public wiki info and all. Only 8 weeks to Nov and there’s only milestone 0 from months ago. Has the release methodology changed? I’m sort of out of the loop. I see there’s this factory thing now. There will be an actual 13.2 release, right?
On 2014-09-08 23:26, xorbe wrote:
>
> Just looking at the public wiki info and all. Only 8 weeks to Nov and
> there’s only milestone 0 from months ago. Has the release methodology
> changed?
YES! A lot.
> There will be an actual 13.2 release, right?
Yep.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Yes, it has.
I see there’s this factory thing now.
Yes, and many people (self included) are running it. You can think of that as a way of testing 13.2.
There will be an actual 13.2 release, right?
Yes, there will. And it may well be the best tested ever. If you want to get started with testing, you can download a factory iso and try it.
Since no one seems to actually be saying anything other than “yes, it’s changed”, I give you my understanding from lurking around (please correct me if I get anything wrong).
Factory used to be where all new packages were dumped. When a new release started, they would take a snapshot of factory and then bug fix it and then release it.
Now, Factory is becoming a rolling release where the goal is for it to always work. There is a new repo factory-totest, which is basically like the old factory – every package just gets dumped there when finished. Then the OBS makes a snapshot built and runs the packages through the openQA automated testing system. If it all passes, then the snapshot of packages flows into Factory (from what I’ve experienced over the last 2 weeks). Since Factory is usually installable and working, when a “release” comes, then they just take a snapshot of that and call it 13.2 (or whatever version is being used). That would again probably get some bugfixing/branding/string fixes to polish it up as a final release. Meanwhile, Factory just keeps on rolling on.
On 2014-09-09 04:16, TeutonJon78 wrote:
> Now, Factory is becoming a rolling release where the goal is for it to
> always work. There is a new repo factory-totest, which is basically like
> the old factory – every package just gets dumped there when finished.
> Then the OBS makes a snapshot built and runs the packages through the
> openQA automated testing system. If it all passes, then the snapshot of
> packages flows into Factory (from what I’ve experienced over the last 2
> weeks).
Basically. But not “all” is tested. Some important things are not, and
some seem to work and do not.
> Since Factory is usually installable and working, when a
> “release” comes, then they just take a snapshot of that and call it 13.2
> (or whatever version is being used). That would again probably get some
> bugfixing/branding/string fixes to polish it up as a final release.
I hope that it doesn’t “some”, but “a lot”.
There are tasks that are simply not started till development freezes,
like, for instance, translation.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
At some time, they will split 13.2 from factory. Repos will be setup for 13.2. Installing a beta or release candidate will use the 13.2 repos rather than the factory repos. And there will be an effort to correct any remaining bugs in 13.2 before the release.
At the same time, the rolling factory will continue with new stuff. But, as a rolling release, it will roll more slowly while people put much of their time into refining 13.2.
Thanks! This page has quite a bit I found:
https://en.opensuse.org/Portal:Factory
Whoa, there’s no dvd iso torrent server?
There’s also this regarding the 13.2 release schedule:
http://turing.suse.de/~coolo/opensuse_13.2/
Whoa, there’s no dvd iso torrent server?
It probably doesn’t make sense, as the ISOs change quite often (maybe daily).
On Tue, 09 Sep 2014 07:46:01 GMT
xorbe <xorbe@no-mx.forums.opensuse.org> wrote:
>
> Thanks! This page has quite a bit I found:
> https://en.opensuse.org/Portal:Factory
>
> Whoa, there’s no dvd iso torrent server?
>
>
If you pick the iso you need from
http://download.opensuse.org/factory/iso/ and click on “details” you
should be presented with a list of various types of download - I usually
use metalink - but I see the one I usually use has a 404 error for
“details”. Nice!
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.2-m0 (64-bit); KDE 4.14.0; AMD Phenom II X2 550 Processor;
Kernel: 3.16.1; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)
Which one?
I just randomly clicked on one and it worked fine.
Maybe you did this when the update was in progress? Or a stale browser cache?
A new snapshot has been published today… 
I just use “aria2c” to download. I don’t bother to click on “details”. It turns out that “aria2c” looks for a metalink and will prefer that to a direct download if it can find it.
On Tue, 09 Sep 2014 19:36:01 GMT
wolfi323 <wolfi323@no-mx.forums.opensuse.org> wrote:
>
> Cloddy;2663693 Wrote:
> > If you pick the iso you need from
> > http://download.opensuse.org/factory/iso/ and click on “details” you
> > should be presented with a list of various types of download - I
> > usually use metalink - but I see the one I usually use has a 404
> > error for “details”. Nice!
> >
> Which one?
> I just randomly clicked on one and it worked fine.
>
> Maybe you did this when the update was in progress? Or a stale browser
> cache?
> A new snapshot has been published today… 
>
>
That’s what happened. It was in the process of updating from 20140901
to 20140904. I should have thought of that as I’d already seen an
e-mail to the effect that a new release was out.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.2-m0 (64-bit); KDE 4.14.0; AMD Phenom II X2 550 Processor;
Kernel: 3.16.1; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)
On 2014-09-09 21:56, nrickert wrote:
> I just use “aria2c” to download. I don’t bother to click on “details”.
> It turns out that “aria2c” looks for a metalink and will prefer that to
> a direct download if it can find it.
What link do you give to it? I have always given it explicitly the
metalink one, I did not know it could dig it out by itself :-?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Once I install a factory ISO, all it needs is zypper refresh / up as usual right to get the latest updates? No need to install the latest factory ISO right? Just want to be perfectly clear. I installed to vbox for testing, was a little surprised it recommended btrfs / xfs on a 16GB partition.
I would suggest “zypper refresh” (perhaps not needed), followed by “zypper dup”.
On 2014-09-11 18:56, nrickert wrote:
>
> xorbe;2664043 Wrote:
>> Once I install a factory ISO, all it needs is zypper refresh / up as
>> usual right to get the latest updates?
>
> I would suggest “zypper refresh” (perhaps not needed), followed by
> “zypper dup”.
No, “zypper refresh” is never needed, unless you disabled automatic
refresh, or you want to check for a change sooner than the refresh
interval times out.
On the other hand, on both factory and tumbleweed, you have to update
with “zypper dup”.
The “zypper patch” of a normal release does not work because the update
repo is not populated. And “zypper up” is not always reliable, because
of the nature of factory: packages removed, changed, etc. Even downgraded.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Ah, thanks for the up vs dup description! (I’ve always used “zypper ref ; zypper dup” actually.)