kicad-doc-devs team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

Hi

I think having a one to one mapping with branches for the i18n repo is
fine, and the i18n is highly dependent on the kicad src. But for the
doc repo, I don't think that is needed, it is better to have as few
branches here as possible, as the docs are only a meta description of
kicad and not dependent in the same way. Clearly not a lot of people
have addressed the newer things in kicad 5.0 so we shall try to avoid
creating more work (aka branches) for ourselves here.

So for doc, we only support master and latest stable, for now we
should probably wait with a 5.0 branch and just tag 5.0.0. A branch
can always be made if the doc is to diverge, i.e. that a new feature
in 5.1 or master is documented not in 5.0. I we create the 5.0 branch
now from the 5.0.0 tag, we will just risk people commits there, and we
diverge the master and 5.0 when we are actually documenting the exact
same features. I am open for other opinions about this.

Nick

Den ons. 18. jul. 2018 kl. 13.21 skrev Carsten Schoenert
<c.schoenert@xxxxxxxxxxx>:
>
> Hello Marco,
>
> Am 18.07.18 um 12:58 schrieb Marco Ciampa:
> > Hello devs and translators,
> > I just created the branches 5.0 and 5.1 of the i18n repo for allowing the
> > translators and translations to follow the recent (and future) ui changes.
> > When there will be a 6.0 branch different from master, please let me know.
>
> wouldn't it have been better to pull first all outstanding pull request
> that are for the version 5.0.0 nonetheless? Or at least some
> communication about how to handle this all? I see some PRs are merged
> some don't. Why?
>
> It's always a bit tedious not to know what's going on (or not).
>
> A branch 5.1 is right now not really useful in my eyes.
>
> > PS: I'm currently on a vacation at a south Italian seaside.
> > Please be patient that the connection (and family :-) do not allow frequent
> > updates...
> >
> > PPS: we should probably create such a branch for docs too or we can
> > better handle it with some notes inside the docs? Please have a say on
> > it!
>
> Not that I don't mind and support this, but to get a proper solution for
> all parties it would be good to use this mailing list here to
> coordinate. I'm currently not really convinced to put ongoing energy
> into translations and rework on the documentation without seeing a real
> gain on it.
>
> --
> Regards
> Carsten Schoenert
>
> --
> Mailing list: https://launchpad.net/~kicad-doc-devs
> Post to     : kicad-doc-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-doc-devs
> More help   : https://help.launchpad.net/ListHelp