1. Steen Jakobsen
  2. PowerBuilder
  3. Thursday, 13 December 2018 04:16 AM UTC

Hi I can see on the roadmap this morning that PB 2018 is delayed 6 months.

 

Is that a typo :-) or what is going on ?

 

Thanks 

//Steen

Julie Jiang @Appeon Accepted Answer Pending Moderation
  1. Friday, 14 December 2018 06:11 AM UTC
  2. PowerBuilder
  3. # 1

Hi Steen, 

First of all, PowerBuilder 2018 is delayed.  We have recently updated the roadmap page, and are sending emails to all customers, to notify everyone of this schedule change.  

However, we do not plan to delay it for 6 months. In fact, the feature development has already been completed in house. Very soon we will start the beta testing program. 

You must have noticed that we state "Q2, 2019" for the PB 2018 GA on the roadmap. There are several reasons: (1) Considering that the c# development feature added in this version is a new subject for most PB users, we want to give more time for people to learn and try the feature in their beta testing. (2) We shall factor in the time needed for implementing P0/P1 feedbacks collected during the beta cycle. (3) We target the delivery to be in Spring.

More news will be announced on the website. Thanks for your interest.  Please stay tuned!

Best regards...Julie

Comment
There are no comments made yet.
Kim Berghall Accepted Answer Pending Moderation
  1. Friday, 14 December 2018 00:48 AM UTC
  2. PowerBuilder
  3. # 2

I am glad they will take extra time to test it more. Much better than releasing it prematurely. I just wish they would take the opportunity and rename it to PowerBuilder 2019, which is what it should have been named from the beginning.

Comment
  1. Sivaprakash BKR
  2. Friday, 14 December 2018 06:35 AM UTC
Yes, I fully agree. Instead of releasing new features, with bugs and for future enhancements, it'll be better to release feature which are complete in nature and thoroughly checked.



At the same time, it's important to fix existing bugs which blocks porting of applications to newer version of Powerbuilder. Hope PB developers are not in a hurry to port / develop applications in C#. Their pressing area would be to implement, fix bug, upgrade existing applications to the latest platforms.



Hope Appeon will study this area also.

  1. Helpful
  1. Armeen Mazda @Appeon
  2. Friday, 14 December 2018 08:49 AM UTC
Hi Kim, There are lots of places to change in the product UI, filenames, documentation, etc. so it is not a trivial effort. Nonetheless, we will seriously consider this suggestion for the final release that is tentatively scheduled for Spring 2019. But for the beta version there would just be no time to rename it... just FYI.
  1. Helpful
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Thursday, 13 December 2018 13:34 PM UTC
  2. PowerBuilder
  3. # 3

Hello,

If PB 2018 is delayed, we would like to know the status of backward compatibility of RICH EDIT TEXT in 2017 R3.   Here we badly depend on this feature to be enabled in R3, as the scheduled implementation is 1st Apr 2018.   With bad performance issue with the currently bundled editor, the previous one is the one where our solution lies.

Hope that will not be delayed and we here badly need it in the month of Jan'2019.   cry

Happiness Always
BKR Sivaprakash

 

Comment
  1. Derek Hammonds
  2. Thursday, 13 December 2018 20:05 PM UTC
This is THE one and only bug fix we need immediately... a fix to the plethora of BUGS introduced by appeon and their ridiculous, terrible, no-good, lousy rich text editor replacement.

  1. Helpful
  1. Julie Jiang @Appeon
  2. Friday, 14 December 2018 06:01 AM UTC
Hi BKR and Deresh,



We will provide a PB 2017 R3 MR in early January, 2019. The MR will include the backwards-compatible TX Text Control that was incorporated in PowerBuilder 12.6.



Best regards, Julie
  1. Helpful
  1. Miguel Leeuwe
  2. Tuesday, 18 December 2018 11:42 AM UTC
Thank god! Same here. We've been waiting and waiting.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.