Hi, Is there any intention of officially releasing Pharo 7.0.5 ? There are 18 commits after 7.0.4 https://github.com/pharo-project/pharo/compare/v7.0.4...Pharo7.0 I need the following https://github.com/pharo-project/pharo/pull/5079 which is one of the 18 commits Zinc HTTP Components is currently partially broken on Pharo 9 because #digitAt: was replaced by #byteAt: and #digitAt: is now removed. In order to fix this I could start using #byteAt: as far back as 7.0.5 and add it myself for even older Pharo versions using my Zinc-Pharo-Forward-Compatibility package. What has to happen to make it possible to release 7.0.5 ? More testing ? Where is the artefact to test ? Thx, Sven
PING: I still did not yet get any answer.
On 17 May 2020, at 12:27, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Hi,
Is there any intention of officially releasing Pharo 7.0.5 ?
There are 18 commits after 7.0.4
https://github.com/pharo-project/pharo/compare/v7.0.4...Pharo7.0
I need the following
https://github.com/pharo-project/pharo/pull/5079
which is one of the 18 commits
Zinc HTTP Components is currently partially broken on Pharo 9 because #digitAt: was replaced by #byteAt: and #digitAt: is now removed.
In order to fix this I could start using #byteAt: as far back as 7.0.5 and add it myself for even older Pharo versions using my Zinc-Pharo-Forward-Compatibility package.
What has to happen to make it possible to release 7.0.5 ? More testing ? Where is the artefact to test ?
Thx,
Sven
Hi Sven, In general, I would say Pharo 7 is not maintained anymore, but in this case I think we should have done this as last task before closing it. I will try to do a final release now (we'll see how it works, it should be an easy task but two years happened since P7 so... we will not know until we try ;) ) Esteban On dim., juin 28, 2020 at 20:32, Sven Van Caekenberghe <sven@stfx.eu> wrote:
PING: I still did not yet get any answer.
On 17 May 2020, at 12:27, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
Hi,
Is there any intention of officially releasing Pharo 7.0.5 ?
There are 18 commits after 7.0.4
<https://github.com/pharo-project/pharo/compare/v7.0.4...Pharo7.0>
I need the following
<https://github.com/pharo-project/pharo/pull/5079>
which is one of the 18 commits
Zinc HTTP Components is currently partially broken on Pharo 9 because #digitAt: was replaced by #byteAt: and #digitAt: is now removed.
In order to fix this I could start using #byteAt: as far back as 7.0.5 and add it myself for even older Pharo versions using my Zinc-Pharo-Forward-Compatibility package.
What has to happen to make it possible to release 7.0.5 ? More testing ? Where is the artefact to test ?
Thx,
Sven
OK, thanks.
On 29 Jun 2020, at 06:58, Esteban Lorenzano <estebanlm@netc.eu> wrote:
Hi Sven,
In general, I would say Pharo 7 is not maintained anymore, but in this case I think we should have done this as last task before closing it. I will try to do a final release now (we'll see how it works, it should be an easy task but two years happened since P7 so... we will not know until we try ;) )
Esteban
On dim., juin 28, 2020 at 20:32, Sven Van Caekenberghe <sven@stfx.eu> wrote:
PING: I still did not yet get any answer.
On 17 May 2020, at 12:27, Sven Van Caekenberghe <sven@stfx.eu
wrote:
Hi,
Is there any intention of officially releasing Pharo 7.0.5 ?
There are 18 commits after 7.0.4
https://github.com/pharo-project/pharo/compare/v7.0.4...Pharo7.0
I need the following
https://github.com/pharo-project/pharo/pull/5079
which is one of the 18 commits
Zinc HTTP Components is currently partially broken on Pharo 9 because #digitAt: was replaced by #byteAt: and #digitAt: is now removed.
In order to fix this I could start using #byteAt: as far back as 7.0.5 and add it myself for even older Pharo versions using my Zinc-Pharo-Forward-Compatibility package.
What has to happen to make it possible to release 7.0.5 ? More testing ? Where is the artefact to test ?
Thx,
Sven
ok, in theory... you have Pharo 7.0.5 now, as final version. Esteban On lun., juin 29, 2020 at 09:11, Sven Van Caekenberghe <sven@stfx.eu> wrote:
OK, thanks.
On 29 Jun 2020, at 06:58, Esteban Lorenzano <estebanlm@netc.eu <mailto:estebanlm@netc.eu>> wrote:
Hi Sven,
In general, I would say Pharo 7 is not maintained anymore, but in this case I think we should have done this as last task before closing it. I will try to do a final release now (we'll see how it works, it should be an easy task but two years happened since P7 so... we will not know until we try ;) )
Esteban
On dim., juin 28, 2020 at 20:32, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
PING: I still did not yet get any answer.
On 17 May 2020, at 12:27, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>
wrote:
Hi,
Is there any intention of officially releasing Pharo 7.0.5 ?
There are 18 commits after 7.0.4
<https://github.com/pharo-project/pharo/compare/v7.0.4...Pharo7.0>
I need the following
<https://github.com/pharo-project/pharo/pull/5079>
which is one of the 18 commits
Zinc HTTP Components is currently partially broken on Pharo 9 because #digitAt: was replaced by #byteAt: and #digitAt: is now removed.
In order to fix this I could start using #byteAt: as far back as 7.0.5 and add it myself for even older Pharo versions using my Zinc-Pharo-Forward-Compatibility package.
What has to happen to make it possible to release 7.0.5 ? More testing ? Where is the artefact to test ?
Thx,
Sven
And will I get that version using $ curl get.pharo.org/64/70 | bash and will that version be available in the Pharo Launcher as well ?
On 29 Jun 2020, at 10:51, Esteban Lorenzano <estebanlm@netc.eu> wrote:
ok, in theory... you have Pharo 7.0.5 now, as final version.
Esteban
On lun., juin 29, 2020 at 09:11, Sven Van Caekenberghe <sven@stfx.eu> wrote:
OK, thanks.
On 29 Jun 2020, at 06:58, Esteban Lorenzano <estebanlm@netc.eu
wrote:
Hi Sven,
In general, I would say Pharo 7 is not maintained anymore, but in this case I think we should have done this as last task before closing it. I will try to do a final release now (we'll see how it works, it should be an easy task but two years happened since P7 so... we will not know until we try ;) )
Esteban
On dim., juin 28, 2020 at 20:32, Sven Van Caekenberghe < sven@stfx.eu
wrote:
PING: I still did not yet get any answer.
On 17 May 2020, at 12:27, Sven Van Caekenberghe < sven@stfx.eu
wrote:
Hi,
Is there any intention of officially releasing Pharo 7.0.5 ?
There are 18 commits after 7.0.4
https://github.com/pharo-project/pharo/compare/v7.0.4...Pharo7.0
I need the following
https://github.com/pharo-project/pharo/pull/5079
which is one of the 18 commits
Zinc HTTP Components is currently partially broken on Pharo 9 because #digitAt: was replaced by #byteAt: and #digitAt: is now removed.
In order to fix this I could start using #byteAt: as far back as 7.0.5 and add it myself for even older Pharo versions using my Zinc-Pharo-Forward-Compatibility package.
What has to happen to make it possible to release 7.0.5 ? More testing ? Where is the artefact to test ?
Thx,
Sven
yes On lun., juin 29, 2020 at 11:05, Sven Van Caekenberghe <sven@stfx.eu> wrote:
And will I get that version using
$ curl get.pharo.org/64/70 | bash
and will that version be available in the Pharo Launcher as well ?
On 29 Jun 2020, at 10:51, Esteban Lorenzano <estebanlm@netc.eu <mailto:estebanlm@netc.eu>> wrote:
ok, in theory... you have Pharo 7.0.5 now, as final version.
Esteban
On lun., juin 29, 2020 at 09:11, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
OK, thanks.
On 29 Jun 2020, at 06:58, Esteban Lorenzano <estebanlm@netc.eu <mailto:estebanlm@netc.eu>
wrote:
Hi Sven,
In general, I would say Pharo 7 is not maintained anymore, but in this case I think we should have done this as last task before closing it. I will try to do a final release now (we'll see how it works, it should be an easy task but two years happened since P7 so... we will not know until we try ;) )
Esteban
On dim., juin 28, 2020 at 20:32, Sven Van Caekenberghe < sven@stfx.eu <mailto:sven@stfx.eu>
wrote:
PING: I still did not yet get any answer.
On 17 May 2020, at 12:27, Sven Van Caekenberghe < sven@stfx.eu <mailto:sven@stfx.eu>
wrote:
Hi,
Is there any intention of officially releasing Pharo 7.0.5 ?
There are 18 commits after 7.0.4
<https://github.com/pharo-project/pharo/compare/v7.0.4...Pharo7.0>
I need the following
<https://github.com/pharo-project/pharo/pull/5079>
which is one of the 18 commits
Zinc HTTP Components is currently partially broken on Pharo 9 because #digitAt: was replaced by #byteAt: and #digitAt: is now removed.
In order to fix this I could start using #byteAt: as far back as 7.0.5 and add it myself for even older Pharo versions using my Zinc-Pharo-Forward-Compatibility package.
What has to happen to make it possible to release 7.0.5 ? More testing ? Where is the artefact to test ?
Thx,
Sven
Thanks again, Esteban, it works well ! Travis CI picked up the latest version as well. I got one project using Integer>>#byteAt: now, https://github.com/svenvc/NeoUniversalBinaryJSON , that cleanly builds on Pharo 7, 8 and 9 using one code base: https://travis-ci.org/github/svenvc/NeoUniversalBinaryJSON Cool. I'll be moving my other projects using that method (MQTT, P3 and Zinc) in the coming days. Sven
On 29 Jun 2020, at 11:07, Esteban Lorenzano <estebanlm@netc.eu> wrote:
yes
On lun., juin 29, 2020 at 11:05, Sven Van Caekenberghe <sven@stfx.eu> wrote:
And will I get that version using
$ curl get.pharo.org/64/70 | bash
and will that version be available in the Pharo Launcher as well ?
On 29 Jun 2020, at 10:51, Esteban Lorenzano <estebanlm@netc.eu
wrote:
ok, in theory... you have Pharo 7.0.5 now, as final version.
Esteban
On lun., juin 29, 2020 at 09:11, Sven Van Caekenberghe < sven@stfx.eu
wrote:
OK, thanks.
On 29 Jun 2020, at 06:58, Esteban Lorenzano < estebanlm@netc.eu
wrote:
Hi Sven,
In general, I would say Pharo 7 is not maintained anymore, but in this case I think we should have done this as last task before closing it. I will try to do a final release now (we'll see how it works, it should be an easy task but two years happened since P7 so... we will not know until we try ;) )
Esteban
On dim., juin 28, 2020 at 20:32, Sven Van Caekenberghe <
sven@stfx.eu
wrote:
PING: I still did not yet get any answer.
On 17 May 2020, at 12:27, Sven Van Caekenberghe <
sven@stfx.eu
wrote:
Hi,
Is there any intention of officially releasing Pharo 7.0.5 ?
There are 18 commits after 7.0.4
https://github.com/pharo-project/pharo/compare/v7.0.4...Pharo7.0
I need the following
https://github.com/pharo-project/pharo/pull/5079
which is one of the 18 commits
Zinc HTTP Components is currently partially broken on Pharo 9 because #digitAt: was replaced by #byteAt: and #digitAt: is now removed.
In order to fix this I could start using #byteAt: as far back as 7.0.5 and add it myself for even older Pharo versions using my Zinc-Pharo-Forward-Compatibility package.
What has to happen to make it possible to release 7.0.5 ? More testing ? Where is the artefact to test ?
Thx,
Sven
participants (2)
-
Esteban Lorenzano -
Sven Van Caekenberghe