www.delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2016/12/24/07:15:17

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <585E6661.8070806@xs4all.nl>
Date: Sat, 24 Dec 2016 13:13:21 +0100
From: "Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] [pcb] Plans for Next Release of pcb
References: <CAJZxidDy5HcLZivqc5w+cnv716EFNLXKJdKXo+jDPMDVrJb2=Q AT mail DOT gmail DOT com> <74d9e3df-7aaa-cb29-5584-8c52d19227b1 AT sbcglobal DOT net> <CAJZxidDPsP4=dBHu=M-yZ7Lmo-kgo2z2jDpcZgD=dtwB4TdWog AT mail DOT gmail DOT com>
In-Reply-To: <CAJZxidDPsP4=dBHu=M-yZ7Lmo-kgo2z2jDpcZgD=dtwB4TdWog@mail.gmail.com>
Reply-To: geda-user AT delorie DOT com

Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> There is a page on launchpad with a list of bugs to fix before the 
> next release (https://launchpad.net/pcb/+milestone/next-bug-release), 
> many of which have been addressed. Unless there are things like fixing 
> warnings, I think we ought to push the rest of them to a future bug 
> release for the sake of getting a release out quickly.
>
> Regarding versioning, I think that generally for major releases, a 
> release candidate and a testing period is a good idea. But I wonder, 
> how many of our users are already using the git head? If most people 
> are, then we've already basically had a testing period. When we put 
> out a release candidate, do distributions package and distribute it? 
> So, basically, would we get a larger testing audience by doing so? If 
> not, then maybe we should just skip it this time for the purpose of 
> getting the release out the door more quickly.
>
> Girvin-
> Slackware was my distro of choice until I had to start using a work 
> computer, so I actually know how to build a Slackware package. But pcb 
> isn't part of the Slackware distribution. You can get an older version 
> of pcb from sbopkg. I think I still have script lying around to build 
> a package from the latest git version if you'd like a copy.
>
> --Chad
>
> On Dec 21, 2016 5:58 PM, "Girvin R. Herr (gherr375 AT sbcglobal DOT net 
> <mailto:gherr375 AT sbcglobal DOT net>) [via geda-user AT delorie DOT com 
> <mailto:geda-user AT delorie DOT com>]" <geda-user AT delorie DOT com 
> <mailto:geda-user AT delorie DOT com>> wrote:
>
>
>
>     On 12/21/2016 05:43 AM, Chad Parker (parker DOT charles AT gmail DOT com
>     <mailto:parker DOT charles AT gmail DOT com>) [via geda-user AT delorie DOT com
>     <mailto:geda-user AT delorie DOT com>] wrote:
>
>         Hi pcb Devs-
>
>
>         Regarding packaging, do we create packages for distributions,
>         or do the distributions to that themselves?
>
>     Chad,
>     I am just a lowly user, but here is my 2-cents:
>     I run Slackware Linux, so I download the source and build my own
>     Slackware installation package.  Whatever was done in the past has
>     worked fine for me.  I have had no problems building the 1.8.2
>     version from source.  I do rebuild .rpm packages for some apps,
>     such as LibreOffice and Slackware has an rpm extractor (rpm2cpio)
>     that works for them, but I prefer to build from source to make
>     sure all the dependencies are correct.
>
>     Not that I have seen them in gEDA, but compile warnings make me
>     nervous.  There is no reason they cannot and should not be fixed.
>     It's a sign of lack of quality.
>     Compile errors are fatal frustrations.
>
>     Thanks and good luck.
>     Girvin Herr
>
>
Hi Chad,

I moved all open bug reports listed to the pcb "future-bug-release" 
(https://launchpad.net/pcb/+milestone/future-bug-release) to get them 
"out of the way" and hope that they do not distract you anymore ;-)

I will keep away from pushing to the "master" branch for the coming 
weeks (busy day job, no holidays, most likely no pcb monthly code sprint 
this last Sunday of the month (December 25th)) so you can start your 
"dry run" any time you like.

Please keep us informed how this "dry run" works out.

Kind regards,

Bert Timmerman.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019