Smalltalk › Pharo › Pharo Smalltalk Users

SandstoneDB for Pharo maintainer?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

4 messages Options

Udo Schneider

SandstoneDB for Pharo maintainer?

All,

I noticed that the most recent SandstoneDB fails most tests when using a
disk based store. I have fixed the issue so that all tests are green
again. I'm not sure how to proceed now though.

I noticed that the StHub repository is public write. But I'm not sure if
it's okay to simply push the changes/config. So who's the current
maintainer or is there any other process?

Thanks,

Udo

Esteban A. Maringolo

Re: SandstoneDB for Pharo maintainer?

I've seen Ramon Leon active on Twitter (@ramon_leon), I don't know if
it was him who did the Pharo port, but asking him wont hurt.

Regards!

Esteban A. Maringolo

2016-06-02 13:26 GMT-03:00 Udo Schneider <[hidden email]>:

> All,
>
> I noticed that the most recent SandstoneDB fails most tests when using a
> disk based store. I have fixed the issue so that all tests are green again.
> I'm not sure how to proceed now though.
>
> I noticed that the StHub repository is public write. But I'm not sure if
> it's okay to simply push the changes/config. So who's the current maintainer
> or is there any other process?
>
> Thanks,
>
> Udo
>
>

Ramon Leon-5

Re: SandstoneDB for Pharo maintainer?

In reply to this post by Udo Schneider

On 06/02/2016 09:26 AM, Udo Schneider wrote:

> All,
>
> I noticed that the most recent SandstoneDB fails most tests when using a
> disk based store. I have fixed the issue so that all tests are green
> again. I'm not sure how to proceed now though.
>
> I noticed that the StHub repository is public write. But I'm not sure if
> it's okay to simply push the changes/config. So who's the current
> maintainer or is there any other process?
>
> Thanks,

It's open commit, feel free to commit your fixes; I'm no longer
maintaining and left it open for all.

--
Ramon Leon

Udo Schneider

Re: SandstoneDB for Pharo maintainer?

On 02/06/16 22:11, Ramon Leon wrote:
> It's open commit, feel free to commit your fixes; I'm no longer
> maintaining and left it open for all.
Will do - it's mostly only a FileReference vs. String mixup.

CU,

Udo