Re: [Kicad-developers] Future plans on the KiCad library releases?

On 1/24/2018 11:57 AM, Carsten Schoenert wrote: > Hi, > > Am 15.01.18 um 12:09 schrieb Rene Pöschl: >> On 15/01/18 11:16, Carsten Schoenert wrote: >>> Hi, >>> >>> as the packaging for Debian will change as well for the next KiCad >>> release I've some questions pointed to the contributors and

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi, Am 15.01.18 um 12:09 schrieb Rene Pöschl: > On 15/01/18 11:16, Carsten Schoenert wrote: >> Hi, >> >> as the packaging for Debian will change as well for the next KiCad >> release I've some questions pointed to the contributors and admins of >> the libraries to be able to prepare the needed

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 01/23/2018 06:18 PM, Matthijs Kooijman wrote: [snip]> Automatically updating existing schematics when one of its symbols moved > to a different library would of course be awesome if that could happen > as well. I also made a suggestion about that: > >> One way I can imagine this works is to

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 1/23/2018 2:18 PM, Vesa Solonen wrote: > Matthijs Kooijman kirjoitti 23/01/18 klo 19:18: >> Hi Wayne, > >> I think upgrading the library list is the most important, since (in the >> eyes of users) it is a fairly trivial change (in terms of what needs to >> happen, not necessarily in terms of

Re: [Kicad-developers] Future plans on the KiCad library releases?

Matthijs Kooijman kirjoitti 23/01/18 klo 19:18: > Hi Wayne, > I think upgrading the library list is the most important, since (in the > eyes of users) it is a fairly trivial change (in terms of what needs to > happen, not necessarily in terms of implementation) that is annoying to > do every time

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 1/23/2018 12:18 PM, Matthijs Kooijman wrote: > Hi Wayne, > >> This is not a trivial issue to fix. I'm not sure there is a good answer >> for this issue. > It's certainly not trivial, but I believe a fix would not be terribly > hard either. > > Let me repeat my original proposal here: > >> I

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi Wayne, > This is not a trivial issue to fix. I'm not sure there is a good answer > for this issue. It's certainly not trivial, but I believe a fix would not be terribly hard either. Let me repeat my original proposal here: > I can imagine that KiCad either gets a way to: > 1) include all

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 1/23/2018 11:56 AM, Matthijs Kooijman wrote: > Hi Wayne, > >> I was not being sarcastic. Here is what I meant: > Thanks for clarifying. > >> For stable version 5, the libraries should be tagged and used for all >> stable 5 point releases (5.0.1, 5.0.2, ...). Most corporate users >> prefer

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi Wayne, > I was not being sarcastic. Here is what I meant: Thanks for clarifying. > For stable version 5, the libraries should be tagged and used for all > stable 5 point releases (5.0.1, 5.0.2, ...). Most corporate users > prefer consistency over having the latest libraries so installing

Re: [Kicad-developers] Future plans on the KiCad library releases?

Mattijs I was not being sarcastic. Here is what I meant: For stable version 5, the libraries should be tagged and used for all stable 5 point releases (5.0.1, 5.0.2, ...). Most corporate users prefer consistency over having the latest libraries so installing the next point release of kicad

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi Wayne, > > > [Proposal to make library upgrades easier] > > > > As a user, 1% agree. > > Me too! If users want to constantly update their libraries, that's > their choice but kicad installers should not be forcing this on users. > We should have a fixed set of libraries that are tagged

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 01/17/2018 11:05 AM, Rene Pöschl wrote: [snip] > The reason for this not being able to be auto tested is that one > can not really parse a datasheet automatically. Minor off-topic: you may want to have a look at uConfig [1]. I do not claim it is a perfect tool, as I doubt it is possible to

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 17/01/18 10:03, Carsten Schoenert wrote: Some more information about the current plans and doings in the library team would be a good thing! And please not only through the KiCad user forum. Please use also the KiCad website and/or the new GitHub site for the libraries you have created. Not

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi Maciej, > I can easily imagine a message saying: "Why do you guys modify my > perfectly organized symbol library table when I update the libraries > package? I have carefully picked the libraries that are useful to me, so > I do not need to go through a long list when selecting components. Now

