|
Hi,
Where can I get the information about the issues/defects fixed in the latest 4.2.1 edition and what are the new features/enhancements implemented in this release?
Thanks in advance.
Regards,
Vinay
Active Forum Topics
- Are there any BJSF equivalent for jstl:forEach and jstl:if loop
- suggestBox Issue
- Selecting multiple checkbox using XPath
- btl.getValue() wont get values of rows behind the first page of a pager
- How to apply different styles for the 2 list grids in same page
- TreeGrid
- How to set Focus on Form fields in an AccordionItem when selected
- treeGrid sort bug?
- Achieve find functionality
- Is there a way to to modify pager to include input box
Recent Blog Posts
- bb.command.load doesn't work with e:fragment
- 4.3.1 Demos Available for Download
- JSF Edition 4.3.1 Released
- Client Edition 4.3.1 Released
- Client Edition 4.3.1 Eclipse Plugin Released
- Backbase Bundle for TextMate
- Client Edition 4.3.0 Released
- Advanced 3D Animations and Transitions
- Telamon Visual Ajax Builder Beta sent to Early Adopters
- Backbase in Visual Studio 2008 Express in 1 Minute
In release notes document
30 June, 2008 - 16:15 — PiotrekYou can find it in Release notes PDF, which is located either here http://download.backbase.com/docs/client/current/Release%20Notes.pdf or in the ZIP file with your Backbase release.
Release notes does not have list of fixed defects..
1 July, 2008 - 11:18 — vinayjThanks Piotrek,
I've already taken a look at the Release Notes, but it is not giving clear idea of kind of performance improvement achieved in this release. Also I am more interested in the defects that got resolved. Since we are already using this framework from version 4.1 and some of the issues got discussed on this forum from my developers, I am more interested in knowing which of the defects got resolved in these release. Release notes is not giving me those details. Even a blog entry (http://bdn.backbase.com/blog/jepc/client-edition-421-released) is saying 100+ defects resolved and comments on this entry are suggesting that this information can be provided offline. Any insight on this will be highly appreciated.
Regards,
Vinay Joshi
I was looking for more
1 July, 2008 - 11:21 — PiotrekI was looking for more detailed (than release notes) description of fixes and improvements as well and I did not find them. I guess it is available in Backbase' internal tracker, but obviously it should be published, at least for developers. Eventually, it is us who use Backbase Framework and it is us who struggle to upgrade applications to the newest version. And without the exact list of changes it is more difficult and time consuming.
Yes, I agree
1 July, 2008 - 11:30 — vinayjYes, I agree. It really help in deciding/prioritizing the upgrade. Not sure what is a philosophy behind not publishing this information.
Regards,
Vinay Joshi
Fixed Issues list
1 July, 2008 - 13:30 — andysHi Piotrek and vinayj,
Thank you for triggering the "fixed issues list" argument. It is an interesting topic as well as for myself.
So far, we have the list for internal only. I did not realize that it is actually will be a good means to help you as a developer in developing your application (when upgrading to the next release).
I will put this as a feature request in our issue tracking system.
For all, thanks for the input. It will help us getting better and better.
Andys
+1 for this feature request
1 July, 2008 - 18:27 — tordona+1 for this feature request
+1 for this feature request
1 July, 2008 - 18:47 — mwrLack of access to such a list has made upgrading from 4.1.2 to 4.2 untenable for us. Upgrading to 4.2.1 may offer fixes for many of the problems we encountered while trying to upgrade to 4.2, but how would we know without access to such a list?
Yes, I am all for adding a
1 July, 2008 - 20:54 — jbackbaseYes, I am all for adding a fix list to the release notes!
BB 4.3 fixed bugs list
7 October, 2008 - 11:32 — PiotrekOK, so Backbase 4.3 has been discreetly ;) released. Can we have any hope for getting detailed a list of what has been fixed? I guess a new release deserves a new thread, so it's here: http://bdn.backbase.com/node/5462
Fixed Issues List
9 October, 2008 - 08:13 — DanielMacDonaldHello all,
Here is a link to the fixed issues list, along with the new and improved feature and change log, for the latest release of Client Framework: http://bdn.backbase.com/client/changelog
Best regards,
Daniel MacDonald
Programmer/Writer
Backbase
filter the list
1 July, 2008 - 22:07 — rbWell... i quess the release notes say 100+ issues fixed. I'm not really sure i want to know all issues that were resolved, it might be a hassle to look through all of them and figure out what they mean. I quess they already filter them by placing it in the "what's new" section. We also have an issue list, and i know for sure that there are many issues that are more internal and not suitable to be published, although they are fixed in the product... perhaps they have the same problem.
I cannot see any problem in
2 July, 2008 - 09:40 — PiotrekI cannot see any problem in publishing a detailed list AND release notes in current (brief) form. If you are not interested in reading details, you read only a general notes - simple.
Some people experience issues which are not documented in release notes. If they don't know if that specific issue has been fixed, they don't know if it is worth spending time on upgrading.
Agree, but no harm in publishing
2 July, 2008 - 10:15 — vinayjI agree that not all issues are important to us. But, there is no harm in publishing this information. Also not everything can be summarized into what's new section.
Consider a scenario where a developer have faced any issue in one of the features, which has been discussed with backbase/or on this forum. Till the time the issue get fixed, the developer might be blocked on that or might have found out a workaround for that problem. Now, from the developer's perspective, if he come to know that the issue is been fixed in the new release he can decide on upgrading. If this release does not contain this issue and other issues that are fixed are not bringing him/her any major advantage he/she can still continue with the old release. There it comes very handy to him/her.
Moreover, as a general practice, release notes contains list of defects that are fixed.
Regards,
Vinay Joshi
Public issue tracker
2 July, 2008 - 15:31 — rbMaybe Backbase can consider having a public issue tracking system... then the community can submit their problems and track them. Also, this allows us to have a list of all issues fixed without them having to publish it in the release notes. It's just that I foresee problems with the issues in the release notes: what if they are not clear? when they have a public issue tracker you can ask questions about a specific issue... Just a suggestion!
Read-only issue tracker
2 July, 2008 - 15:43 — PiotrekTo be honest, I would not like everyone being able to submit issues to the tracker. It easily leads to a mess, issue reports duplicating etc.
I guess the Forums are perfect for submitting issues by users, and then BackBase employees only should be able to "filter" them and submit to tracker (as it actually is done now).
Most developers of a serious
1 October, 2008 - 09:08 — dmitriidMost developers of a serious programming framewrok post lists of things they fix.
See, for instance:
http://extjs.com/deploy/dev/CHANGES.html
http://developer.yahoo.com/yui/build/container/README
http://qooxdoo.org/about/release_notes/0.8
http://dojotoolkit.org/book/dojo-1-2-release-notes
Since these are organized by module, it's easy to see all the relevant changes
Most developers of a serious
7 October, 2008 - 16:11 — yudiHi All,
I try to bring this issue (issues fixed documentation) to the development team and add this as feature request for BB release note into our issue tracking system
cheers,
Yudi