Thanks for the Information! I also like the Idea of having a single "Enhancing PPRPanelGroup" issue. But I'll put not all of the suggestions in there to be sure I'll be able to finish them within reasonable time ( weeks ). And also because, there are some points for which I don't have any Ideas how to implement them yet. Also some of them will probably need to be discussed like for instance the Client-Side State saving.
however, thanks for the support kind regards Ernst On 8/28/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
On 8/26/06, Ernst Fastl <[EMAIL PROTECTED]> wrote: > If I understood the recent discussions correctly we should > create JIRA Issues seperately for every change we want to make > rather than Issues like "Enhancing component x". No, that's not really what's being said. Every change should be associated with a Jira issue, but a jira issue can be associated with many changes, as long as it's reasonable :-) I'd say that "Enhancing component x" is fine as a single jira issue provided that all of these changes are going to be made within the same period of time. What we don't want to do is have code changes without jira issues (that's the biggest problem), nor do we want to have never-ending jira issues that can't be closed because they cover too many tasks. > Should I add them to "MyFaces Tomahawk - New Component" or is > it possible to create the PPRPanelGroup as a component in JIRA ? I'll create PPRPanelGroup for you. Until someone creates a new component entry, I think using "new component" makes the most sense. > Since this are a lot of changes I will probably not be > able to fix all of them before the next release. Is creating > the JIRA issues now in conflict with the release policy > if they are not fixed befor the next release? For improvements, I'd say as long as you're planning to work on them, go ahead and create the issues. Just set the fix version to be the newest snapshot. Considering the next release is probably months away, it's unlikely to be problem in any case.
