Ralf Hemmecke wrote:
>
> Hi Waldek,
>
> > I think that we should merge
> > new-lambda shortly after new release -- new-lambda does not
> > add new user visible features but potentially may add new
> > bugs.
>
> I would be more in favour of merging new-lambda, when all the conversion
> is done on the branch. There are still a lot of outstanding conversions.
>
Yes, convertion should be complete before merge -- I hope this will
happen shortly after release. Simply I think that the new release
should not wait for new-lambda and even if new lambda were ready
form merge (it is not) doing merge after release is better.
> If you think that we should just synchronize new-lambda with latest
> changes from 1.0.5, then that should be easily possible using SVK
> (instead of SVN) so that the system remembers which revisions have been
> moved.
>
I think that ATM we should avoid extra changes to new-lambda --
syncing now would duplicate work which we have to do anyway
when merging.
--
Waldek Hebisch
[email protected]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/fricas-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
