kicad-doc-devs team mailing list archive

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

I don't see an advantage of creating a 5.0 branch before more issues are fixed

https://github.com/KiCad/kicad-doc/issues

We don't gain anything by having a 5.0 branch other than wasting
valuable time. IMHO.
On Thu, 11 Oct 2018 at 08:13, Marco Ciampa <ciampix@xxxxxxxxxx> wrote:
>
> On Wed, Oct 10, 2018 at 07:04:16PM +0200, Carsten Schoenert wrote:
> > Hi,
> >
> > Am 09.10.18 um 14:32 schrieb Marco Ciampa:
> > > Forwarding this from the dev mailing list...
> > >
> > > Please note that Nick is ready to tag 5.0.1 from the 5.0 branch, see:
> > >
> > > https://github.com/KiCad/kicad-i18n/issues/306
> > >
> > >> Unless anyone comments on this issue, that they are working on
> > >> translations for 5.0.1, I will tag 5.0.1 tonight. This issue have been
> > >> open for comments for almost a month, and the KiCad source has been
> > >> tagged.
> > >
> > > and I agree. So if there is a last-time update, get a move on!
> >
> > what is about the tree on kicad-doc?
> > I will need this update too (if there is one) for packaging kicad.
> > kicad-doc has only the master and the old 4.0 branch so I don't know the
> > status for this repo.
>
> The master is (partially) updated for the 5.0 source branch, so, in my
> opinion, it should have a 5.0 branch too.
>
> If all agree we can create the branch.
>
> Nick?
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get it.
>
> ------------------------
>
>  GNU/Linux User #78271
>  FSFE fellow #364
>
> ------------------------
>
>
> --
> 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