[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Octave Forge] Octave 4.0 call for packages
From: |
Sebastian Schoeps |
Subject: |
Re: [Octave Forge] Octave 4.0 call for packages |
Date: |
Thu, 16 Apr 2015 19:03:30 +0200 |
> Am 16.04.2015 um 18:21 schrieb c. <address@hidden>:
>
>
>> On 14 Apr 2015, at 17:52, Sebastian Schöps <address@hidden> wrote:
>>
>>
>>>> Am 14.04.2015 um 13:28 schrieb c. <address@hidden>:
>>>> I actually thought you and KaKiLa were unofficially maintaining odepkg
>>>> and mentoring those students, since you were the only one to reply to
>>>> the students on the mailing list.
>> Jacopo's and and my office are in the same building thus we typically
>> discuss IRL.
>>
>>> Sebastian is jacopo's phd and socis supervisor so it's jacopo who is
>>> actually pushing the changes. If you prefer to give access to jacopo I
>>> think that is also a good idea, actually my preferred solution would be :
>>>
>>> 1) give push access to both jacopo and sebastian
>>> 2) merge bitbucket repo into OF
>>> 3) shut down the bitbucket repo and carry out all work on OF
>>>
>>> c.
>> can we agree on that? If yes, Jacopo and I will take care about the next
>> steps.
>>
>> Sebastian
>
> While we wait for permissions to be set correctly,
>
> I just pushed a changeset on OF to merge the changes
> from bitbucket and those on OF.
>
> Could you all please rebase any changesets being discussed
> on the patch tracker so that they apply to the current
> head in OF?
>
> I'll now look in the tracker to get an idea of all changes
> happening there.
I am not sure if this is the best way to proceed since the latest changes in
bitbucket have increased compatibility with Matlab but therefore break backward
compatibility with previous versions of odepkg (e.g. odeset, -get have slightly
different syntax).
I suggest for now a minor version bump that fixes only octave 4.0 compatibility
and then make a proper new mayor release (0.9?) when odeXY and odeget/odeset
are in octave core (probably with the 4.1 dev branch).
Sebastian
- Re: [Octave Forge] Octave 4.0 call for packages, (continued)
- Re: [Octave Forge] Octave 4.0 call for packages, Tatsuro MATSUOKA, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Sebastian Schöps, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages,
Sebastian Schoeps <=
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, Jacopo Corno, 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Sebastian Schoeps, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
Re: Re: [Octave Forge] Octave 4.0 call for packages, Tatsuro MATSUOKA, 2015/04/11