[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GSoc 2016: Final Reviews required
From: |
Juan Pablo Carbajal |
Subject: |
Re: GSoc 2016: Final Reviews required |
Date: |
Sun, 21 Aug 2016 22:25:32 +0200 |
On Sun, Aug 21, 2016 at 11:35 AM, PhilipNienhuis <address@hidden> wrote:
> JuanPi, how would you like development to proceed further?
> Amr has finished his work but polishing the code for error checks etc. is
> still required. Such (input) error checks do not look very difficult and can
> be copied from other code in octave.
> The error catching (= avoiding crashes) is probably more challenging.
Hi,
I will keep apologizing for my lack of reaction.
I think the best is to merge with geometry asap (there is also APi
issues to solve) and continue fixing from there on.
I could make a bitbucket repo to ease the merging, or somebody with
push rights to SF could do it, if the time is pressing and you can't
wait for a window in my schedule.
Cheers
- GSoc 2016: Final Reviews required, Amr Mohamed, 2016/08/17
- Re: GSoc 2016: Final Reviews required, PhilipNienhuis, 2016/08/19
- Re: GSoc 2016: Final Reviews required, AMR_KELEG, 2016/08/20
- Re: GSoc 2016: Final Reviews required, John Swensen, 2016/08/20
- Re: GSoc 2016: Final Reviews required, PhilipNienhuis, 2016/08/21
- Re: GSoc 2016: Final Reviews required, PhilipNienhuis, 2016/08/21
- Re: GSoc 2016: Final Reviews required,
Juan Pablo Carbajal <=
- Re: GSoc 2016: Final Reviews required, Philip Nienhuis, 2016/08/22
- Re: GSoc 2016: Final Reviews required, John Swensen, 2016/08/22
- Re: GSoc 2016: Final Reviews required, Juan Pablo Carbajal, 2016/08/23