Re: [GSoC] current working status

From: Charles Cui <charles(dot)cui1984(at)gmail(dot)com>
To: Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>
Cc: Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GSoC] current working status
Date: 2018-06-15 01:16:18
Message-ID: CA+SXE9skOOg-5hA8K0xCSJ5mgdh6Bq9EWvrqE7GNokmzcfcn8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi mentors,

The repo currently can be build on my mac. You can check it out.
Also I am working on the CI config to monitor each commit.

Thanks

2018-06-14 8:29 GMT-07:00 Charles Cui <charles(dot)cui1984(at)gmail(dot)com>:

> good idea, will keep a feature branch, and set up ci.
>
> On Thu, Jun 14, 2018, 8:03 AM Aleksander Alekseeev <
> a(dot)alekseev(at)postgrespro(dot)ru> wrote:
>
>> Hello Charles,
>>
>> > I saw the list of errors you posted. That's because I have some new
>> > function implemented and pushed without testing(in order forget my
>> > change in local machine).
>> > So you are saying it is best to keep each commit workable. Right?
>>
>> Ideally, yes. You can always create a separate branch to experiment with
>> new code and merge it to master branch when it becomes stable. This is
>> not a strict GSoC requirement or something like this, but a good
>> practice. If something goes wrong you can just delete an experimental
>> branch and go back to working master branch.
>>
>>
>> --
>> Best regards,
>> Aleksander Alekseev
>>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2018-06-15 01:38:00 Re: BUG #15237: I got "ERROR: source for a multiple-column UPDATE item must be a sub-SELECT or ROW() expression"
Previous Message Amit Langote 2018-06-15 01:05:04 Re: Partitioning with temp tables is broken