Hi David I'm working on a project that involves safety and security considerations. There's just no way a product labelled 'beta' can be approved for use.
Of course, use of a product over time may be the most important way to test reliability, but that still doesn't justify use of a beta product, at least not for where I work. There being more to be added to GWT is not a reason for not producing a GA release. GWT is a vital part of the software I write - I love it, and intent using it indefinitely, but I really don't think that announcing a new release of GWT in 2014 and not having a GA version of that release in 2016 is helpful to the large community of GWT developers. It suggests that GWT is not being developed for the community, but for internal use somewhere. That's absolutely fine, as it's a free and open source project. But what I'm after is communication. If there are no plans to release GWT 2.8 or GWT 3.0 in the near future, I'll accept that and put up with it. I feel like John Cleese's character in the film 'Clockwise': "It's not the despair, [..]. I can take the despair. It's the hope I can't stand." On 18 January 2016 at 10:41, David <[email protected]> wrote: > Steve, > > Just to be clear: I'm not a contributor, I'm also working in an enterprise > environment where these kind of rules are in place. It can be frustrating, > but you cannot blame people of an opensource project that they don't work > according to the same restricting rules. > > Beta releases from GWT developers are of very high quality, Google is > actually using snapshot releases from what I read here, there is a huge > amount of unit testing, ... etc. That is what is probably holding them back > for quickly releasing new things. They need to make sure that changes do > not cause regression issues with their own software. > > Even though we are using "stable" technologies as a rule, every use case > is different and we still find bugs in products that have been used by many > projects. So the only way to be fully assured that a product is stable for > deployment is to actually use it and stress it in your environment. > > For GWT I managed to convince my managers that we should be using the > beta. If we wait until the final 2.8 and even worse if we wait until the > rest of the community has migrated then we will always run behind. From my > experience, the beta works just fine and it allows me to save a lot of time > by using Java 8 syntax but also the JsInterop 2 allows me to do things that > were previously cumbersome to do. So, I have more time to do regression > testing. > > > On Mon, Jan 18, 2016 at 9:03 AM, steve Zara <[email protected]> > wrote: > >> It's good practice for the development of commercial products which have >> to guarantee reliability and stability (as I am working on) to only use >> stable releases, and even then only after such releases have been generally >> available long enough for major bugs to have been located and fixed. >> >> I can't justify using a beta release for such development. Neither can a >> substantial number of developers. GWT is now the only development platform >> I use that forces me to stick to Java 7 syntax. After having waited for >> GWT 2.8/3.0 after their announcement over a year ago, I think my >> frustration should be understandable. >> >> So, SOME idea of when 2.8 GA might be helpful. I'd like to be able to >> use Java 8 syntax in a fully generally available and stable public release >> GWT before I retire. Or at least before the release of Java 11. I have to >> say things aren't looking hopeful for those deadlines! >> >> On Friday, 15 January 2016 09:11:53 UTC, DavidN wrote: >>> >>> What stops you from using the beta1 ? I did not yet notice any backward >>> compatibility issues. >>> >>> On Thu, Jan 14, 2016 at 12:25 PM Gilberto <[email protected]> wrote: >>> >>>> In my experience, asking for a release date of a project where there >>>> are Google folks involved, is the same as asking for peace on Middle East. >>>> >>>> They never work with strict dates, and when they say a date, it's >>>> always wrong - I wish I could do that to my customers =P >>>> >>>> The lack of communication only makes the matter worse. >>>> >>>> So, I'd say the date of the GA release is soon*™.* >>>> >>>> >>>> On Thursday, January 14, 2016 at 9:03:21 AM UTC-2, Marcin Okraszewski >>>> wrote: >>>>> >>>>> Hi, >>>>> We have hit a bug with SDM in 2.7, when we use shared CSS via >>>>> interfaces inheritance. It seems to be fixed in 2.8 beta. Therefore a >>>>> question - when can we expect GA to happen? >>>>> >>>>> Thank you, >>>>> Marcin >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "GWT Users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at https://groups.google.com/group/google-web-toolkit. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "GWT Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/google-web-toolkit. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "GWT Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-web-toolkit/UOcZ5VKmu8M/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
