Re: Pharo-project Digest, Vol 20, Issue 286

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Pharo-project Digest, Vol 20, Issue 286

Colin Putney

On 2009-12-29, at 2:15 AM, [hidden email] wrote:

>
>> Good point. When I have a fix for OB under pharo. What is the preferred
>> ?process. So far I posted them on the bug tracker, is that okay?
>
> OB has its bug tracker at <http://code.google.com/p/omnibrowser/>.
>
> In the past people have been committing fixes to
> http://source.wiresong.ca/ob. The problem with this approach was that
> there is no control over what got integrated. People submitted changes
> to wrong packages, untested changes, changes that broke the tests,
> changes that broke the meta-model, or changes that simply broke some
> browsers. Then people merged random branches and it was not clear what
> to load, what worked and what didn't. I don't know what the take on
> this is from Colin?

Yes, we definitely need a little more process around this. I'm thinking of having a separate inbox repository where contributions can be made. Once a contribution had been tested, it would be promoted to the main repository. Ultimately, I'd like to have a robot do at least part of that - run the tests and either report test failures or promote the changes - but for now we can do it manually.

Thoughts?

Colin
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Pharo-project Digest, Vol 20, Issue 286

Stéphane Ducasse

On Dec 29, 2009, at 4:50 PM, Colin Putney wrote:

>
> On 2009-12-29, at 2:15 AM, [hidden email] wrote:
>
>>
>>> Good point. When I have a fix for OB under pharo. What is the preferred
>>> ?process. So far I posted them on the bug tracker, is that okay?
>>
>> OB has its bug tracker at <http://code.google.com/p/omnibrowser/>.
>>
>> In the past people have been committing fixes to
>> http://source.wiresong.ca/ob. The problem with this approach was that
>> there is no control over what got integrated. People submitted changes
>> to wrong packages, untested changes, changes that broke the tests,
>> changes that broke the meta-model, or changes that simply broke some
>> browsers. Then people merged random branches and it was not clear what
>> to load, what worked and what didn't. I don't know what the take on
>> this is from Colin?
>
> Yes, we definitely need a little more process around this. I'm thinking of having a separate inbox repository where contributions can be made. Once a contribution had been tested, it would be promoted to the main repository. Ultimately, I'd like to have a robot do at least part of that - run the tests and either report test failures or promote the changes - but for now we can do it manually.
>
> Thoughts?

would be cool. (I got no time to have a look at Mason).
We brainstormed with henrik or I do not remember who about the same setup for
validating packages for given version of pharo.

Colin should we reply to you in addition than to pharo?
Lukas told me that the forge refused your email because you have your own smtp.

> Colin
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Pharo-project Digest, Vol 20, Issue 286

Colin Putney

On 2009-12-29, at 8:39 AM, Stéphane Ducasse wrote:

> Colin should we reply to you in addition than to pharo?
> Lukas told me that the forge refused your email because you have your own smtp.

I got that resolved, so my email should be working normally now. I'm on the pharo list, but not following it terribly closely. If there's something you need a response to CC me directly, and I'll respond to the list.

Colin
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project