On Friday, October 14, 2011 11:32:26 PM UTC+2, Jens wrote:
Just assigning someone to a patch so it gets recognized (and later maybe
reassigned) somehow doesn't feel right to me. I think its definitely better
if the community can see who is active in the development team and who would
be
That is good advice. In addition to the active GWT development team, there
is a fairly large group of ex-GWT team members who are still committers on
the project and working on it during their Google 20% time. If you happen to
pick the wrong person, we should be able to correct it quickly.
--
Providing your own patches doesn't guarantee it will get looked at...
I submitted the following patch because it was a simple and quick
first attempt at recommending a patch for GWT:
http://code.google.com/p/google-web-toolkit/issues/detail?id=6589
The patch got no attention from the GWT team,
Patches should be submitted to http://gwt-code-reviews.appspot.com where, if
you set reviewers, they will show in their reviewable by me (and they'll
receive a mail).
As for your patch, a single JSNI method is faster in DevMode, because it
only requires one roundtrip to the browser to execute
It was somewhat of a coincidence as we were starting a small project to
clean up and triage the issue tracker (which had been unfortunately
neglected for awhile). We definitely took notice of your post and looked at
each of the issues you referenced.
PatchesWelcome does indeed mean that we
As you now have your small clean up project phase it might be a good time to
update the duties column
in http://code.google.com/p/google-web-toolkit/people/list or create a
similar list as wiki page to help the community to decide which persons
should be assigned for reviewing patches in
It seems that after my post there started a tidying up of issues. Most of
them turned to PatchesWelcome, even those trivial to implement. Also my
newly reported issues turn to PatchesWelcome. Does it mean that GWT
developer team will not implement it and waits for GWT users to do it? Or
does
On Tuesday, October 11, 2011 6:01:01 PM UTC+2, Martin Ždila wrote:
It seems that after my post there started a tidying up of issues.
That's right (though I don't know whether it's because of your post, or they
just coincidentally happened at about the same time)
Most of them turned to
I'd recommend trying to provide your own patches. GWT is a community effort
and as such it needs more than just the support of google. You'll almost
certianly learn something in the process aswell, so it really is win/win.
--
You received this message because you are subscribed to the Google
*Marking something as PatchesWelcome means that we do think it is a good
idea, but it ls likely not something we are going to do ourselves any time
soon. We will, however, happily accept, review, and integrate high quality
patches that implement this behavior. Issue 6401 is a perfect example of
I have been frustrated with this as well and voiced my concern before. But
all they keep on doing is adding features that most of us don't need.
GWT is great, but there is a lot of old stuff in there that is half baked
and nobody in the GWT team seems to be concerned with actually fixing bugs.
Some time ago I stepped into the issue lifecycle wiki page.
http://code.google.com/p/google-web-toolkit/wiki/BugTriageProcess
http://code.google.com/p/google-web-toolkit/wiki/ManagingMerges
Maybe this can clarify some things about why issues are not updated
(looks like most of times this is an
Hello
GWT is a perfect toolkit but there are still many small but frustrating
issues open in bug-tracker and GWT developer team seems to be ignoring them
for many months or even years. GWT issues seems not to be maintained very
well as there are many of them not closed but are already fixed in
+1
04.10.2011 12:40 пользователь Martin Ždila m.zd...@gmail.com написал:
Hello
GWT is a perfect toolkit but there are still many small but frustrating
issues open in bug-tracker and GWT developer team seems to be ignoring
them
for many months or even years. GWT issues seems not to be
+1
2011/10/4 Stanislav Ievlev stanislav.iev...@gmail.com
+1
04.10.2011 12:40 пользователь Martin Ždila m.zd...@gmail.com написал:
Hello
GWT is a perfect toolkit but there are still many small but frustrating
issues open in bug-tracker and GWT developer team seems to be ignoring
them
15 matches
Mail list logo
