Empathy List Archives

GP

Guille Polito

Wed, Oct 5, 2022 8:20 AM

Hi all,

We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository.
It’s just a convenience for dev.
Thoughts?

What should we add in the readme to make sure people do not make mistakes?

say that stable versions are in releases?
say the default branch is always dev?

cheers,
G & J

Hi all, We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository. It’s just a convenience for dev. Thoughts? What should we add in the readme to make sure people do not make mistakes? - say that stable versions are in releases? - say the default branch is always dev? cheers, G & J

NH

Norbert Hartl

Wed, Oct 5, 2022 8:26 AM

I think it is good to have the main trunk being dev. The project is about developing pharo so that says it all. Furthermore tools tend to branch of the default branch mostly. So that would avoid a lot errornous PRs I guess. Stable should always branch off and receive hotfixes.

My 2 cents,

Norbert

Am 05.10.2022 um 10:20 schrieb Guille Polito guillermo.polito@inria.fr:

Hi all,

We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository.
It’s just a convenience for dev.
Thoughts?

What should we add in the readme to make sure people do not make mistakes?

say that stable versions are in releases?
say the default branch is always dev?

cheers,
G & J

Pharo-vm mailing list -- pharo-vm@lists.pharo.org
To unsubscribe send an email to pharo-vm-leave@lists.pharo.org

I think it is good to have the main trunk being dev. The project is about developing pharo so that says it all. Furthermore tools tend to branch of the default branch mostly. So that would avoid a lot errornous PRs I guess. Stable should always branch off and receive hotfixes. My 2 cents, Norbert > Am 05.10.2022 um 10:20 schrieb Guille Polito <guillermo.polito@inria.fr>: > > Hi all, > > We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository. > It’s just a convenience for dev. > Thoughts? > > What should we add in the readme to make sure people do not make mistakes? > - say that stable versions are in releases? > - say the default branch is always dev? > > cheers, > G & J > _______________________________________________ > Pharo-vm mailing list -- pharo-vm@lists.pharo.org > To unsubscribe send an email to pharo-vm-leave@lists.pharo.org

T

tesonep@gmail.com

Wed, Oct 5, 2022 8:57 AM

I think is a good idea, go ahead

On Wed, Oct 5, 2022, 10:20 Guille Polito guillermo.polito@inria.fr wrote:

Hi all,

We were thinking here with Jean Privat that we could make the pharoX
branch (the dev branch) the default branch in the repository.
It’s just a convenience for dev.
Thoughts?

What should we add in the readme to make sure people do not make mistakes?

say that stable versions are in releases?
say the default branch is always dev?

cheers,
G & J

Pharo-vm mailing list -- pharo-vm@lists.pharo.org
To unsubscribe send an email to pharo-vm-leave@lists.pharo.org

I think is a good idea, go ahead On Wed, Oct 5, 2022, 10:20 Guille Polito <guillermo.polito@inria.fr> wrote: > Hi all, > > We were thinking here with Jean Privat that we could make the pharoX > branch (the dev branch) the default branch in the repository. > It’s just a convenience for dev. > Thoughts? > > What should we add in the readme to make sure people do not make mistakes? > - say that stable versions are in releases? > - say the default branch is always dev? > > cheers, > G & J > _______________________________________________ > Pharo-vm mailing list -- pharo-vm@lists.pharo.org > To unsubscribe send an email to pharo-vm-leave@lists.pharo.org >

LF

Luc Fabresse

Wed, Oct 5, 2022 1:21 PM

+1

--+- (default) dev - Pharo X (nowadays) --->
| |--- feature || PR ---> # will be merged in default
|--- releases --->

BTW: I wanted to do a pass on the wiki pages of the VM repo but I think I
need rights for that. do you confirm?

Cheers,
Luc

Le mer. 5 oct. 2022 à 10:58, tesonep@gmail.com tesonep@gmail.com a écrit :

I think is a good idea, go ahead

