10.4 10.4 Beta with Update Subscription

[ŁukaszDe 38]

https://community.idera.com/developer-tools/b/blog/posts/get-ready-for-the-10-4-beta-with-update-subscription

 

[Lars Fosdal 1792]

Note that even if every update subscriber gets access to the beta, they are still under NDA and may not discuss testing 10.4 Denali in public.

 

 

[Kryvich 165]

Delphi

• Language Server Protocol for Delphi (!)
• Language Enhancements: Managed Records (after 1.5 years of waiting...)
• Unified memory management across all platforms (!)

[Markus Kinzler 174]

But again belated. Start of beta in april for a product being addressed for release "early 2020"

[Attila Kovacs 629]

Rather later than a monday version again. 

[FredS 138]

2 hours ago, Lars Fosdal said:

they are still under NDA and may not discuss testing 10.4 Denali in public.

Wasn't there also a clause that you can't even talk about it for 2 years after?

 

Pretty sure its still legal to say; I won't be on it! 🙂

 

[Georgge Bakh 29]

I hope there will be something that justifies such a secrecy. 

[Kryvich 165]

@Georgge Bakh Traditions...

[Lars Fosdal 1792]

I guess it to a certain degree reduces rumors and opinions on thin foundations - but, yeah... it is an antiquated approach for a public beta.

[David Heffernan 2345]

If you want your beta testers to find bugs, don't you want lots of testers? 

[dummzeuch 1505]

17 minutes ago, David Heffernan said:

If you want your beta testers to find bugs, don't you want lots of testers? 

So, we conclude:

They limit the number of testers => Don't want them to find bugs?

 

On the other hand: Many bug reports are that bad that they are not worth the time you spend reading them.

(But in my experience the majority of bug reports are good.)

[Lars Fosdal 1792]

I didn't read that as a conclusion, but as defining a goal for testing.
More diverse testing = better testing.

Naturally, the quality of the bug reports is important. 

• Good description of context: OS, platform, libs, etc
• Good description of symptom / problem 
• Proper steps to reproduce

[dummzeuch 1505]

1 hour ago, Lars Fosdal said:

I didn't read that as a conclusion, but as defining a goal for testing.
More diverse testing = better testing.

Naturally, the quality of the bug reports is important. 

• Good description of context: OS, platform, libs, etc
• Good description of symptom / problem 
• Proper steps to reproduce

And also: Responding to any questions that may follow.

 

(Unfortunately I am guilty of not answering questions to some of my QC(?) reports: When I'm on holiday I simply can't. Guess what? They closed the report.)

[Uwe Raabe 2057]

Just now, dummzeuch said:

They closed the report.)

You can dispute it then.