I'm fine with using this for bike shedding as long as the results get updated in the actual road map and this is not the official road map. One caveat, by allowing anyone to edit this file, you may loose control of it's content. That's one of the things I don't like about launchpads blueprints. I also don't want this to turn into a popularity contest. We have to make sensible decisions based upon project requirements and manpower limitations so all final decisions are made by the lead development team.
On 3/5/2018 12:57 PM, Jon Evans wrote: > Hi all, > > Since my day job involves a lot of engineering planning/timelines/etc, > I've had this rolling around in my head... > I started brainstorming some proposed changes to the roadmaps. > > I am using Google drive because that's what is easiest for me to play > with; I'm happy to send patches against the official roadmaps if get > some buy-in for this. > > Feel free to comment (either directly on the doc or by email) with > thoughts on this. > > https://docs.google.com/document/d/1mpxqvxLv497cyfk8KTQijhySSpFxF7ooTtcT_HU86kw/edit# > > Basically what I am proposing is to put most of the energy into Eeschema > for 6.0, with changes to other parts of the software basically being > "whatever people have time left over for". Everything else has been > bumped to 7.0 > > -Jon > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : firstname.lastname@example.org > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : email@example.com Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp