Hi, I also think we should have two repositories (one for v2 and one for v4). This way changes is the v2 code won´t cause merge conflicts for v4 code which could be annoying.
What would be the best way to ask infrastructure about this? Is it even possible to request two distinct git repositories for one project? Best Regards, Christian -----Original Message----- From: Bolz, Michael [mailto:[email protected]] Sent: Montag, 15. Juli 2013 10:12 To: [email protected] Subject: Re: Git Repository Hi, In my opinion we should try to get an additional git repository so that we have a clear separation between v2 and v4 version. Or is it final that we only get this single git repo? Perhaps till the second repository is created we can start with v2 in the already available repo. Kind regards, Michael On 15.07.13 10:06, "Klevenz, Stephan" <[email protected]> wrote: >Hi, > >Infrastructure has created a Git repository for Olingo: > >https://git-wip-us.apache.org/repos/asf/incubator-olingo.git > >Unfortunately it is not exact what we have proposed. The basic idea was >to have to repositories where one keeps the code for OData V2.0 library >and another one for future OData V4.0 development. Now we have only one >repository. > >I would like to propose the following file structure for the repository: > >root/odata2/ > - pom.xml > - /src >root/odata4/ > - pom.xml > - /src > >Basically I would like to introduce the protocol versioning on the first >level of the repository where each version has its own parent pom.xml. >With that it should be possible to develop in two tracks which can >release independently. Drawback is that each git branch will contain both >protocol versions which is sometimes unneeded. > >Maybe someone has a better idea. Or maybe having two separate >repositories is the cleaner way but the we have to ask infrastructure >again to do a change. > >WDYT? > >Regards, >Stephan
