You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by John Fallows <jo...@gmail.com> on 2005/12/29 17:34:04 UTC
Fixing issues as a non-committer
MyFaces Devs,
I am working on http://issues.apache.org/jira/browse/MYFACES-829 for JSR-127
compliance.
What is the best way to indicate that this fix is in progress on JIRA (as a
non-committer)?
After the fix is completed, I plan to attach the patch file to the issue.
Kind Regards,
John Fallows.
--
Author Pro JSF and Ajax: Building Rich Internet Components
http://www.apress.com/book/bookDisplay.html?bID=10044
Re: Fixing issues as a non-committer
Posted by John Fallows <jo...@gmail.com>.
Thanks Sean!
On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
>
> I assigned it to myself and marked it in progress. I'm looking
> forward to the fix for this one!
>
> sean
>
> On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> > MyFaces Devs,
> >
> > I am working on
> > http://issues.apache.org/jira/browse/MYFACES-829 for
> > JSR-127 compliance.
> >
> > What is the best way to indicate that this fix is in progress on JIRA
> (as a
> > non-committer)?
> >
> > After the fix is completed, I plan to attach the patch file to the
> issue.
> >
> > Kind Regards,
> > John Fallows.
> >
> > --
> > Author Pro JSF and Ajax: Building Rich Internet Components
> > http://www.apress.com/book/bookDisplay.html?bID=10044
>
--
Author Pro JSF and Ajax: Building Rich Internet Components
http://www.apress.com/book/bookDisplay.html?bID=10044
Re: Fixing issues as a non-committer
Posted by John Fallows <jo...@gmail.com>.
+1.
This sounds like a very good plan, Sean.
Kind Regards,
John Fallows
On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
>
> It may be a while though since its not yet been released. Then there
> is the issues of convincing infra to upgrade. Certainly this feature
> makes a very compelling case to upgrade though!
>
> sean
>
> On 12/29/05, Mike Kienenberger <mk...@gmail.com> wrote:
> > Great!
> > I'm definitely +1 for treating resolved (fixed in nightly) and closed
> > (fixed in public release) differently, and I'm glad to hear it'll soon
> > be possible.
> >
> > On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
> > > Right. I'm hoping that eventually we can change that policy once the
> > > following two issues are resolved:
> > >
> > > 1.) JIRA fixes an outstanding bug/limitation where you cannot "bulk"
> > > close issues. Once that is done we could just change all resolved to
> > > closed in one step. Apparently this very popular JIRA features (198
> > > votes!) has been fixed in the upcoming release.[1]
> > >
> > > 2.) We change the notification rule so that closed issues do not
> > > result in emails (just resolved.)
> > >
> > > sean
> > >
> > > [1] http://jira.atlassian.com/browse/JRA-2427
> > >
> > > On 12/29/05, Mike Kienenberger <mk...@gmail.com> wrote:
> > > > On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
> > > > > Another example of a change I would like to see is that all users
> can
> > > > > reopen a bug that is not yet closed. We have a lot of people who
> > > > > report that a fix did not work, etc. and it would be nice to just
> > > > > reopen with comments.
> > > >
> > > > Unfortunately, that won't help since our current policy is to mark a
> > > > bug as closed whenever it's resolved.
> > > >
> > >
> >
>
--
Author Pro JSF and Ajax: Building Rich Internet Components
http://www.apress.com/book/bookDisplay.html?bID=10044
Re: Fixing issues as a non-committer
Posted by Sean Schofield <se...@gmail.com>.
It may be a while though since its not yet been released. Then there
is the issues of convincing infra to upgrade. Certainly this feature
makes a very compelling case to upgrade though!
sean
On 12/29/05, Mike Kienenberger <mk...@gmail.com> wrote:
> Great!
> I'm definitely +1 for treating resolved (fixed in nightly) and closed
> (fixed in public release) differently, and I'm glad to hear it'll soon
> be possible.
>
> On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
> > Right. I'm hoping that eventually we can change that policy once the
> > following two issues are resolved:
> >
> > 1.) JIRA fixes an outstanding bug/limitation where you cannot "bulk"
> > close issues. Once that is done we could just change all resolved to
> > closed in one step. Apparently this very popular JIRA features (198
> > votes!) has been fixed in the upcoming release.[1]
> >
> > 2.) We change the notification rule so that closed issues do not
> > result in emails (just resolved.)
> >
> > sean
> >
> > [1] http://jira.atlassian.com/browse/JRA-2427
> >
> > On 12/29/05, Mike Kienenberger <mk...@gmail.com> wrote:
> > > On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
> > > > Another example of a change I would like to see is that all users can
> > > > reopen a bug that is not yet closed. We have a lot of people who
> > > > report that a fix did not work, etc. and it would be nice to just
> > > > reopen with comments.
> > >
> > > Unfortunately, that won't help since our current policy is to mark a
> > > bug as closed whenever it's resolved.
> > >
> >
>
Re: Fixing issues as a non-committer
Posted by Mike Kienenberger <mk...@gmail.com>.
Great!
I'm definitely +1 for treating resolved (fixed in nightly) and closed
(fixed in public release) differently, and I'm glad to hear it'll soon
be possible.
On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
> Right. I'm hoping that eventually we can change that policy once the
> following two issues are resolved:
>
> 1.) JIRA fixes an outstanding bug/limitation where you cannot "bulk"
> close issues. Once that is done we could just change all resolved to
> closed in one step. Apparently this very popular JIRA features (198
> votes!) has been fixed in the upcoming release.[1]
>
> 2.) We change the notification rule so that closed issues do not
> result in emails (just resolved.)
>
> sean
>
> [1] http://jira.atlassian.com/browse/JRA-2427
>
> On 12/29/05, Mike Kienenberger <mk...@gmail.com> wrote:
> > On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
> > > Another example of a change I would like to see is that all users can
> > > reopen a bug that is not yet closed. We have a lot of people who
> > > report that a fix did not work, etc. and it would be nice to just
> > > reopen with comments.
> >
> > Unfortunately, that won't help since our current policy is to mark a
> > bug as closed whenever it's resolved.
> >
>
Re: Fixing issues as a non-committer
Posted by Sean Schofield <se...@gmail.com>.
Right. I'm hoping that eventually we can change that policy once the
following two issues are resolved:
1.) JIRA fixes an outstanding bug/limitation where you cannot "bulk"
close issues. Once that is done we could just change all resolved to
closed in one step. Apparently this very popular JIRA features (198
votes!) has been fixed in the upcoming release.[1]
2.) We change the notification rule so that closed issues do not
result in emails (just resolved.)
sean
[1] http://jira.atlassian.com/browse/JRA-2427
On 12/29/05, Mike Kienenberger <mk...@gmail.com> wrote:
> On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
> > Another example of a change I would like to see is that all users can
> > reopen a bug that is not yet closed. We have a lot of people who
> > report that a fix did not work, etc. and it would be nice to just
> > reopen with comments.
>
> Unfortunately, that won't help since our current policy is to mark a
> bug as closed whenever it's resolved.
>
Re: Fixing issues as a non-committer
Posted by Mike Kienenberger <mk...@gmail.com>.
On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
> Another example of a change I would like to see is that all users can
> reopen a bug that is not yet closed. We have a lot of people who
> report that a fix did not work, etc. and it would be nice to just
> reopen with comments.
Unfortunately, that won't help since our current policy is to mark a
bug as closed whenever it's resolved.
Re: Fixing issues as a non-committer
Posted by Matthias Wessendorf <mw...@gmail.com>.
That sounds good!
I usually mark *fixed* bugs as *resolved*.
So it is up to the QA to close them ;)
-Matthias
On 12/29/05, Sean Schofield <se...@gmail.com> wrote:
> Its probably possible. I am the alternate JIRA admin but I'm a bit
> busy at the moment. In the not too distant future I am going to
> submit a proposal to the dev list for changes to the default
> permission schemes so I will add this to my proposal.
>
> Another example of a change I would like to see is that all users can
> reopen a bug that is not yet closed. We have a lot of people who
> report that a fix did not work, etc. and it would be nice to just
> reopen with comments.
>
> sean
>
>
> On 12/29/05, Matthias Wessendorf <mw...@gmail.com> wrote:
> > I have in mind that Manfred our jira admin, but he seams to be in vaction.
> > So I have no idea.
> >
> > On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> > > Yes Matthias, I'd be interested to know the general strategy for this too.
> > >
> > > Kind Regards,
> > > John Fallows.
> > >
> > >
> > > On 12/29/05, Matthias Wessendorf <mw...@gmail.com> wrote:
> > > > > I assigned it to myself and marked it in progress. I'm looking
> > > > > forward to the fix for this one!
> > > >
> > > > maybe this issue is already taken, but is it possible to asign bugs to
> > > yourself,
> > > > even, when you are not a committer?
> > > > (have no idea on howto configure Jira.)
> > > >
> > > > -Matthias
> > > >
> > > >
> > > > > sean
> > > > >
> > > > > On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> > > > > > MyFaces Devs,
> > > > > >
> > > > > > I am working on
> > > > > > http://issues.apache.org/jira/browse/MYFACES-829 for
> > > > > > JSR-127 compliance.
> > > > > >
> > > > > > What is the best way to indicate that this fix is in progress on JIRA
> > > (as a
> > > > > > non-committer)?
> > > > > >
> > > > > > After the fix is completed, I plan to attach the patch file to the
> > > issue.
> > > > > >
> > > > > > Kind Regards,
> > > > > > John Fallows.
> > > > > >
> > > > > > --
> > > > > > Author Pro JSF and Ajax: Building Rich Internet Components
> > > > > > http://www.apress.com/book/bookDisplay.html?bID=10044
> > > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > > Zülpicher Wall 12, 239
> > > > 50674 Köln
> > > > http://www.wessendorf.net
> > > > mwessendorf-at-gmail-dot-com
> > > >
> > >
> > >
> > >
> > > --
> > >
> > > Author Pro JSF and Ajax: Building Rich Internet Components
> > > http://www.apress.com/book/bookDisplay.html?bID=10044
> >
> >
> > --
> > Matthias Wessendorf
> > Zülpicher Wall 12, 239
> > 50674 Köln
> > http://www.wessendorf.net
> > mwessendorf-at-gmail-dot-com
> >
>
--
Matthias Wessendorf
Zülpicher Wall 12, 239
50674 Köln
http://www.wessendorf.net
mwessendorf-at-gmail-dot-com
Re: Fixing issues as a non-committer
Posted by Sean Schofield <se...@gmail.com>.
Its probably possible. I am the alternate JIRA admin but I'm a bit
busy at the moment. In the not too distant future I am going to
submit a proposal to the dev list for changes to the default
permission schemes so I will add this to my proposal.
Another example of a change I would like to see is that all users can
reopen a bug that is not yet closed. We have a lot of people who
report that a fix did not work, etc. and it would be nice to just
reopen with comments.
sean
On 12/29/05, Matthias Wessendorf <mw...@gmail.com> wrote:
> I have in mind that Manfred our jira admin, but he seams to be in vaction.
> So I have no idea.
>
> On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> > Yes Matthias, I'd be interested to know the general strategy for this too.
> >
> > Kind Regards,
> > John Fallows.
> >
> >
> > On 12/29/05, Matthias Wessendorf <mw...@gmail.com> wrote:
> > > > I assigned it to myself and marked it in progress. I'm looking
> > > > forward to the fix for this one!
> > >
> > > maybe this issue is already taken, but is it possible to asign bugs to
> > yourself,
> > > even, when you are not a committer?
> > > (have no idea on howto configure Jira.)
> > >
> > > -Matthias
> > >
> > >
> > > > sean
> > > >
> > > > On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> > > > > MyFaces Devs,
> > > > >
> > > > > I am working on
> > > > > http://issues.apache.org/jira/browse/MYFACES-829 for
> > > > > JSR-127 compliance.
> > > > >
> > > > > What is the best way to indicate that this fix is in progress on JIRA
> > (as a
> > > > > non-committer)?
> > > > >
> > > > > After the fix is completed, I plan to attach the patch file to the
> > issue.
> > > > >
> > > > > Kind Regards,
> > > > > John Fallows.
> > > > >
> > > > > --
> > > > > Author Pro JSF and Ajax: Building Rich Internet Components
> > > > > http://www.apress.com/book/bookDisplay.html?bID=10044
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > > Zülpicher Wall 12, 239
> > > 50674 Köln
> > > http://www.wessendorf.net
> > > mwessendorf-at-gmail-dot-com
> > >
> >
> >
> >
> > --
> >
> > Author Pro JSF and Ajax: Building Rich Internet Components
> > http://www.apress.com/book/bookDisplay.html?bID=10044
>
>
> --
> Matthias Wessendorf
> Zülpicher Wall 12, 239
> 50674 Köln
> http://www.wessendorf.net
> mwessendorf-at-gmail-dot-com
>
Re: Fixing issues as a non-committer
Posted by Matthias Wessendorf <mw...@gmail.com>.
I have in mind that Manfred our jira admin, but he seams to be in vaction.
So I have no idea.
On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> Yes Matthias, I'd be interested to know the general strategy for this too.
>
> Kind Regards,
> John Fallows.
>
>
> On 12/29/05, Matthias Wessendorf <mw...@gmail.com> wrote:
> > > I assigned it to myself and marked it in progress. I'm looking
> > > forward to the fix for this one!
> >
> > maybe this issue is already taken, but is it possible to asign bugs to
> yourself,
> > even, when you are not a committer?
> > (have no idea on howto configure Jira.)
> >
> > -Matthias
> >
> >
> > > sean
> > >
> > > On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> > > > MyFaces Devs,
> > > >
> > > > I am working on
> > > > http://issues.apache.org/jira/browse/MYFACES-829 for
> > > > JSR-127 compliance.
> > > >
> > > > What is the best way to indicate that this fix is in progress on JIRA
> (as a
> > > > non-committer)?
> > > >
> > > > After the fix is completed, I plan to attach the patch file to the
> issue.
> > > >
> > > > Kind Regards,
> > > > John Fallows.
> > > >
> > > > --
> > > > Author Pro JSF and Ajax: Building Rich Internet Components
> > > > http://www.apress.com/book/bookDisplay.html?bID=10044
> > >
> >
> >
> > --
> > Matthias Wessendorf
> > Zülpicher Wall 12, 239
> > 50674 Köln
> > http://www.wessendorf.net
> > mwessendorf-at-gmail-dot-com
> >
>
>
>
> --
>
> Author Pro JSF and Ajax: Building Rich Internet Components
> http://www.apress.com/book/bookDisplay.html?bID=10044
--
Matthias Wessendorf
Zülpicher Wall 12, 239
50674 Köln
http://www.wessendorf.net
mwessendorf-at-gmail-dot-com
Re: Fixing issues as a non-committer
Posted by John Fallows <jo...@gmail.com>.
Yes Matthias, I'd be interested to know the general strategy for this too.
Kind Regards,
John Fallows.
On 12/29/05, Matthias Wessendorf <mw...@gmail.com> wrote:
>
> > I assigned it to myself and marked it in progress. I'm looking
> > forward to the fix for this one!
>
> maybe this issue is already taken, but is it possible to asign bugs to
> yourself,
> even, when you are not a committer?
> (have no idea on howto configure Jira.)
>
> -Matthias
>
>
> > sean
> >
> > On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> > > MyFaces Devs,
> > >
> > > I am working on
> > > http://issues.apache.org/jira/browse/MYFACES-829 for
> > > JSR-127 compliance.
> > >
> > > What is the best way to indicate that this fix is in progress on JIRA
> (as a
> > > non-committer)?
> > >
> > > After the fix is completed, I plan to attach the patch file to the
> issue.
> > >
> > > Kind Regards,
> > > John Fallows.
> > >
> > > --
> > > Author Pro JSF and Ajax: Building Rich Internet Components
> > > http://www.apress.com/book/bookDisplay.html?bID=10044
> >
>
>
> --
> Matthias Wessendorf
> Zülpicher Wall 12, 239
> 50674 Köln
> http://www.wessendorf.net
> mwessendorf-at-gmail-dot-com
>
--
Author Pro JSF and Ajax: Building Rich Internet Components
http://www.apress.com/book/bookDisplay.html?bID=10044
Re: Fixing issues as a non-committer
Posted by Matthias Wessendorf <mw...@gmail.com>.
> I assigned it to myself and marked it in progress. I'm looking
> forward to the fix for this one!
maybe this issue is already taken, but is it possible to asign bugs to yourself,
even, when you are not a committer?
(have no idea on howto configure Jira.)
-Matthias
> sean
>
> On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> > MyFaces Devs,
> >
> > I am working on
> > http://issues.apache.org/jira/browse/MYFACES-829 for
> > JSR-127 compliance.
> >
> > What is the best way to indicate that this fix is in progress on JIRA (as a
> > non-committer)?
> >
> > After the fix is completed, I plan to attach the patch file to the issue.
> >
> > Kind Regards,
> > John Fallows.
> >
> > --
> > Author Pro JSF and Ajax: Building Rich Internet Components
> > http://www.apress.com/book/bookDisplay.html?bID=10044
>
--
Matthias Wessendorf
Zülpicher Wall 12, 239
50674 Köln
http://www.wessendorf.net
mwessendorf-at-gmail-dot-com
Re: Fixing issues as a non-committer
Posted by Sean Schofield <se...@gmail.com>.
I assigned it to myself and marked it in progress. I'm looking
forward to the fix for this one!
sean
On 12/29/05, John Fallows <jo...@gmail.com> wrote:
> MyFaces Devs,
>
> I am working on
> http://issues.apache.org/jira/browse/MYFACES-829 for
> JSR-127 compliance.
>
> What is the best way to indicate that this fix is in progress on JIRA (as a
> non-committer)?
>
> After the fix is completed, I plan to attach the patch file to the issue.
>
> Kind Regards,
> John Fallows.
>
> --
> Author Pro JSF and Ajax: Building Rich Internet Components
> http://www.apress.com/book/bookDisplay.html?bID=10044