> Recall the easrlier discussion where we talked about the "artifacts" > of the process (http://wiki.apache.org/myfaces/MyFaces_Artifacts). > Its hard to imagine a scenario where we would release a new version of > tomahawk but now release a new version of myfaces (because of the > shared code.) Those using the RI with Tomahawk, however, need only to > download the new tomahawk.jar.
Yes, that's also my feeling. Both parts (impl and tomahawk) should be released concurrently. At least for major releases. If tomahawk (for what reason ever) needs to be released separately it is the task of the release technician(s) to make sure that there are no incompatibilities to the current myfaces implementation (i.e. there where no non-trivial changes in the shared code since the last impl release). So, one step during the tomahawk release vote would be to test the tomahawk components against the last official myfaces impl. If there are problems or incompatibilities, the decision (release or not) is made by voting. Two possible results: 1. Release is done with a "disclaimer" in the release notes 2. Release of tomahawk is deferred until the next official myfaces impl I think this is a pragmatical solution taking into acount, that the shared classes are mainly common base classes that won't change every day. -Manfred
