Re: One Git repo per major version

Hi Oleg On Mon, May 15, 2017 at 11:06 AM, Oleg Kalnichevski wrote: > On Mon, 2017-05-15 at 10:09 +0200, Julian Sedding wrote: >> I am in favour of using a single repository and branches (with a >> clean >> convention). Having a repo per version IMHO sends the wrong message, >>

Re: One Git repo per major version

On Mon, 2017-05-15 at 10:09 +0200, Julian Sedding wrote: > I am in favour of using a single repository and branches (with a > clean > convention). Having a repo per version IMHO sends the wrong message, > namely that the new version is completely different. > Hi Julian I believe this idea is

Re: One Git repo per major version

I am in favour of using a single repository and branches (with a clean convention). Having a repo per version IMHO sends the wrong message, namely that the new version is completely different. Again IMHO, we should strive to improve our backwards compatibility with version 6.x (with regard to

One Git repo per major version

Folks, since there is still some disagreement on how an issue should be applied to 4.4.x and 5.0.x, I'd like to propose the following two ideas: Have one repo per major version and all pain will end: httpcomponents-core-4 httpcomponents-client-4 httpcomponents-core-5 httpcomponents-client-5