Re: Git migration: new branch/tag naming scheme

2019-02-25 Thread Konstantin Kolinko
пн, 18 февр. 2019 г. в 11:08, Emmanuel Bourg > > Le 16/02/2019 à 16:09, Michael Osipov a écrit : > > > The given approach, for whatsoever reason, performs an uppercase and > > replaces dots with underscores. This reduces readability, but also > > requires people (esp. package maintainers) to perfo

Re: Git migration: new branch/tag naming scheme

2019-02-20 Thread Michael Osipov
Am 2019-02-20 um 17:44 schrieb Mark Thomas: On 20/02/2019 16:14, Igal Sapir wrote: Michael, On Mon, Feb 18, 2019 at 11:53 AM Michael Osipov wrote: Am 2019-02-18 um 15:19 schrieb Igal Sapir: I actually prefer "tc8.5" and "tc7.0" for the branches (over "8.5.x" and "7.0.x"). If tags will on

Re: Git migration: new branch/tag naming scheme

2019-02-20 Thread Igal Sapir
Mark, On 2/20/2019 8:44 AM, Mark Thomas wrote: On 20/02/2019 16:14, Igal Sapir wrote: Michael, On Mon, Feb 18, 2019 at 11:53 AM Michael Osipov wrote: Am 2019-02-18 um 15:19 schrieb Igal Sapir: I actually prefer "tc8.5" and "tc7.0" for the branches (over "8.5.x" and "7.0.x"). If tags wil

Re: Git migration: new branch/tag naming scheme

2019-02-20 Thread Mark Thomas
On 20/02/2019 16:14, Igal Sapir wrote: > Michael, > > On Mon, Feb 18, 2019 at 11:53 AM Michael Osipov wrote: > >> Am 2019-02-18 um 15:19 schrieb Igal Sapir: >>> >>> >>> I actually prefer "tc8.5" and "tc7.0" for the branches (over "8.5.x" and >>> "7.0.x"). If tags will only use the numeric vers

Re: Git migration: new branch/tag naming scheme

2019-02-20 Thread Igal Sapir
Michael, On Mon, Feb 18, 2019 at 11:53 AM Michael Osipov wrote: > Am 2019-02-18 um 15:19 schrieb Igal Sapir: > > > > > > I actually prefer "tc8.5" and "tc7.0" for the branches (over "8.5.x" and > > "7.0.x"). If tags will only use the numeric versions then this will make > > it easy to differen

Re: Git migration: new branch/tag naming scheme

2019-02-18 Thread Michael Osipov
Am 2019-02-18 um 15:19 schrieb Igal Sapir: On Mon, Feb 18, 2019 at 2:03 AM Mark Thomas wrote: On 18/02/2019 09:13, Rémy Maucherat wrote: On Sat, Feb 16, 2019 at 4:09 PM Michael Osipov wrote: Folks, given that we are currently in the process of migrating to Git I'd like to propose a more

Re: Git migration: new branch/tag naming scheme

2019-02-18 Thread Michael Osipov
Am 2019-02-18 um 11:03 schrieb Mark Thomas: On 18/02/2019 09:13, Rémy Maucherat wrote: On Sat, Feb 16, 2019 at 4:09 PM Michael Osipov wrote: Folks, given that we are currently in the process of migrating to Git I'd like to propose a more readible and with the branch names consistent tag nami

Re: Git migration: new branch/tag naming scheme

2019-02-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 2/18/19 05:03, Mark Thomas wrote: > On 18/02/2019 09:13, Rémy Maucherat wrote: >> On Sat, Feb 16, 2019 at 4:09 PM Michael Osipov >> wrote: >> >>> Folks, >>> >>> given that we are currently in the process of migrating to Git >>> I'd like

Re: Git migration: new branch/tag naming scheme

2019-02-18 Thread Igal Sapir
On Mon, Feb 18, 2019 at 2:03 AM Mark Thomas wrote: > On 18/02/2019 09:13, Rémy Maucherat wrote: > > On Sat, Feb 16, 2019 at 4:09 PM Michael Osipov > wrote: > > > >> Folks, > >> > >> given that we are currently in the process of migrating to Git I'd like > >> to propose a more readible and with t

Re: Git migration: new branch/tag naming scheme

2019-02-18 Thread Mark Thomas
On 18/02/2019 09:13, Rémy Maucherat wrote: > On Sat, Feb 16, 2019 at 4:09 PM Michael Osipov wrote: > >> Folks, >> >> given that we are currently in the process of migrating to Git I'd like >> to propose a more readible and with the branch names consistent tag >> naming scheme. >> >> The given app

Re: Git migration: new branch/tag naming scheme

2019-02-18 Thread Rémy Maucherat
On Sat, Feb 16, 2019 at 4:09 PM Michael Osipov wrote: > Folks, > > given that we are currently in the process of migrating to Git I'd like > to propose a more readible and with the branch names consistent tag > naming scheme. > > The given approach, for whatsoever reason, performs an uppercase an

Re: Git migration: new branch/tag naming scheme

2019-02-18 Thread Emmanuel Bourg
Le 16/02/2019 à 16:09, Michael Osipov a écrit : > The given approach, for whatsoever reason, performs an uppercase and > replaces dots with underscores. This reduces readability, but also > requires people (esp. package maintainers) to perform sed(1) magic to > convert back and forth. I agree thi

Re: Git migration: new branch/tag naming scheme

2019-02-17 Thread Igal Sapir
Michael, On Sat, Feb 16, 2019 at 7:09 AM Michael Osipov wrote: > > > There are bascially two approaches I'd like to discuss: > > Approch 1: It will reuse the branch name of the current major version, > excluding master. Thus, we will have the following prefixes: tomcat90-, > tomcat85-, and tomc

Git migration: new branch/tag naming scheme

2019-02-16 Thread Michael Osipov
Folks, given that we are currently in the process of migrating to Git I'd like to propose a more readible and with the branch names consistent tag naming scheme. The given approach, for whatsoever reason, performs an uppercase and replaces dots with underscores. This reduces readability, but