geda-developers team mailing list archive

[Ivan Stankovic <pokemon@xxxxxxxxxxxxxx>]

On Thu, Sep 17, 2015 at 10:33:38AM +0300, Vladimir Zhbanov wrote:
> > > 2. because it breaks my release plans (I've been thinking of a new
> > >    release as is ASAP, and then a bug-fix release)
> > 
> > Branch from just before the xorn integration, then.  I think that
> > until we have a solid development schedule, we're going to have to
> > risk things happening "not when convenient".
>
> Yes, yes. And then branch from that branch, and then again. Why is
> the master branch needed then?

I'm not a fan of numerous branches either, but maybe in this case
the situation would not be that bad?  Maybe one could keep xorn
on a branch until the integration problems get fixed up?

> > Heh, if we waited until all the windows "complications" were resolved,
> > we'd never release anything ;-)
> 
> 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.

I don't think that's fair to DJ.  FWIW, I tend to agree with him, there
won't be any progress unless *something* is done.  Whether something
is good or bad in the end may not be obvious.  Personally, I haven't
tried xorn but am willing to try.  I guess there are other people as well.
Making it more easy for people to try it out and see for themselves
will improve the kind of feedback we get on the -user list.

Also, if you've got a release ready already, just do it, without xorn.  I
certainly do not see any technical problems standing in the way.

And by the way, the very fact that there is a discussion on the -dev list again
makes me optimistic.

-- 
Ivan Stankovic, pokemon@xxxxxxxxxxxxxx

"Protect your digital freedom and privacy, eliminate DRM, 
learn more at http://www.defectivebydesign.org/what_is_drm";