Thanks for the info. Repology is now showing Fedora Rawhide as having 5.0.0
available.
Steve
On 07/22/2018 10:18 PM, Mark Roszko wrote:
> For the record, the little badges on the kicad website for linux
> distro package versions come from https://repology.org which scans the
> repos of
For the record, the little badges on the kicad website for linux
distro package versions come from https://repology.org which scans the
repos of many distros and provides the badges. So changes in the
version of the package may not be reflected immediately until they
rescan. Pretty useful since
Thank you.
Den søn. 22. jul. 2018 kl. 15.04 skrev Steven A. Falco :
>
> I took a look, and no changes to the web site are needed regarding Fedora
> packages. Thanks for the pointers.
>
> Steve
>
> On 07/20/2018 09:48 PM, Adam Wolf wrote:
> > Hi Steven,
> >
> > The website is actually
I took a look, and no changes to the web site are needed regarding Fedora
packages. Thanks for the pointers.
Steve
On 07/20/2018 09:48 PM, Adam Wolf wrote:
> Hi Steven,
>
> The website is actually managed via github, and you can fork the
> repository and make the edit and make a pull
I looked at that page, and I opened a bug to update the text from 5.0.0-rc3 to
5.0.0:
https://bugs.launchpad.net/kicad/+bug/1782858
The page looks a little strange in Fedora's Firefox, although it looks fine in
chrome.
I attached a screenshot showing how part of the text is chopped off. I
Hi Steven,
Thank you.
Will you submit a pr for changes on the fedora download page if at all needed?
http://kicad-pcb.org/download/fedora/
Nick
Den fre. 20. jul. 2018 kl. 20.02 skrev Steven A. Falco :
>
> I've made a build of 5.0.0 for Fedora rawhide:
>
>
I've made a build of 5.0.0 for Fedora rawhide:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1129084
This will take a little while to push out to the Fedora mirror servers.
Steve
On 07/20/2018 07:53 AM, Wayne Stambaugh wrote:
> Great work Rene and thanks to all of the library
Great work Rene and thanks to all of the library developers. Our
libraries will be one of the most noticeable improvements in the v5 release.
Cheers,
Wayne
On 07/19/2018 06:51 PM, Nick Østergaard wrote:
> Awesome, thanks for the update!
> Den fre. 20. jul. 2018 kl. 00.48 skrev Rene Pöschl :
>>
Awesome, thanks for the update!
Den fre. 20. jul. 2018 kl. 00.48 skrev Rene Pöschl :
>
> The library repos should now all be tagged. (Github had some server
> problems so it all took quite some time. I hope nothing got damaged
> because of that.)
>
> On 19/07/18 10:49, Nick Østergaard wrote:
> >
The library repos should now all be tagged. (Github had some server
problems so it all took quite some time. I hope nothing got damaged
because of that.)
On 19/07/18 10:49, Nick Østergaard wrote:
This sounds good. Thank you.
Den tor. 19. jul. 2018 kl. 10.43 skrev Rene Pöschl :
On 18/07/18
This sounds good. Thank you.
Den tor. 19. jul. 2018 kl. 10.43 skrev Rene Pöschl :
>
> On 18/07/18 19:59, Carsten Schoenert wrote:
> > Am 18.07.18 um 19:55 schrieb Rene Pöschl:
> >>> I'm traveling the whole Saturday and Sunday to Debian DebCamp and
> >>> DebConf in Taiwan and working on packaging
On 18/07/18 19:59, Carsten Schoenert wrote:
Am 18.07.18 um 19:55 schrieb Rene Pöschl:
I'm traveling the whole Saturday and Sunday to Debian DebCamp and
DebConf in Taiwan and working on packaging kicad-packages3d on a laptop
is PITA. So I'd like to this at home on a more powerful machine at home
Am 18.07.18 um 19:55 schrieb Rene Pöschl:
>> I'm traveling the whole Saturday and Sunday to Debian DebCamp and
>> DebConf in Taiwan and working on packaging kicad-packages3d on a laptop
>> is PITA. So I'd like to this at home on a more powerful machine at home
>> latest on Friday afternoon.
>>
>>
On 18/07/18 18:09, Carsten Schoenert wrote:
Hi,
Am 18.07.18 um 16:23 schrieb Nick Østergaard:
I probably didn't mention this clearly. It is also good for me if
everything is tagged on friday, I guess that is mostly about the libs,
as I will probably tag i18n and doc myself.
I'd like to see at
Hi,
Am 18.07.18 um 16:23 schrieb Nick Østergaard:
> I probably didn't mention this clearly. It is also good for me if
> everything is tagged on friday, I guess that is mostly about the libs,
> as I will probably tag i18n and doc myself.
I'd like to see at least the packages3D repository is
I am away from monday, so no worries.
ons. 18. jul. 2018 16.27 skrev Wayne Stambaugh :
> Nick,
>
> Please let me know if you can't get around to tagging the i18n and doc
> repos. I can tag them on Friday if need be.
>
> Cheers,
>
> Wayne
>
> On 7/18/2018 10:23 AM, Nick Østergaard wrote:
> > I
Nick,
Please let me know if you can't get around to tagging the i18n and doc
repos. I can tag them on Friday if need be.
Cheers,
Wayne
On 7/18/2018 10:23 AM, Nick Østergaard wrote:
> I probably didn't mention this clearly. It is also good for me if
> everything is tagged on friday, I guess
I probably didn't mention this clearly. It is also good for me if
everything is tagged on friday, I guess that is mostly about the libs,
as I will probably tag i18n and doc myself.
I am on vacation next week with no connectivity.
Nick
Den ons. 18. jul. 2018 kl. 16.19 skrev Wayne Stambaugh :
>
>
Sorry about that. I missed the restructure info. I think I covered
most of the changes in my repo. I will try to get my changes pushed
tonight so I can get some feedback before the official release announcement.
On 7/18/2018 10:13 AM, Nick Østergaard wrote:
> Ohh, well, I wrote that. He just
Ohh, well, I wrote that. He just restructured the dir structure
recently. I have only listed features added that could remember at
some point, there are certainly missing. So I suggest any developer
who have anything to add just creates a PR ASAP.
Den ons. 18. jul. 2018 kl. 16.10 skrev Wayne
Nick,
A preliminary draft is already written[1] by Mark Roszko. I just need
to finish cleaning it up and remove the draft tag for the release
announcement.
Cheers,
Wayne
[1]:
https://github.com/KiCad/kicad-website/blob/master/content/blog/release-5.0.0.adoc
On 7/18/2018 10:01 AM, Nick
AFAIK, old stable was any stable release prior to the v4 release. From
v4 on we should make any required migration paths version specific.
On 7/18/2018 9:58 AM, Adam Wolf wrote:
> Oof! I hadn't even thought of that. I was just concerned about folks
> not understanding that "old stable" means a
Wayne,
If you have a draft ready for the release announcement, please create
a pull request with it as a draft or push it as a draft, in case we
would like to add more info. This to avoid anyone else in attempting
to write it.
Nick
Den ons. 18. jul. 2018 kl. 14.41 skrev Wayne Stambaugh :
>
>
Oof! I hadn't even thought of that. I was just concerned about folks
not understanding that "old stable" means a specific nameless release,
rather than the phrase "a stable release that is older than the
current release".
Adam
On Wed, Jul 18, 2018 at 8:56 AM Wayne Stambaugh wrote:
>
> Migrating
Migrating is definitely a version to version issue so v4 to v5 migration
would make the upgrade path clear. I would hope no one is upgrading
from old stable to v5. That would really be ugly.
On 7/18/2018 9:50 AM, Adam Wolf wrote:
> I am talking with Nick about if we want the "migration from old
I am talking with Nick about if we want the "migration from old
stable" still in the sidebar, or if we should replace it with V4 to V5
migration, or if we should make a new generic migration page. I think
we could discuss it here, rather than a Github issue on the website
repo.
I think
The goal is to have everything tagged by Friday and then give the
package builders a few days to get the 5.0.0 packages (or a least most
of them) built and added to the website before making the official
announcement. I still have some changes to make to the release
announcement which I should
Tell me if I am wrong, but I start to believe we are going to publish v5
this Friday. Is there anything missing I could help with? Do we have the
website updates ready?
Cheers,
Orson
On 07/11/2018 08:49 PM, Wayne Stambaugh wrote:
> Are there any critical bugs remaining to be fixed for the stable
On 7/12/2018 10:50 AM, Rene Pöschl wrote:
> On 12/07/18 16:35, Wayne Stambaugh wrote:
>> I agree with you in principal but the practical side of these changes is
>> far more subtle as demonstrated by the simulation and erc issues. The
>> invisible power pin issue has been around for as long as I
Le 12/07/2018 à 16:43, Rene Pöschl a écrit :
> On 12/07/18 16:20, jp charras wrote:
>> Le 12/07/2018 à 16:04, Rene Pöschl a écrit :
>>> Sadly the old symbols are completely unusable in many modern circuits which
>>> use more then one power
>>> supply for different parts of the circuit. Hidden
On 12/07/18 16:20, jp charras wrote:
Le 12/07/2018 à 16:04, Rene Pöschl a écrit :
Sadly the old symbols are completely unusable in many modern circuits which use
more then one power
supply for different parts of the circuit. Hidden power pins are not the way to
go! The fix for this
bug must
I agree with you in principal but the practical side of these changes is
far more subtle as demonstrated by the simulation and erc issues. The
invisible power pin issue has been around for as long as I can remember
(mid 80s). Oddly enough, op-amps typically have power pins shown on all
units
Le 12/07/2018 à 16:04, Rene Pöschl a écrit :
> Sadly the old symbols are completely unusable in many modern circuits which
> use more then one power
> supply for different parts of the circuit. Hidden power pins are not the way
> to go! The fix for this
> bug must come from a different side then
I certainly agree about the invisible pins! What I have done for my symbols is
to put the power pins on the first unit of a multi-unit component and make them
visible.
On 07/12/2018 09:04 AM, Rene Pöschl wrote:
Sadly the old symbols are completely unusable in many modern circuits which use
Sadly the old symbols are completely unusable in many modern circuits
which use more then one power supply for different parts of the circuit.
Hidden power pins are not the way to go! The fix for this bug must come
from a different side then reintroducing hidden power pins.
On 12/07/18 13:46,
On 7/12/2018 8:01 AM, jp charras wrote:
> Le 12/07/2018 à 13:46, Wayne Stambaugh a écrit :
>> Rene,
>>
>> Bug https://bugs.launchpad.net/kicad/+bug/1781290 may be an issue. The
>> decision to separate symbol power pins as a separate symbol unit caused
>> this bug. I didn't think about this when
Le 12/07/2018 à 13:46, Wayne Stambaugh a écrit :
> Rene,
>
> Bug https://bugs.launchpad.net/kicad/+bug/1781290 may be an issue. The
> decision to separate symbol power pins as a separate symbol unit caused
> this bug. I didn't think about this when the changes to the symbol
> libraries where
Rene,
Bug https://bugs.launchpad.net/kicad/+bug/1781290 may be an issue. The
decision to separate symbol power pins as a separate symbol unit caused
this bug. I didn't think about this when the changes to the symbol
libraries where made but it is going to cause issues for anyone trying
to
The libs should be ready to go. We might still fix some minor things
till the release but we do not have any showstopper topics open.
On 11/07/18 20:49, Wayne Stambaugh wrote:
Are there any critical bugs remaining to be fixed for the stable 5
release? I didn't see any thing outstanding but I
For windows the installer should also be in good nick. No pun intended.
There are some minor things that I would like to do, but they are by
no means a blocker for a release.
Nick
Den ons. 11. jul. 2018 kl. 21.35 skrev Adam Wolf
:
>
> MacOS installer is ready.
>
> Adam
> On Wed, Jul 11, 2018 at
MacOS installer is ready.
Adam
On Wed, Jul 11, 2018 at 1:50 PM Wayne Stambaugh wrote:
>
> Are there any critical bugs remaining to be fixed for the stable 5
> release? I didn't see any thing outstanding but I may have missed
> something while I was on vacation. I'm going to create a 5.0.0
>
Are there any critical bugs remaining to be fixed for the stable 5
release? I didn't see any thing outstanding but I may have missed
something while I was on vacation. I'm going to create a 5.0.0
milestone for the last few remaining bugs and shoot for a 7/20 tag date
unless there are any more
42 matches
Mail list logo
