User here. I'd be happy to try and release a Gentoo ebuild in an overlay, but I'd want an RC first, versus live ebuilds, which kind of suck, since I believe they force a fresh build for every source update. I'd also be somewhat curious about trying to do a homebrew package for OS X, but from lurking on this list I suspect there's already some folks who might know how to do that already, but if not I'm happy to give it a shot.
-Ian On Mon, Sep 7, 2015 at 9:29 AM Nick Østergaard <oe.n...@gmail.com> wrote: > Indeed. Also by making an release candidate might motivate packagers > to prepare packages for their system, and then we can catch some > potential problems, and possible get some input to address them for > the release. > > 2015-09-07 14:33 GMT+02:00 Chris Pavlina <pavlina.ch...@gmail.com>: > > I second this. Just make the branch! The bugs keep piling in anyway, and > > most of them are minor - barely reproducible. We're as ready as we'll > ever > > be! > > > > On Sep 7, 2015 6:00 AM, "Brian Sidebotham" <brian.sidebot...@gmail.com> > > wrote: > >> > >> My humble suggestion is to just create the RC1 branch now because I've > >> been through all of those bugs, and they're all either incomplete or > >> not repeatable for me. In which case we need more information in order > >> to be able to fix them. > >> > >> In order to get more information, it's better to have a larger > >> user-base. Plus, a user-base on a pre-built rc candidate. It's > >> possible for example that some people's systems are a bit screwy when > >> building and so we're really chasing phantoms that are down to their > >> specific build. With an RC we're at least debugging a single sane > >> thing. > >> > >> That's what an RC is for in my opinion - it has known issues, but we > >> need help moving forward. Plus, these issues will become insignificant > >> compared the waft of new bugs that are going to come out of the > >> woodwork when we make an RC build for mass people to test. I don't > >> think that work should be delayed for a few bugs that are almost > >> unrepeatable. > >> > >> I have a patch holding for adding the interactive routing options to > >> the draw toolbar. It makes no sense to me for those brilliant tools to > >> be available only in a menu option - they should be in the draw > >> toolbar and disabled when in legacy canvas mode so people know what > >> they're missing out on! ;) > >> > >> Sorry, I've only just managed to get some time together to be able to > >> work on KiCad again, so bad timing! > >> > >> Best Regards, > >> > >> Brian. > >> > >> On 6 September 2015 at 21:11, Wayne Stambaugh <stambau...@gmail.com> > >> wrote: > >> > This is a reminder to *all* developers, please do not send any patches > >> > or merge requests unless it is specifically to fix an existing bug > >> > report. Also, please don't bother fixing the build scripts or any of > >> > the CMake dependency library build code as they will be removed during > >> > the next development cycle. My preference is that we focus on the > >> > critical bug reports that are keeping me from creating an rc1 branch. > >> > They can be found here: > >> > > >> > > >> > > https://bugs.launchpad.net/kicad/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on > >> > > >> > This list needs to get to zero before I'm willing to create any rc1 > >> > branch. > >> > > >> > Thank you for your cooperation. > >> > > >> > Cheers, > >> > > >> > Wayne > >> > > >> > _______________________________________________ > >> > Mailing list: https://launchpad.net/~kicad-developers > >> > Post to : kicad-developers@lists.launchpad.net > >> > Unsubscribe : https://launchpad.net/~kicad-developers > >> > More help : https://help.launchpad.net/ListHelp > >> > >> _______________________________________________ > >> Mailing list: https://launchpad.net/~kicad-developers > >> Post to : kicad-developers@lists.launchpad.net > >> Unsubscribe : https://launchpad.net/~kicad-developers > >> More help : https://help.launchpad.net/ListHelp > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : kicad-developers@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
