Re: [Pharo-dev] Zinc HTTP Components version 3.0.1

[Norbert Hartl]

Great That removes a decent disruption we had. Thank you very much!

Norbert

> Am 22.11.2018 um 21:55 schrieb Sven Van Caekenberghe :
> 
> I finally merged and synced all Zinc HTTP Components repos and did a full 
> release on Pharo versions 3 to 7.
> 
>  https://github.com/svenvc/zinc/releases/tag/v3.0.1
> 
> Main README was updated
> 
>  https://github.com/svenvc/zinc
> 
> Green build for Pharo 7 RC1 (linux 64-bit) using BaselineOfZincHTTPComponents
> 
>  https://travis-ci.org/svenvc/zinc
> 
> Green builds for Pharo 3, 4, 5 and 6 using ConfigurationOfZincHTTPComponents 
> (#stable 3.0.1)
> 
>  https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/
> 
> If there are any problems or issues, don't hesitate to ask.
> 
> Sven
> 
> 
> 
> 

[Pharo-dev] Zinc HTTP Components version 3.0.1

[Sven Van Caekenberghe]

I finally merged and synced all Zinc HTTP Components repos and did a full 
release on Pharo versions 3 to 7.

  https://github.com/svenvc/zinc/releases/tag/v3.0.1

Main README was updated

  https://github.com/svenvc/zinc

Green build for Pharo 7 RC1 (linux 64-bit) using BaselineOfZincHTTPComponents

  https://travis-ci.org/svenvc/zinc

Green builds for Pharo 3, 4, 5 and 6 using ConfigurationOfZincHTTPComponents 
(#stable 3.0.1)

  https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/

If there are any problems or issues, don't hesitate to ask.

Sven

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

[Christophe Demarey]

> Le 22 nov. 2018 à 13:25, Esteban Lorenzano  a écrit :
> 
>> On 22 Nov 2018, at 13:21, Esteban Lorenzano > > wrote:
>> 
>>> On 22 Nov 2018, at 12:48, Christophe Demarey >> > 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 
>>  and tags (v7.0.0-rc1, for example) will generate 
>> a release.

maybe not for now but we can update the scripts to check:
- master branch => release (only release tags there)
- development branch => snapshot
- release branch => snapshots or realease (rcx) if a tag is defined
- all other branches => do nothing

>> 
>> 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)
> 
> Btw, I’m not complete happy with this either: as it is previewed now, there 
> will not be stable branch, and I feel this is incorrect. But again… good 
> thing is we can iterate, we’ll see if this works.

we could use the master branch for that =>  commits to master are only merges 
from release branches and hotfix branches.

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

[Esteban Lorenzano]

> On 22 Nov 2018, at 13:21, Esteban Lorenzano  wrote:
> 
> 
> 
>> On 22 Nov 2018, at 12:48, Christophe Demarey > > 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 
>  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)

Btw, I’m not complete happy with this either: as it is previewed now, there 
will not be stable branch, and I feel this is incorrect. But again… good thing 
is we can iterate, we’ll see if this works.

Esteban

> 
> Esteban
> 
>> 
>> Christophe
>> 
>>> Le 22 nov. 2018 à 11:40, Esteban Lorenzano >> > 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
>> 
>> 
> 

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

[Esteban Lorenzano]

> On 22 Nov 2018, at 12:48, Christophe Demarey  
> 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 
 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  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
> 
> 

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

[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  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

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

[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  a écrit :
> 
> Once we open dev-8.0, yes :)
> 
> Esteban
> 
>> On 22 Nov 2018, at 11:51, Julien > > 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 
>> 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 >> > 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
>> 
> 

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

[Esteban Lorenzano]

Once we open dev-8.0, yes :)

Esteban

> On 22 Nov 2018, at 11:51, Julien  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 
> 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 > > 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
> 

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

[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  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

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

[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

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

[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  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.
>