Smalltalk › Pharo › Pharo Smalltalk Users

Slice for a non Pharo package ?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Matthieu

Slice for a non Pharo package ?

Hello,

I reported a bug on Athens here : https://pharo.fogbugz.com/f/cases/15640/

I also created a slice to solve it by following the Pharo fogbugz video tutorial.

But then I realized that Athens is not present in Pharo/main so it would not make sense to commit the slice into the Pharo Inbox.

What is the procedure to propose a Slice for a package outside Pharo/main ?

Sorry if it's a dumb question :s

Cheers,

Matthieu

Sergio Fedi

Re: Slice for a non Pharo package ?

Don't worry about the question.

I'm interested in this too.

Nicolai Hess

Re: Slice for a non Pharo package ?

In reply to this post by Matthieu

I or one of the other athens maintainer can include the

fix in the athens repository and

create a new configuration for integration in the main image.

2015-05-30 12:47 GMT+02:00 Matthieu Lacaton <[hidden email]>:

Hello,

I reported a bug on Athens here : https://pharo.fogbugz.com/f/cases/15640/

I also created a slice to solve it by following the Pharo fogbugz video tutorial.
But then I realized that Athens is not present in Pharo/main so it would not make sense to commit the slice into the Pharo Inbox.

What is the procedure to propose a Slice for a package outside Pharo/main ?

Sorry if it's a dumb question :s

Cheers,

Matthieu

CyrilFerlicot

Re: Slice for a non Pharo package ?

Hi, Marcus told me that the procedure was:
- You open an issue about a non Pharo package.
- You do your changes
- You save your changes on the project's smalltalkhub (For example
www.smalltalkhub.com/#!/~Pharo/Athens/main, and if you don't have the
right send a mail on the mailing list to have them)
- You resolve the case on foxbugz
and you put the case in "Resolved (Fixed upstream)"

When your changes will be merge and a new configurationOf will be
created Marcus will close the issue.

On 30 May 2015 at 13:46, Nicolai Hess <[hidden email]> wrote:

> I or one of the other athens maintainer can include the
> fix in the athens repository and
> create a new configuration for integration in the main image.
>
>
> 2015-05-30 12:47 GMT+02:00 Matthieu Lacaton <[hidden email]>:
>>
>> Hello,
>>
>> I reported a bug on Athens here : https://pharo.fogbugz.com/f/cases/15640/
>>
>> I also created a slice to solve it by following the Pharo fogbugz video
>> tutorial.
>> But then I realized that Athens is not present in Pharo/main so it would
>> not make sense to commit the slice into the Pharo Inbox.
>>
>> What is the procedure to propose a Slice for a package outside Pharo/main
>> ?
>>
>> Sorry if it's a dumb question :s
>>
>> Cheers,
>>
>> Matthieu
>
>

--
Cheers
Cyril Ferlicot

Sean P. DeNigris

Re: Slice for a non Pharo package ?

Administrator

jecisc wrote

- You save your changes on the project's smalltalkhub...
[INSERT HERE]
- You resolve the case on foxbugz
and you put the case in "Resolved (Fixed upstream)"

I would add above: create a new configuration yourself and copy it to the Inbox. When you resolve the issue in Fogbugz, add the configuration info to the issue (there are dedicated fields for this). This way, the monkey will pick up and validate your changes just like with a slice.

Cheers,
Sean