I think the drawbacks here are enough to make me unsure if this adds enough value. This would mean we could only add new documentation, and could not remove or edit documentation that is out of date in master.
I agree with Marco that it would be best if there were two doc branches (stable and master) and both are published to the web automatically. So we could have https://docs.kicad-pcb.org/nightly/ or whatever. That way, the translation effort could stay mostly with the stable branch, but also the translators (and anyone else editing documentation) could see rough drafts of the coming documentation for a long time, and users who are testing nightly builds have a better chance of finding documentation that actually applies to them. -Jon On Fri, Jan 10, 2020 at 5:05 AM Maciej Suminski <maciej.sumin...@cern.ch> wrote: > One idea which is simple to implement and improves the situation a bit > is to add a note saying 'this feature is enabled in nightlies/will be > enabled in 6.0'. Unfortunately it works only for new features, but not > for things that are just modified between KiCad versions. > > Cheers, > Orson > > -- > Mailing list: https://launchpad.net/~kicad-doc-devs > Post to : kicad-doc-devs@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-doc-devs > More help : https://help.launchpad.net/ListHelp >
-- Mailing list: https://launchpad.net/~kicad-doc-devs Post to : kicad-doc-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-doc-devs More help : https://help.launchpad.net/ListHelp
