On Sun, Jul 3, 2016 at 7:25 PM, Bernhard Pieber <bernh...@pieber.com> wrote:
> Done!

Thanks Bernhard, but I can't find the issue in the tracker. Can you
paste a link?


On Sun, Jul 3, 2016 at 7:41 PM, Bernhard Pieber <bernh...@pieber.com> wrote:
> I wonder about the process for fixes for Pharo 4.0? Is it the same? If I’d 
> put the equivalent fix into the Pharo40Inbox, would it be integrated?

I am not familiar with the release process, but apparently there is a
fair amount of manual work to do each release.  Typically it seems
each major release is followed by one minor point release about 6
months later.  So 4.0 is probably too far back for another release.

It would be good however if there was some community process to manage
fixes for very old releases.  Perhaps there could be a tag like
"Pharo4-hotfix" in Fogbugz, so users of their own accord could search
for community fixes contributed long after the main development focus
has moved on - to be used at own risk.  This might provide better
sustainability for older releases without drawing resources from the
latest version.  That is, Pharo 4.0 users would need to rely on review
by other Pharo 4.0 user to review and promote their fixes to "hotfix"
- but at least the Fogbugz facilitates the collaboration.  This might
also work for 5.0 fixes as a state between Work Needed and Closed Fix
Integrated while they are waiting to be rolled up into the point
release.

cheers -ben

>
> Cheers,
> Bernhard
>
>> Am 03.07.2016 um 08:46 schrieb stepharo <steph...@free.fr>:
>>
>> Thanks Bernhard
>>
>> - can you open a bug entry?
>>
>> - publish a slice? (press slice + bug number)
>>
>> Our integration tool and process work this way
>>
>> Stef
>>
>> Le 2/7/16 à 21:16, Bernhard Pieber a écrit :
>>> Hi,
>>>
>>> The following code goes into an endless loop:
>>> MailAddressParser addressesIn: 'romeo&ju...@verona.it‘
>>>
>>> It’s because of the ampersand. The fix is trivial, because the bug just was 
>>> a typo.
>>>
>>> Fix and test are in the Pharo50Inbox:
>>> Network-Mail-BernhardPieber.46.mcz
>>> Network-Tests-BernhardPieber.14.mcz
>
>

Reply via email to