[MGNLUI-2941] Upgrade to Vaadin 7.1.15 Created: 27/May/14 Updated: 07/Aug/14 Resolved: 07/Aug/14 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | framework |
| Affects Version/s: | 5.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Critical |
| Reporter: | Andreas Weder | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | vaadin, vaadin7.1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
The current version of Vaadin is 7.1.15 - our 5.3 codebase currently uses 7.1.7. We should consider upgrading to the latest version after proper testing before going final. We might even want to consider upgrading Vaadin to 7.2.1, which is out now. To ease taking a decision on this, I've compiled a list of major changes in all version since 7.1.7. I've marked those which have the potential to fix issues we have. Major changes in Vaadin versions since 7.1.77.1.8
7.1.9
7.1.10
7.1.11
7.1.12
7.1.13
7.1.14
7.1.15
|
| Comments |
| Comment by Andreas Weder [ 13/Jun/14 ] |
|
We briefly discussed this in project management yesterday: it would be good if we were running on the latest Vaadin version. Don't count on upgrading it during maintenance: that's only going to be done if there's a very good reason (a severe bug) for it. |
| Comment by Andreas Weder [ 13/Jun/14 ] |
|
I'm re-opening this because I'd like you to (re-)consider upgrading to 7.1.15 now, as we won't be able to do this during maintenance anymore (see my comment). |
| Comment by Christopher Zimmermann [ 16/Jun/14 ] |
|
The list of fixes does look attractive. But given the time constraints, the effort, and the risks Mikael and I feel this should be postponed. |