> Aren't you afraid this will turn into one-man show? YES! And I'm afraid I'll be the one man again...
> Yes, yes. And then branch from that branch, and then again. Why is > the master branch needed then? Releases always come from branches. Part of doing a release is choosing where to branch from. If a point in the past is the best point, then it's the best point. Make a branch, stabilize it, release it, then go back to working on master. Master exists to be where all the work comes together. That implies that it will be in constant churn. Expecting master to always be "releasable" only works if nobody ever changes it. > And why do you resist of moving pcb onto xorn? I don't resist it per se, I just point out that there are complications because pcb's file format has issues that gschem's format doesn't. I.e. the timing is bad because we're trying to figure out what to do about the file format, and adding xorn now would either be a lot of wasted effort or the solution to our problems. Making sure we take the right path is important here. > Look, I worked on it for half a year, and had a progress. Then my plan > was to make an unstable release and let Windows users see it, then a > bug-fix release, to have a bit more stable version. Now, when geda-gaf > builds also without problems on *BSD, it would be the most appropriate > moment. But you move in an experimental stuff, making things to be in > flux again, and drive me into a corner. That sounds like a wonderful plan but I don't recall hearing about it before this. Granted, my memory's not that great, but if it was a major issue in the gaf world it should have been near the top of everyone's mind. -- Mailing list: https://launchpad.net/~geda-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~geda-developers More help : https://help.launchpad.net/ListHelp
