- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Preparing the 7.0 release (and 8.0 open), we will need to rename "development" branch to "dev-7.0"

by Esteban Lorenzano

> On 22 Nov 2018, at 12:48, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Hi, > > Why not following git flow? > Keep the development branch for dev and open a 70-release branch to prepare the release. > This way, there is no change for most people. Because our scripts are automated in branch and tag basis. dev-7.0 will generate SNAPSHOT versions for files.pharo.org/70 <http://files.pharo.org/70> and tags (v7.0.0-rc1, for example) will generate a release. We could have another flow, but this was what we decided last week and we will try it (maybe this is wrong and we will need to change it, but wellâ¦ weâll seeâ¦ good part of having a process is that we can iterate on it :P) Esteban > > Christophe > >> Le 22 nov. 2018 Ã 11:40, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : >> >> Hi list, >> >> Well, subject says pretty much all. >> We are planning to release Pharo 7.0 very soon now, and while preparing the release process, we came to the conclusion that we will need a branch for version to develop, and because of that we will need to rename what is not âdevelopmentâ to âdev-7.0â. >> Then, it will be a âdev-8.0â and so onâ¦ >> >> So, be prepared to submit your PRs to dev-7.0 instead development :) >> >> Cheers, >> Esteban > >

Nov. 22, 2018

Re: [Pharo-dev] Preparing the 7.0 release (and 8.0 open), we will need to rename "development" branch to "dev-7.0"

by Christophe Demarey

Hi, Why not following git flow? Keep the development branch for dev and open a 70-release branch to prepare the release. This way, there is no change for most people. Christophe > Le 22 nov. 2018 Ã 11:40, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > > Hi list, > > Well, subject says pretty much all. > We are planning to release Pharo 7.0 very soon now, and while preparing the release process, we came to the conclusion that we will need a branch for version to develop, and because of that we will need to rename what is not âdevelopmentâ to âdev-7.0â. > Then, it will be a âdev-8.0â and so onâ¦ > > So, be prepared to submit your PRs to dev-7.0 instead development :) > > Cheers, > Esteban

Nov. 22, 2018

Re: [Pharo-dev] Preparing the 7.0 release (and 8.0 open), we will need to rename "development" branch to "dev-7.0"

by Julien

Cool, thanks for all this work ! :-) Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 22 nov. 2018 Ã 12:00, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > > Once we open dev-8.0, yes :) > > Esteban > >> On 22 Nov 2018, at 11:51, Julien <julien.delplanque(a)inria.fr <mailto:julien.delplanque@inria.fr>> wrote: >> >> Hi, >> >> Should we submit PR concerning non-stabilisation changes (like refactoring or new features) to another branch like dev-8.0 then? >> >> Cheers, >> >> Julien >> >> --- >> Julien Delplanque >> Doctorant Ã lâUniversitÃ© de Lille >> http://juliendelplanque.be/phd.html <http://juliendelplanque.be/phd.html> >> Equipe Rmod, Inria >> BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq >> NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 >> >>> Le 22 nov. 2018 Ã 11:40, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> a Ã©crit : >>> >>> Hi list, >>> >>> Well, subject says pretty much all. >>> We are planning to release Pharo 7.0 very soon now, and while preparing the release process, we came to the conclusion that we will need a branch for version to develop, and because of that we will need to rename what is not âdevelopmentâ to âdev-7.0â. >>> Then, it will be a âdev-8.0â and so onâ¦ >>> >>> So, be prepared to submit your PRs to dev-7.0 instead development :) >>> >>> Cheers, >>> Esteban >> >

Nov. 22, 2018

Re: [Pharo-dev] Preparing the 7.0 release (and 8.0 open), we will need to rename "development" branch to "dev-7.0"

by Esteban Lorenzano

Once we open dev-8.0, yes :) Esteban > On 22 Nov 2018, at 11:51, Julien <julien.delplanque(a)inria.fr> wrote: > > Hi, > > Should we submit PR concerning non-stabilisation changes (like refactoring or new features) to another branch like dev-8.0 then? > > Cheers, > > Julien > > --- > Julien Delplanque > Doctorant Ã lâUniversitÃ© de Lille > http://juliendelplanque.be/phd.html <http://juliendelplanque.be/phd.html> > Equipe Rmod, Inria > BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq > NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > >> Le 22 nov. 2018 Ã 11:40, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> a Ã©crit : >> >> Hi list, >> >> Well, subject says pretty much all. >> We are planning to release Pharo 7.0 very soon now, and while preparing the release process, we came to the conclusion that we will need a branch for version to develop, and because of that we will need to rename what is not âdevelopmentâ to âdev-7.0â. >> Then, it will be a âdev-8.0â and so onâ¦ >> >> So, be prepared to submit your PRs to dev-7.0 instead development :) >> >> Cheers, >> Esteban >

Nov. 22, 2018

Re: [Pharo-dev] Preparing the 7.0 release (and 8.0 open), we will need to rename "development" branch to "dev-7.0"

by Julien

