This has been brought up in the past (1.2 trunk), but it is again a hot topic here at oracle for applying trinidad patches.
Currently we have in SVN: https://svn.apache.org/repos/asf/myfaces/trinidad/trunk/trinidad https://svn.apache.org/repos/asf/myfaces/trinidad/branches/1.2.x-branch The problem with this structure is that there is a window between a trunk release and a branch release where there is no place for development on the 1.2 branch. Take now for example: 1.0.3 (Released) 1.0.4-SNAPSHOT (Trunk - dev) 1.2.3-SNAPSHOT (branch - pre-release) There is no 1.2.4 area for people that are making 1.0.4 changes to apply to the 1.2 branch. Would ppl. be in support of an SVN re-architecture for the following general structure? https://svn.apache.org/repos/asf/myfaces/trinidad/trunk/jsf-1.1/ (snapshot version) https://svn.apache.org/repos/asf/myfaces/trinidad/trunk/jsf-1.2/ (snapshot version) https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf-1.1/1.0.4 (created for pre-release) https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf-1.2/1.2.4 (created for pre-release) The build/api/impl folders could be directly below these folders. Example: https://svn.apache.org/repos/asf/myfaces/trinidad/trunk/jsf-1.2/trinidad-build Opinions? -Andrew
