Mail Archives: geda-user/2015/09/01/13:34:50
On Tue, 1 Sep 2015, DJ Delorie wrote:
>
>> For me, the important quesiton is whether the changes put in such a
>> branch gets into the next release - or is left in a feature branch
>> to bit rot.
>
> Changes put in a separate repo will surely not get into any release,
> unless they make it to the main repo first. What ends up in the next
> release is up to the people willing to put in the work to make a
> release.
>
> Using the main repo for side projects at least keeps all the work in
> one place that everyone knows about, and thus less likely to be lost
> in the shuffle.
Thanx, these were all clear to me. Having the stuff in mainline is one of
the local optimums. There are other local optimums, tho. And there are
suboptimal points that combine the drawbacks of different solutions, like
git + not having the stuff merged in mainline.
Before I make my decision, I really want to see the chances of getting an
optimal solution vs. wasting time. This why I want to see, before I start
in any direction, whether my ideas are backed up by mainline maintainers.
>
>> So what do you, gschem maintainers, think about the gschem-related points
>> of my proposal?
>
> For the record, I don't consider myself a gschem maintainer. For
> not-pcb I just keep the server running.
>
Clear, I meant the "you" part in general. I am not sure who exactly are
maintaining gschem nowdays. I have some guesses, but those guys did not
comment any of the back annotation threads.
Regards,
Igor2
- Raw text -