Hi, Should we submit PR concerning non-stabilisation changes (like refactoring or new features) to another branch like dev-8.0 then? Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 22 nov. 2018 Ã 11:40, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > > Hi list, > > Well, subject says pretty much all. > We are planning to release Pharo 7.0 very soon now, and while preparing the release process, we came to the conclusion that we will need a branch for version to develop, and because of that we will need to rename what is not âdevelopmentâ to âdev-7.0â. > Then, it will be a âdev-8.0â and so onâ¦ > > So, be prepared to submit your PRs to dev-7.0 instead development :) > > Cheers, > Esteban

Nov. 22, 2018

Preparing the 7.0 release (and 8.0 open), we will need to rename "development" branch to "dev-7.0"

by Esteban Lorenzano

Hi list, Well, subject says pretty much all. We are planning to release Pharo 7.0 very soon now, and while preparing the release process, we came to the conclusion that we will need a branch for version to develop, and because of that we will need to rename what is not âdevelopmentâ to âdev-7.0â. Then, it will be a âdev-8.0â and so onâ¦ So, be prepared to submit your PRs to dev-7.0 instead development :) Cheers, Esteban

Nov. 22, 2018

Re: [Pharo-dev] 32 vs 64 bits and large integer hash

by Marcus Denker

> On 22 Nov 2018, at 10:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 21 Nov 2018, at 19:45, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi All, >> >> right now we have the following definition of Large(Positive)Integer>>hash: >> >> hash >> ^ByteArray hashBytes: self startingWith: self species hash >> >> which means that for all integers outside of the 32-bit SmallInteger range (-2 ^ 30 to 2 ^ 30 - 1), the 32-bit system and the 64-bit system answer different values for hash. >> >> e.g. in 64 bits: (2 raisedTo: 30) hash 1073741824 >> but in 32 bits: (2 raisedTo: 30) hash 230045764 >> >> This is unsatisfactory. I propose changing Large(Positive)Integer>>hash to >> >> hash >> ^self digitLength <= 8 >> ifTrue: [self] >> ifFalse: [ByteArray hashBytes: self startingWith: self species hash] >> >> > > Thanks, I added an issue tracker entry: > > https://pharo.fogbugz.com/f/cases/22690/32-vs-64-bits-and-large-integer-hash > > I will do a pull request later (if not someone else is faster to do it). https://github.com/pharo-project/pharo/pull/2009 <https://github.com/pharo-project/pharo/pull/2009> > > -- > Marcus Denker -- marcus(a)2denker.de > http://www.zweidenker.de

Nov. 22, 2018

Re: [Pharo-dev] 32 vs 64 bits and large integer hash

by Marcus Denker

> On 21 Nov 2018, at 19:45, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > > right now we have the following definition of Large(Positive)Integer>>hash: > > hash > ^ByteArray hashBytes: self startingWith: self species hash > > which means that for all integers outside of the 32-bit SmallInteger range (-2 ^ 30 to 2 ^ 30 - 1), the 32-bit system and the 64-bit system answer different values for hash. > > e.g. in 64 bits: (2 raisedTo: 30) hash 1073741824 > but in 32 bits: (2 raisedTo: 30) hash 230045764 > > This is unsatisfactory. I propose changing Large(Positive)Integer>>hash to > > hash > ^self digitLength <= 8 > ifTrue: [self] > ifFalse: [ByteArray hashBytes: self startingWith: self species hash] > > Thanks, I added an issue tracker entry: https://pharo.fogbugz.com/f/cases/22690/32-vs-64-bits-and-large-integer-hash I will do a pull request later (if not someone else is faster to do it). Marcus -- Marcus Denker -- marcus(a)2denker.de http://www.zweidenker.de

Nov. 22, 2018

Re: [Pharo-dev] ZnCharacterReadWriteStream is missing #tab

by Sven Van Caekenberghe

Do you load from https://github.com/svenvc/zinc using the baseline ? I mostly moved to GitHub (well I try to support both). See the Travis CI build as well. > On 22 Nov 2018, at 00:17, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi Sven, > > in latest P7 I get an error when loading my Bootstrap 4 project: > > https://github.com/astares/Seaside-Bootstrap4 > > about > > MessageNotUnderstood: ZnCharacterReadWriteStream>>tab > > This is sent from STONWriter>>newlineIndent. > > To reproduce please use the following load expression: > > Metacello new > baseline:'Bootstrap4'; > repository: 'github://astares/Seaside-Bootstrap4:master/src'; > load > > > If the missing method in ZnCharacterReadWriteStream is implemented like > > tab > writeStream tab > > it works. > > As I'm constantly unclear about how Zinc (and some other externally maintained packages) > are managed now I would kindly ask you to integrate it. Thanks in advance! > > Bye > T. >

Nov. 22, 2018

Re: [Pharo-dev] [squeak-dev] Message>>#= & Message>>#hash

by Chris Muller

> That's "one should not rename classes and expect things to work", isn't > it? Not really, since that is already true anyway. If you rename a class, all references to that class will be broken.

Nov. 22, 2018