On Wed, Oct 5, 2022, 10:20 Guille Polito guillermo.polito@inria.fr
wrote:

Hi all,

We were thinking here with Jean Privat that we could make the pharoX
branch (the dev branch) the default branch in the repository.
It’s just a convenience for dev.
Thoughts?

What should we add in the readme to make sure people do not make mistakes?

say that stable versions are in releases?
say the default branch is always dev?

cheers,
G & J

Pharo-vm mailing list -- pharo-vm@lists.pharo.org
To unsubscribe send an email to pharo-vm-leave@lists.pharo.org

+1 --+- (default) dev - Pharo X (nowadays) ---> | |--- feature || PR ---> # will be merged in default |--- releases ---> BTW: I wanted to do a pass on the wiki pages of the VM repo but I think I need rights for that. do you confirm? Cheers, Luc Le mer. 5 oct. 2022 à 10:58, tesonep@gmail.com <tesonep@gmail.com> a écrit : > I think is a good idea, go ahead > > On Wed, Oct 5, 2022, 10:20 Guille Polito <guillermo.polito@inria.fr> > wrote: > >> Hi all, >> >> We were thinking here with Jean Privat that we could make the pharoX >> branch (the dev branch) the default branch in the repository. >> It’s just a convenience for dev. >> Thoughts? >> >> What should we add in the readme to make sure people do not make mistakes? >> - say that stable versions are in releases? >> - say the default branch is always dev? >> >> cheers, >> G & J >> _______________________________________________ >> Pharo-vm mailing list -- pharo-vm@lists.pharo.org >> To unsubscribe send an email to 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 >

GP

Guille Polito

Wed, Oct 5, 2022 3:10 PM

Thanks for the input! This is now done!

El 5 oct 2022, a las 15:21, Luc Fabresse luc.fabresse@imt-nord-europe.fr escribió:

+1

--+- (default) dev - Pharo X (nowadays) --->
| |--- feature || PR ---> # will be merged in default
|--- releases --->

BTW: I wanted to do a pass on the wiki pages of the VM repo but I think I need rights for that. do you confirm?

Cheers,
Luc

Le mer. 5 oct. 2022 à 10:58, tesonep@gmail.com mailto:tesonep@gmail.com <tesonep@gmail.com mailto:tesonep@gmail.com> a écrit :
I think is a good idea, go ahead

On Wed, Oct 5, 2022, 10:20 Guille Polito <guillermo.polito@inria.fr mailto:guillermo.polito@inria.fr> wrote:
Hi all,

We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository.
It’s just a convenience for dev.
Thoughts?

What should we add in the readme to make sure people do not make mistakes?

say that stable versions are in releases?
say the default branch is always dev?

cheers,
G & J

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

Thanks for the input! This is now done! > El 5 oct 2022, a las 15:21, Luc Fabresse <luc.fabresse@imt-nord-europe.fr> escribió: > > > +1 > > --+- (default) dev - Pharo X (nowadays) ---> > | |--- feature || PR ---> # will be merged in default > |--- releases ---> > > BTW: I wanted to do a pass on the wiki pages of the VM repo but I think I need rights for that. do you confirm? > > Cheers, > Luc > > Le mer. 5 oct. 2022 à 10:58, tesonep@gmail.com <mailto:tesonep@gmail.com> <tesonep@gmail.com <mailto:tesonep@gmail.com>> a écrit : > I think is a good idea, go ahead > > On Wed, Oct 5, 2022, 10:20 Guille Polito <guillermo.polito@inria.fr <mailto:guillermo.polito@inria.fr>> wrote: > Hi all, > > We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository. > It’s just a convenience for dev. > Thoughts? > > What should we add in the readme to make sure people do not make mistakes? > - say that stable versions are in releases? > - say the default branch is always dev? > > cheers, > G & J > _______________________________________________ > 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 <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

pharo-vm@lists.pharo.org

Making pharoX the default branch