Cleaning stale branches
We have a couple of stale branches, named a bit chaotically, I’d like to rename them in a good way, but I don’t remember what they are about :)
The numbers below (behind | ahead) are according to the current stable pharo9 branch.
- headless has already the new tree organisation with cmake
- dev-7 and pharo branches have the old tree organisation, dev-7 has some bugfixes when comparing to
pharo - Cog has the original imported version from monticello
Maybe we can have some naming convention for branches?
- pharo-[version] to denote major development version branches
- feat/[feature] for feature branches if needed
Then the four above should be renamed accordingly. Something on the lines of...
- Cog -> rename as pharo-0?
- pharo -> can be removed
- dev-7 -> pharo-1
- headless -> pharo-2
?
G
Hello,
Propositions:
- PharoX = should be the default branch (dev branch)
- Pharo9 = the current stable branch
- Cog -> I would keep cog because Pharo-0 is misleading ; it looks like
that it is the VM for Pharo Image v 0 :-) - pharo -> yes remove it
- dev-7 -> cog-pharo7 ?
- headless -> feat/headless ? to me, it is a feature branch that started on
top of cog
Luc
Le mer. 5 oct. 2022 à 10:37, Guille Polito guillermo.polito@inria.fr a
écrit :
We have a couple of stale branches, named a bit chaotically, I’d like to
rename them in a good way, but I don’t remember what they are about :)
The numbers below (behind | ahead) are according to the current stable
pharo9 branch.
- headless has already the new tree organisation with cmake
- dev-7 and pharo branches have the old tree organisation, dev-7 has some
bugfixes when comparing topharo - Cog has the original imported version from monticello
Maybe we can have some naming convention for branches?
- pharo-[version] to denote major development version branches
- feat/[feature] for feature branches if needed
Then the four above should be renamed accordingly. Something on the lines
of...
- Cog -> rename as pharo-0?
- pharo -> can be removed
- dev-7 -> pharo-1
- headless -> pharo-2
?
G
Pharo-vm mailing list -- pharo-vm@lists.pharo.org
To unsubscribe send an email to pharo-vm-leave@lists.pharo.org
Thanks Luc!
We have done some cleaning there, I hope that’s better now.
G
El 5 oct 2022, a las 15:50, Luc Fabresse luc.fabresse@imt-nord-europe.fr escribió:
Hello,
Propositions:
- PharoX = should be the default branch (dev branch)
- Pharo9 = the current stable branch
- Cog -> I would keep cog because Pharo-0 is misleading ; it looks like that it is the VM for Pharo Image v 0 :-)
- pharo -> yes remove it
- dev-7 -> cog-pharo7 ?
- headless -> feat/headless ? to me, it is a feature branch that started on top of cog
Luc
Le mer. 5 oct. 2022 à 10:37, Guille Polito <guillermo.polito@inria.fr mailto:guillermo.polito@inria.fr> a écrit :
We have a couple of stale branches, named a bit chaotically, I’d like to rename them in a good way, but I don’t remember what they are about :)
The numbers below (behind | ahead) are according to the current stable pharo9 branch.
<Gráfico_pegado-3.png>
<Gráfico_pegado-4.png>
- headless has already the new tree organisation with cmake
- dev-7 and pharo branches have the old tree organisation, dev-7 has some bugfixes when comparing to
pharo - Cog has the original imported version from monticello
Maybe we can have some naming convention for branches?
- pharo-[version] to denote major development version branches
- feat/[feature] for feature branches if needed
Then the four above should be renamed accordingly. Something on the lines of...
- Cog -> rename as pharo-0?
- pharo -> can be removed
- dev-7 -> pharo-1
- headless -> pharo-2
?
G
Pharo-vm mailing list -- pharo-vm@lists.pharo.org mailto:pharo-vm@lists.pharo.org
To unsubscribe send an email to pharo-vm-leave@lists.pharo.org mailto:pharo-vm-leave@lists.pharo.org
Pharo-vm mailing list -- pharo-vm@lists.pharo.org
To unsubscribe send an email to pharo-vm-leave@lists.pharo.org