[Closed] The epic PR 1.2 anticipation thread - Page 161 - maemo.org

Active Topics

The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 3 hrs, 56 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 16 hrs ago
more...

Page 161 of 723

161

Thread Tools

	benny1967	2010-04-19 , 14:22
	Posts: 3,790 \| Thanked: 5,718 times \| Joined on Mar 2006 @ Vienna, Austria	#1601

Originally Posted by Chrome

If waiting for an update that was supposed to be released weeks ago...

... was it?

	Chrome	2010-04-19 , 14:28
	Posts: 349 \| Thanked: 309 times \| Joined on Feb 2010 @ PS/IL	#1602

Originally Posted by benny1967

... was it?

Yes

http://talk.maemo.org/showpost.php?p...5&postcount=15

	w00t	2010-04-19 , 14:33
	Posts: 1,055 \| Thanked: 4,107 times \| Joined on Oct 2009 @ Norway	#1603

Originally Posted by Chrome

Yes

http://talk.maemo.org/showpost.php?p...5&postcount=15

I don't see anything about a release date there.

I see that it is no longer under active development, and undergoing testing/QA - which is what occurs normally in a release process.

__________________
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.

	Chrome	2010-04-19 , 14:37
	Posts: 349 \| Thanked: 309 times \| Joined on Feb 2010 @ PS/IL	#1604

Originally Posted by w00t

I don't see anything about a release date there.

I see that it is no longer under active development, and undergoing testing/QA - which is what occurs normally in a release process.

Please explain: "PR1.2 was frozen weeks ago" ?

that clearly means if they didn't leave it weeks without any progress, it would be ready by now.

HugoSon	2010-04-19 , 14:43
Posts: 221 \| Thanked: 51 times \| Joined on Nov 2009 @ Germany	#1605

Originally Posted by Chrome

Please explain: "PR1.2 was frozen weeks ago" ?

that clearly means if they didn't leave it weeks without any progress, it would be ready by now.

Feature wise it's frozen - within QA they are only fixing bugs from features they want to release within PR1.2; and there are more features and bugs then we know - the public bug tracker is just a part of the whole thing.

	zehjotkah	2010-04-19 , 14:46
	Posts: 2,361 \| Thanked: 3,746 times \| Joined on Dec 2007 @ Berlin - Love this city!!	#1606

Originally Posted by Chrome

Please explain: "PR1.2 was frozen weeks ago" ?

that clearly means if they didn't leave it weeks without any progress, it would be ready by now.

there is something called "feature-freeze" that means no more features or bug-fixes added, but it is currently under testing and if this testing shows some bugs or flaws in the new, already added features or bug-fixes, these have to be resolved before release to the public.

__________________
me on Twitter

Donate to the Hildon Foundation to keep maemo.org alive!

	w00t	2010-04-19 , 14:46
	Posts: 1,055 \| Thanked: 4,107 times \| Joined on Oct 2009 @ Norway	#1607

Originally Posted by Chrome

Please explain: "PR1.2 was frozen weeks ago" ?

that clearly means if they didn't leave it weeks without any progress, it would be ready by now.

It's a concept of software engineering.

Take a look at: http://en.wikipedia.org/wiki/Freeze_...re_engineering)

('frozen for weeks' is most likely a feature freeze, in which only fixes for bugs are allowed)

	Chrome	2010-04-19 , 14:50
	Posts: 349 \| Thanked: 309 times \| Joined on Feb 2010 @ PS/IL	#1608

Ok, now thats a lot of explanations.. Thanks all

hope the update is close to get released.

little_beat	2010-04-19 , 14:53
Posts: 23 \| Thanked: 15 times \| Joined on Mar 2010 @ Moscow	#1609

Originally Posted by zehjotkah

there is something called "feature-freeze" that means no more features or bug-fixes added, but it is currently under testing and if this testing shows some bugs or flaws in the new, already added features or bug-fixes, these have to be resolved before release to the public.

Well, feature-freeze/feature-complete stage can actually occur somewhere in the middle of software life cycle, months from the release date. I really hope PR1.2 is in code-freeze/code-complete stage. Then, only the bugs found during the last testing cycle are to be fixed.