Re: [Kicad-developers] Future plans on the KiCad library releases?

On Wed, Jan 17, 2018 at 07:55:02AM +, Matthijs Kooijman wrote: > Hi Wayne, > > > KiCad should not be determining which libraries get loaded just because > > our library layout gets more complex. I would reject any design changed > > that loaded libraries outside the users control. Maybe I'm

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi Matthijs, On 01/17/2018 08:55 AM, Matthijs Kooijman wrote: [snip] > Additionally, I don't really want to think about this when upgrading. If > I upgrade the libraries package, I really want to still be able to just > use all official libraries, without having to check after each upgrade > if

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi Wayne, Carsten, On Mon, Jan 15, 2018 at 12:49:00PM -0500, Wayne Stambaugh wrote: > I agree 100%. Once we tag the v5 stable libraries, package devs should > clone from that version for every v5 point release to prevent the issue > you are describing. I think there might be a misunderstanding

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi Wayne, > KiCad should not be determining which libraries get loaded just because > our library layout gets more complex. I would reject any design changed > that loaded libraries outside the users control. Maybe I'm misreading > this but it kind of sounds like that to me. My proposal would

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hey Carsten, On 1/15/2018 11:14 AM, Carsten Schoenert wrote: > Hello Wayne, > > Am 15.01.2018 um 14:56 schrieb Wayne Stambaugh: >> I though we were using version tags on the library repos that matched >> the kicad stable release version to ensure that packagers would be able >> to provide the

Re: [Kicad-developers] Future plans on the KiCad library releases?

We should tag stable 5 for all of the library repos and that should be used for *all* stable 5 releases. Changing libraries during a stable version series (5.0.0, 5.0.1, ...) doesn't make sense to me. I don't think users expect their libraries to change for bug fix releases of KiCad. Any other

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 1/15/2018 10:23 AM, Matthijs Kooijman wrote: > Hi folks, > >>> 3. What are the plans for providing coherent library names and the >>> introducing new libraries? >> We will try to limit such problems. But it might still happen that a library >> will be split up into multiple libs if the library

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 15/01/18 17:53, Carsten Schoenert wrote: Am 15.01.2018 um 12:09 schrieb Rene Pöschl: ... 1. Is there some release time strategy planned? Are there any release dates planned for the newly created repositories and what are the planes for releasing updates of these. The only discussion i know

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hello Wayne, Am 15.01.2018 um 14:56 schrieb Wayne Stambaugh: > I though we were using version tags on the library repos that matched > the kicad stable release version to ensure that packagers would be able > to provide the same libraries. I don't want a situation where each > packager uses

Re: [Kicad-developers] Future plans on the KiCad library releases?

The version number is not the real question here. We can tag the libs monthly to allow users more fine grained control over which version they want to use. One option to still have the release information is to add an additional tag (with the kicad version) to the monthly release that coincides

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi folks, > > 3. What are the plans for providing coherent library names and the > > introducing new libraries? > We will try to limit such problems. But it might still happen that a library > will be split up into multiple libs if the library gets too large. I had an idea on solving this. Not

Re: [Kicad-developers] Future plans on the KiCad library releases?

I though we were using version tags on the library repos that matched the kicad stable release version to ensure that packagers would be able to provide the same libraries. I don't want a situation where each packager uses different commits from the library repos to create packages. I don't

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 15/01/18 11:16, Carsten Schoenert wrote: Hi, as the packaging for Debian will change as well for the next KiCad release I've some questions pointed to the contributors and admins of the libraries to be able to prepare the needed package transitions as also mentioned by Jean-Samuel. 1. Is

Re: [Kicad-developers] Future plans on the KiCad library releases?

Den 15. jan. 2018 11.16 skrev "Carsten Schoenert" : Hi, as the packaging for Debian will change as well for the next KiCad release I've some questions pointed to the contributors and admins of the libraries to be able to prepare the needed package transitions as also

[Kicad-developers] Future plans on the KiCad library releases?

Hi, as the packaging for Debian will change as well for the next KiCad release I've some questions pointed to the contributors and admins of the libraries to be able to prepare the needed package transitions as also mentioned by Jean-Samuel. 1. Is there some release time strategy planned? Are