Hi Michael, See inline.
Regards, ~ Simon On Tue, Feb 24, 2009 at 3:38 PM, Michael Concini <[email protected]> wrote: > Now that the JSF 2.0 spec is getting closer to completion, I think it > would be a good idea for some more planning to go into the development > process for the MyFaces 2.0 release going forward. There are several > aspects of this that need to be addressed. > > First, regarding the changes/additions to the JSF spec. Is anyone keeping > track somewhere of which changes have JIRA issues attached versus those that > still need to have new issues created? It is getting to be hard to > determine what changes might still not have issues attached at this point as > the number of JIRA issues associated with the 2.0 spec approaches 200. > The tickets matching the public review are all created. I'll do another roundtrip with my team when the final spec is released to create the missing ones. Basically Werner is working on the JavaScript API, Leonardo and Jan-Kees help in various areas, I'm currently working on integrating Facelets and my teammate are helping me with that. One MAJOR issue that we have right now are unit tests. Leonardo proposed to attack that one, but since Shale might change his mind about the future of Shale-test, I asked him to postpone dealing with it just in case so that we don't have to work on that issue for nothing. > > > Second, I think it would be very helpful to put together a more detailed > road map of when we want to target specific changes and features. I think a > good example of how we might want to do this is what OpenWebBeans is doing in > their road > map<https://issues.apache.org/jira/secure/BrowseProject.jspa?id=12310844&subset=-1>. > They've outlined exactly what is being planned for the upcoming milestone > work. I know something like this would be very useful to my team at IBM in > determining which work is best for us to take on in any milestone period. > I don't know if milestones are relevant when implementing a spec considering what has to be done is fixed and static. I don't see any release coming not passing the TCK, thus not implementing everything needed. > > > I also think it would be a good idea to come up with a more formal way of > keeping track of who is working on which items. As more folks become > involved, its going to become more and more likely that we'll step on each > other's toes. > I agree, but JIRA only allows to assign ticket to commiters and I don't have anything better than adding a comment to the ticket for now. If you have a better idea it would be welcome. > > > Does anyone have thoughts on any of the above? I'd be glad to work with > someone from the PMC to assist in any of the required planning. > > Thanks, > Mike Concini >
