I would say either
http://myfaces.apache.org/wiki/core/faq.html
or under
http://myfaces.apache.org/wiki/core/committer-and-pmc-guide.html
possibly at the bottom of the following page under Issue Tracker guidelines
all right!
Added it:
http://myfaces.apache.org/wiki/core/committer-and-pmc-guide/myfaces-project-management.html
Will start with the first issues this week.
2015-08-26 20:05 GMT+02:00 Mike Kienenberger mkien...@gmail.com:
I would say either
http://myfaces.apache.org/wiki/core/faq.html
or
Would you add it as a FAQ item or a as a new page?
2015-08-21 17:23 GMT+02:00 Mike Kienenberger mkien...@gmail.com:
I don't know how they are used but they sound like they might fit what
we want to do.
On Fri, Aug 21, 2015 at 5:40 AM, Dennis Kieselhorst m...@dekies.de
wrote:
We should
Sure, let's start in the wiki.
It should probably be in a more permanent place, but there's a FAQ
item I have posted into issues already in the wiki somewhere, so
that's probably a good starting place for this one too.
On Fri, Aug 21, 2015 at 3:18 AM, Thomas Andraschko
I don't know how they are used but they sound like they might fit what
we want to do.
On Fri, Aug 21, 2015 at 5:40 AM, Dennis Kieselhorst m...@dekies.de wrote:
We should probably document our policy of closing issues somewhere and
refer that that policy in each comment.
- Issues older than 5
We should probably document our policy of closing issues somewhere and
refer that that policy in each comment.
- Issues older than 5 years are closed.
- Issues needing reporter feedback are closed after 1 year
- Enhancement/improvement Issues without a patch for maintenance mode
branches
I could also post it in every issue, would be no problem :)
2015-08-21 9:18 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com:
sounds good!
Probably in the wiki or somewhere?
2015-08-20 22:31 GMT+02:00 Mike Kienenberger mkien...@gmail.com:
We should probably document our policy of
sounds good!
Probably in the wiki or somewhere?
2015-08-20 22:31 GMT+02:00 Mike Kienenberger mkien...@gmail.com:
We should probably document our policy of closing issues somewhere and
refer that that policy in each comment.
- Issues older than 5 years are closed.
- Issues needing reporter
Hi,
i would invest some hours to do a big cleanup of our issue tracker.
There are tickets available which are 10 years old!
I think such a cleanup is really required. AFAIR mojarra did the same some
months ago.
I would do the following:
1) Close every issue older than 2010. The most issues
+1
regards,
gerhard
2015-08-20 11:00 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com:
Hi,
i would invest some hours to do a big cleanup of our issue tracker.
There are tickets available which are 10 years old!
I think such a cleanup is really required. AFAIR mojarra did the same
2) i think about something like allow pluggable seralization mechansim, i
think thats enough to add such improvements to 2.2. i also use 2.1 and im
actually very happy with it.
4) that would be issues where devs asked for more details and the creator
didnt provided more details.
5) is a little
We should probably document our policy of closing issues somewhere and
refer that that policy in each comment.
- Issues older than 5 years are closed.
- Issues needing reporter feedback are closed after 1 year
- Enhancement/improvement Issues without a patch for maintenance mode
branches are
4) i would probably close every ticket without feedback since 1 year.
I will do 1-4 first, lets check 5) afterwards.
Am Donnerstag, 20. August 2015 schrieb Mike Kienenberger :
One more comment on 5). I've found that if I specifically ask for a
patch that the reporter often submits one. So
On Thu, Aug 20, 2015 at 3:58 PM, Thomas Andraschko
andraschko.tho...@gmail.com wrote:
4) that would be issues where devs asked for more details and the creator
didnt provided more details.
Yes, that seems reasonable, although we have to decide on a policy for
how long we should wait.
5)
One more comment on 5). I've found that if I specifically ask for a
patch that the reporter often submits one. So I'd prefer we try that
approach first. In fact, we should get in the habit of doing so as
soon as we first read an issue to encourage reporters to become
involved in scratching their
Thanks for looking into this!
Comments in line.
On Thu, Aug 20, 2015 at 5:00 AM, Thomas Andraschko
andraschko.tho...@gmail.com wrote:
3) Close improvements/enhancements tickets without a patch which targets 1.x
- 2.1 (e.g. https://issues.apache.org/jira/browse/MYFACES-3402)
MyFaces still
16 matches
Mail list logo
