Re: GWT issue tracker spring cleaning

[Ed]

What means exactly "AssumedStale"?

What are the plans for issued marked as "AssumedStale"?

Idea: issue tracker glossary...

[Jens]

What are the plans for issued marked as "AssumedStale"?

If the issue owner does not respond with something like "hey this issue still exists in GWT 2.5" then this issue won't be tackled I guess. Daniel simply can't verify all the old, open issues, but the issue owner and everyone who stars the issue can do so. By marking most issues with AssumedStale you pretty much have a distributed issue verification process started ;-)

You would probably do the same if you had to cleanup thousands of old issues. You would ping every issue owner and wait for responses and then re-open issues where the issue owner tells you that this issue is still an issue.

-- J.

[Ed Bras]

BTW: Note: some issues that are marked as Stale, I am planning to pick up and submit a patch, but that will not be soon, seen my agenda. So I hope the issue will still be considered then (or is considered dead by then when no activity happens in X weeks)    ;)

On Thu, May 30, 2013 at 8:33 PM, Ed Bras <post2...@gmail.com> wrote:

Ahhhh, that explainss....

Thanks, it's difficult to understand "these thoughts" through a piece of "paper".

-- J.

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/15XXIsPI4Zc/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Ed Bras]

Ahhhh, that explainss....

Thanks, it's difficult to understand "these thoughts" through a piece of "paper".

On Thu, May 30, 2013 at 8:30 PM, Jens <jens.ne...@gmail.com> wrote:

-- J.

--

[Thomas Broyer]

On Thursday, May 30, 2013 8:36:23 PM UTC+2, Ed wrote:

BTW: Note: some issues that are marked as Stale, I am planning to pick up and submit a patch, but that will not be soon, seen my agenda. So I hope the issue will still be considered then (or is considered dead by then when no activity happens in X weeks)    ;)

As with most OSS projects, patches are welcome whether there's an issue open for them or not (opening an issue then allows for better tracking, particularly when writing the release notes).

Before working on a patch though (particularly a big one), unless you're ready to maintain a personal/private fork, you'd probably better come discuss on the gwt-contrib: if it's something that would be rejected, no need to start working on a patch and it'll save you time (that you could then dedicate to some other patch :-P )

Think of "assumed stale" as "nobody seems to really care" (historically, "assumed stale" also meant "we think it might have been fixed, please test with the latest version", but it's not that different actually: we want to close the issue and send a "signal" to anyone who cares about it; if he says it's fixed, we can change the status to Fixed, if he says he no longer care, or doesn't respond, we'll leave it as is, or maybe change the status to NotPlanned; if he says he still wants it, then we'll probably leave it closed and "ask" for a patch; when the patch comes –or the contributor says he's about to start working on it– we can change the issue status).

BTW, there's a "glossary" at https://code.google.com/p/google-web-toolkit/wiki/BugTriageProcess but it might need an update, and it doesn't talk about AssumedStale.

Maybe we should move it to gwtproject.org, patches welcome ;-)

(if you want to propose enhancements to that wiki page, feel free to come discuss it at gwt-contrib –I'm not sure comments on the wiki will notify anyone, so better use gwt-contrib–)

[Daniel Kurka]

Hi Ed,

thank you Ed for the feedback. We really like to see patches on issues that you care about. If you want to work on something we will happily review your work. As Thomas pointed out: If you want to propose a bigger patch please get in contact with gwt contributors to make sure you are heading in the right direction and your work will make it into gwt master. Some patches seem to be quite controversial and I want to make sure that we do not waste your time.

-Daniel