This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
We are having problems (means getting a lot of negative feedback) after releasing patches that says : no change in splash screen... see issue 208627 ... and please use THAT issue for any further discussion, do not put it here, thanks in advance. The possible solution would be to change the way we use branding ... change the version number in splash screen and use text field instead of graphic, text read from bundle : - we can stay with one graphic for the whole release (no changes in pictures during a release cycle) - also we might put there more than just a number So for example : - start to work on 7.2 ... - development builds .... splash says NetBeans "7.2 Development Version" - Beta .... splash says NetBeans "7.2 Beta" - RCs .... splash says NetBeans "7.2 RC 1" .... RC X - releasing major release 7.2 ... splash says NetBeans "7.2" - building 7.2.1 .... splash says NetBeans "7.2.1 Development Version" - releasing 7.2.1 ... splash says NetBeans "7.2.1" - upgrade from 7.2 to 7.2.1 ... splash says NetBeans "7.2 with patch 1" - building 7.2.2 .... splash says NetBeans "7.2.2 Development Version" - releasing 7.2.2 ... splash says NetBeans "7.2.2" - upgrade from 7.2 to 7.2.2 ... splash says NetBeans "7.2 with patch 2" - upgrade from 7.2.1 to 7.2.2 ... splash says NetBeans "7.2.1 with patch 2"
I'm preparing a summary this issue and outline of possible solutions. I'll add the link here soon.
*** Bug 208627 has been marked as a duplicate of this bug. ***
Marian, would you mind changing your issue to be a duplicate of my issue 208627? In that way we can keep the already existing discussion in one place. You could add your issue description there and change the title of issue 208627 appropriately. What do you think?
(In reply to comment #3) > Marian, would you mind changing your issue to be a duplicate of my issue > 208627? In that way we can keep the already existing discussion in one place. > You could add your issue description there and change the title of issue 208627 > appropriately. What do you think? No, discussion should run in issue 208627. This is only placeholder for solutions we will do. At the end we will close (of-course) both issues as fixed.
Not all cases closed to 7.2, leave it open for next release.
Any resolution planned for 7.3 beta? Why is this a P1 defect?
No response after my last comment -> changing priority to P3. If this is required for 7.3, I would like to know what are the next steps, when and by whom.
I haven't seen any negative feedback for a while, so assume we already addressed it. Thanks all for participation.