Hi Michael,

This sounds very much like it should have gone into trunk /before/ going into 0.92 or 0.93.

The process is that items are merged into trunk/main and then are forked to the release branch, these forks then get merges from trunk (and rarely fixes just for that branch).

If it was working for 0.92 and still works in trunk and has been reviewed, merge it in.

The deadline is Wed 7th June, so it's practically now!

Best Regards, Martin Owens

On Sun, 2017-06-04 at 17:12 +0200, Michael Soegtrop wrote:

Dear Martin,

I am sure the answer is somewhere in the lengthy discussion on moving to git but I must admit I didn't follow it. What I need to know is what the deadline is.

The stuff was working fine in 0.92 and reviewed OK (by Jabier), it just didn't make it in time for 0.93. So all that needs to be done is merge it from 0.92 to 0.93 (or the current baseline).

There is one additional LPE in this branch which is intended for making designs for stitching machines. This is also working, but it could need some improvements in the path optimization algorithms (a TSP). But I think this can be fixed later (enable this LPE only in development builds).

Best regards,

Michael

On 04.06.2017 17:01, Martin Owens wrote:

...

Michael,

If you don't think it can be completed in the time left, then we should look for the git branch when the migration is complete. If it's not there, you may have to copy across your changes and commit them into a new branch.

But if you need help with your branch, this is a good time to ask.

Best Regards, Martin Owens

On Sun, 2017-06-04 at 14:11 +0200, Michael Soegtrop wrote:

...

Dear Martin,

I am not sure how to proceed with my bool lpe. Shoul dit be finalized in bzr until some deadline, or should I move it over somehow (manually) to git?

Best regards,

Michael