kicad-developers team mailing list archive

[Carsten Schoenert <c.schoenert@xxxxxxxxxxx>]

Hello Orson,

Am 25.07.18 um 15:53 schrieb Maciej Sumiński:
...
> It has been discussed in this thread already, but I will repeat: the
> main problem now is that we need to apply patches to both master and
> 5.1.

thanks for clarifying (probably again).
The question will come again and again, unless it's written down to a
road map where it can be referenced to. I haven't found anything related
to this on the website and I also haven't time to follow any thread in
deep here on the ml which is more technical, but it's also interesting
for me as the person who is doing the Debian packaging where the
developing will move to and what are the plans for which release.

Why not discuss the goals which are targeted for 5.1.x (now mostly
already happen) and make this public (as a blog post on the website
e.g.)? This can be used later while developing to see how far the next
release is. I think the current development isn't that transparent
that's for sure not intended.

> This is fairly easy now, as there are no new features in the master
> branch yet, but if we merged all the feature branches then I think we
> would spend too much time resolving conflicts. There is no point nor
> manpower to develop two branches in parallel.

Sorry, I don't get this or I don't understand this really. If you say
this you will also constrain the development to only work in serial mode
like happen a decade ago while Subversion was a modern VCS and all needs
mostly done in just one branch. I don't think this is wanted as this
would mean you bothersome people who want to work on features for 6.x to
delay their work. And this is normally the last thing you wanna do.
That's part of the development projects needs to handle and deal with.
Git gives the possibility to get this managed, the only thing you need
to be clear is to know which branch needs to be merged into another.
And, yes this needs manpower to handle releases, but this needs to be
done anyway. To say there is no manpower would be a wrong thing to me,
as this has will have a huge impact just later. As I tried to express in
one of my previous emails I think it's important KiCad will get a better
policy for development and also for release planning.

All above is just my personal view and I don't want to enforce the
"real" developers to do something exactly in this way. The developers
are deciding what to do and how, so I don't want to bother any of you.

-- 
Regards
Carsten Schoenert