Is the reason people want to skip to v= ersion 4 just because of that fork that claimed version 3.x? If so, we coul= d still use the 2.x.x series before having to worry about the naming collis= ion, and then skip to 4.0.0. Or is it that we want to tell prospective user= s that ours is better by having a higher version number?

DJ-
I agree that there haven't been any changes that would break backward= compatibility, but sometimes you just have to make a clean break, like whe= n the kernel went to 3.0.0.

Bert-

Thanks, I can be a = little OCD sometimes, and I do like things to be neat and clean! Particular= ly when it comes to plans.

I sort of assumed that we would either h= ave the code sprint earlier, or not have one this month since the last Sund= ay of the month (tomorrow) is Christmas day and I imagine that a lot of peo= ple will be observing that holiday.

I'll run through = the release procedure that Dan pointed out sometime in the next couple of d= ays and let folks know how things go. I think there are at least a couple o= f compile warnings on my Mac that will need to be fixed.

= Cheers, and have a good holiday to all those who are celebrating.

--Chad

On Sat, Dec 24, 2016 at 3:01 PM, Girvin He= rr (girvin_herr+g= herr_lists AT fastmail DOT com) [via = geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote= :

=20 =20 =20

On 12/24/2016 04:5= 0 AM, M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via= geda-user AT delorie DOT com] wrote:=

=20 As a prospective proxy maintainer for Gentoo, please let me know when you roll a tarball, and I'll run through the Gentoo packagin= g process, and do some preliminary build/run-testing and feed back.

If wanted, I can do the same for a Slackware Linux package.=C2=A0 I am currently running Slackware 14.1 (k3.10.103), but I have a copy of the latest 14.2 and plan to install it early next year.=C2=A0 The only change I can see is that the package architecture went from i486 in 14.1 to i586 in 14.2, but that is trivial.=C2=A0 Of course, the dependencies have changed.

Another option would be to contact the SlackBuilds.org pcb package maintainer, Felix Pfeifer:=C2=A0 pfeifer [dot] felix [at] googlemail [dot] com
He might be willing to do this task and put the resulting packages on SlackBuilds.

geda-gaf on SlackBuilds.org seems to be maintained by a different maintainer, Stephen Van Berg:=C2=A0 stephen_van_berg at earlicker dot c= om

I would second a more consistent version num= bering system, as this makes version-tracking easier for packagers too, so pcb v4 would indeed be a good choice if settled upon!

Consistency, yes.=C2=A0 But the form doesn't matter for Slackware packaging.=C2=A0 x.y.z is just as fine as yyyymmdd.=C2=A0 The only cave= at is that dashes may not be used in the version string.=C2=A0 I usually chan= ge them to underscores or remove them entirely if in yyyy-mm-dd.

Girvin Herr

Good luck, thanks, and keep us posted on the list :)

Michael.

On 24/12/16 12:2= 3, Peter Clifton (petercjc= lifton AT googlemail DOT com) [via geda-user AT delorie DOT com= ] wrote:

Nice to hear work is going on with mainline pcb as well...

One thing prior to release. We ought to git rm the debian directory that added to the repository.

This matches preferred distro policy, and makes life easier for the official packagers (so they can use our sources directly without having to repackage them to remove the debian dir.

I checked this with our debian packagers some while back to confirm, but never got around to making the delete.

Peter

--001a114428c4361ba90544704174--