[xwiki-devs] [VOTE] Upgrade to GWT 2.0 before 2.2M2 release
Hi devs, I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release. Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in: * ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo: mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar Who can help me with that? All unit and integration tests pass locally so here's my +1. Thanks, Marius
On 01/25/2010 08:09 PM, Marius Dumitru Florea wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release.
+1
Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
Done, http://maven.xwiki.org/externals/com/google/gwt/gwt-incubator/20091216-r1739...
All unit and integration tests pass locally so here's my +1.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On 01/25/2010 08:09 PM, Marius Dumitru Florea wrote:
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
What is this file supposed to do, and why doesn't it have a stable release version? -- Sergiu Dumitriu http://purl.org/net/sergiu/
Sergiu Dumitriu wrote:
On 01/25/2010 08:09 PM, Marius Dumitru Florea wrote:
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
What is this file supposed to do, and why doesn't it have a stable release version?
As you can see on http://code.google.com/p/google-web-toolkit-incubator/wiki/Downloads this is their release for GWT 2.0. They are not consistent about naming their versions. We use the GlassPanel widget from this library to make WYSIWYG dialogs modal. Thanks, Marius
Hi Marius, On Jan 25, 2010, at 8:09 PM, Marius Dumitru Florea wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release. Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
All unit and integration tests pass locally so here's my +1.
My take is that it's just too dangerous to do now, especially since we should already have released XE 2.2M2 and we're late. I don't think there's any value in taking unnecessary risks at this point. Personally I'd much rather wait for XE 2.3M1 (i.e a few days since we'll create a branch at the end of this week - I also need that branch to continue my work on references which I have also stopped last Thursday in order to not cause more unnecessary risks). So I'd be -1 right now since I don't see a compelling reason to do that now. If everyone else agrees, I'll reconsider my judgement and move that to a -0. Thanks -Vincent PS: If you really want to start committing it now, we can easily do it on a branch and merge in a few days. The merge would probably not be hard.
Hi Vincent, Vincent Massol wrote:
Hi Marius,
On Jan 25, 2010, at 8:09 PM, Marius Dumitru Florea wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release. Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
All unit and integration tests pass locally so here's my +1.
My take is that it's just too dangerous to do now, especially since we should already have released XE 2.2M2 and we're late. I don't think there's any value in taking unnecessary risks at this point.
I don't understand why you think this upgrade is so dangerous. Selenium tests cover a significant number of use cases and if GWT 2.0 leads to a regression we can still fix it in RC1. We can even revert the upgrade if it's really bad. I don't have bad experiences with GWT upgrades. The last one (to GWT 1.7) produced only one regression on the menu bar, which was caught by the selenium tests. GWT 2.0 is supposed to be better and fixes some bugs over GWT 1.7 which means that the widgets used by the editor are better. Thanks, Marius
Personally I'd much rather wait for XE 2.3M1 (i.e a few days since we'll create a branch at the end of this week - I also need that branch to continue my work on references which I have also stopped last Thursday in order to not cause more unnecessary risks).
So I'd be -1 right now since I don't see a compelling reason to do that now. If everyone else agrees, I'll reconsider my judgement and move that to a -0.
Thanks -Vincent
PS: If you really want to start committing it now, we can easily do it on a branch and merge in a few days. The merge would probably not be hard.
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi again Marius, On Jan 25, 2010, at 9:25 PM, Marius Dumitru Florea wrote:
Hi Vincent,
Vincent Massol wrote:
Hi Marius,
On Jan 25, 2010, at 8:09 PM, Marius Dumitru Florea wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release. Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
All unit and integration tests pass locally so here's my +1.
My take is that it's just too dangerous to do now, especially since we should already have released XE 2.2M2 and we're late. I don't think there's any value in taking unnecessary risks at this point.
I don't understand why you think this upgrade is so dangerous.
Any upgrade done at the last moment is dangerous. And even more for a major release upgrade. If it were about upgrading from Groovy 1.7 to Groovy 2.0 I'd say the same.
Selenium tests cover a significant number of use cases and if GWT 2.0 leads to a regression we can still fix it in RC1. We can even revert the upgrade if it's really bad. I don't have bad experiences with GWT upgrades. The last one (to GWT 1.7) produced only one regression on the menu bar, which was caught by the selenium tests. GWT 2.0 is supposed to be better and fixes some bugs over GWT 1.7 which means that the widgets used by the editor are better.
I'm definitely not against upgrading. For me it's just a timing issue. Since everyone else seems to think it's a good idea I'm moving my vote from -1 to -0. Please just make sure that the final release is not delayed because of this (in case something goes wrong). Thanks -Vincent
Thanks, Marius
Personally I'd much rather wait for XE 2.3M1 (i.e a few days since we'll create a branch at the end of this week - I also need that branch to continue my work on references which I have also stopped last Thursday in order to not cause more unnecessary risks).
So I'd be -1 right now since I don't see a compelling reason to do that now. If everyone else agrees, I'll reconsider my judgement and move that to a -0.
Thanks -Vincent
PS: If you really want to start committing it now, we can easily do it on a branch and merge in a few days. The merge would probably not be hard.
0 Abstaining due to lack of knowledge on the topic. Caleb Vincent Massol wrote:
Hi again Marius,
On Jan 25, 2010, at 9:25 PM, Marius Dumitru Florea wrote:
Hi Vincent,
Vincent Massol wrote:
Hi Marius,
On Jan 25, 2010, at 8:09 PM, Marius Dumitru Florea wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release. Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
All unit and integration tests pass locally so here's my +1. My take is that it's just too dangerous to do now, especially since we should already have released XE 2.2M2 and we're late. I don't think there's any value in taking unnecessary risks at this point. I don't understand why you think this upgrade is so dangerous.
Any upgrade done at the last moment is dangerous. And even more for a major release upgrade. If it were about upgrading from Groovy 1.7 to Groovy 2.0 I'd say the same.
Selenium tests cover a significant number of use cases and if GWT 2.0 leads to a regression we can still fix it in RC1. We can even revert the upgrade if it's really bad. I don't have bad experiences with GWT upgrades. The last one (to GWT 1.7) produced only one regression on the menu bar, which was caught by the selenium tests. GWT 2.0 is supposed to be better and fixes some bugs over GWT 1.7 which means that the widgets used by the editor are better.
I'm definitely not against upgrading. For me it's just a timing issue.
Since everyone else seems to think it's a good idea I'm moving my vote from -1 to -0. Please just make sure that the final release is not delayed because of this (in case something goes wrong).
Thanks -Vincent
Thanks, Marius
Personally I'd much rather wait for XE 2.3M1 (i.e a few days since we'll create a branch at the end of this week - I also need that branch to continue my work on references which I have also stopped last Thursday in order to not cause more unnecessary risks).
So I'd be -1 right now since I don't see a compelling reason to do that now. If everyone else agrees, I'll reconsider my judgement and move that to a -0.
Thanks -Vincent
PS: If you really want to start committing it now, we can easily do it on a branch and merge in a few days. The merge would probably not be hard.
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Mon, Jan 25, 2010 at 20:09, Marius Dumitru Florea <[email protected]> wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release.
+1 That's a milestone, that's milestone job to introduce new things and we WILL upgrade to 2.0 anyway so i don't see why not doing it now especially if all unit and integration tests pass.
Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
All unit and integration tests pass locally so here's my +1.
Thanks, Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Jan 25, 2010, at 8:40 PM, Thomas Mortagne wrote:
On Mon, Jan 25, 2010 at 20:09, Marius Dumitru Florea <[email protected]> wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release.
+1
That's a milestone, that's milestone job to introduce new things
yes I agree but not one day after the last day of the last milestone and knowing that we've reduced the RC time by 2 weeks already vs what was planned. Let's get more votes. Thanks -Vincent
and we WILL upgrade to 2.0 anyway so i don't see why not doing it now especially if all unit and integration tests pass.
Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
All unit and integration tests pass locally so here's my +1.
Thanks, Marius
Hi Marius On 01/25/2010 09:09 PM, Marius Dumitru Florea wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release. Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
you forgot to mention declarative UI: http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html#NewFeaturesUi... (youpiii!)
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
All unit and integration tests pass locally so here's my +1.
I think it should be safe, even before the 2.2M2. It's still in a milestone and if the tests pass I wouldn't expect it to go unfixable wrong. Also a + for this are the upgrade notes http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html#Upgrading which don't mention breaking api or such. So here's my +1 Thanks, Anca
Thanks, Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Marius Dumitru Florea wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release.
+0 Jerome.
Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
All unit and integration tests pass locally so here's my +1.
Thanks, Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
4 +1 1 +0 1 0 1 -0 Upgrading now. Thanks, Marius Marius Dumitru Florea wrote:
Hi devs,
I'd like to upgrade platform/web to GWT 2.0 before the 2.2M2 release. Even if the WYSIWYG users won't notice any difference (maybe a small decrease in loading time and a small increase in responsiveness dues to compiler optimizations) this upgrade will help ease the development. You can find the detailed release notes at http://code.google.com/webtoolkit/doc/latest/ReleaseNotes.html . I'm most interested in:
* ability to run the unit tests on the build server (a 32-bit JVM isn't needed anymore, finally, since the tests are run by default with HtmlUnit) * ability to run and debug the Java code directly in the browser (new development mode using a FF plugin) * ability to split the code and load it on demand
In order to upgrade I need http://google-web-toolkit-incubator.googlecode.com/files/gwt-incubator-20091... in our maven repo:
mvn install:install-file -Dfile=gwt-incubator-20091216-r1739.jar -DgroupId=com.google.gwt -DartifactId=gwt-incubator -Dversion=20091216-r1739 -Dpackaging=jar
Who can help me with that?
All unit and integration tests pass locally so here's my +1.
Thanks, Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (7)
-
Anca Luca -
Caleb James DeLisle -
Jerome Velociter -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol