Re: [Octave Forge] Octave 4.0 call for packages

[c.]

On 16 Apr 2015, at 19:03, Sebastian Schoeps <address@hidden> wrote:

>> 
>> 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

It's OK for me either if you want to make an intermediate backward-compatible 
release or go directly
to the new version, but in the end the matlab-compatible functions should be 
preferred.

After all Matlab incompatibilities are considered as bugs so the current 
version can be considered buggy.

If you want to make the intermediate backward-compatible release I suggest you 
create a branch in the repository
at the following changeset :

changeset:   491:883ebfb8c5df
user:        Juan Pablo Carbajal <address@hidden>
date:        Tue Mar 04 09:41:27 2014 +0100
summary:     maint: applying Mike Miller's patches to .diff files

and apply any remaining changes for 4.0 compatibility there.
After the release you can then merge and close the branch.

c.