Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
On Thu, Oct 11, 2018 at 07:51:42AM -0400, Wayne Stambaugh wrote: > What is the issue here? There are no serious issues here, I think we should only make things more clear and straightforward... > Do we just need a 5.0.1 tag or do we need something else? Tagging the master to 5.0.1 surely is enough to let packagers go on for now but I think that the simpler & logical solution is to keep source, i18n & docs branch names in sync. > I doubt there are any documentation changes that are > specific to 5.1 so it seems easy enough to tag the documentation at > 5.0.1 as it stands lets do just this for now. > but maybe I'm not understanding the issue. I would suggest to adopt a more coherent and general approach to the matter in the future. Docs sport hotkeys, procedures and screenshots. One or more of these elements are do to change with future versions of KiCad. If 5.1 will not be so different from the 5.0 branch, the same will definitely not be for the 6.0 version. Now we have two branches of docs: 4.0 and master. I really can't see why not branching docs to 4.0, 5.0 or 5.* and master (future 6.0 or 6.* if you prefer...) anyway branches are cheap... -- 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-doc-devs More help : https://help.launchpad.net/ListHelp
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
A tag will be made when the docs have been checked. There shall be no 5.0 branch at its current state. 5.0 series docs are made from master directly. As agreed earlier there will be some time between tagging the kicad source and i18n and docs to get the last fixes in. Please be patient. On Thu, 11 Oct 2018 at 14:26, Carsten Schoenert wrote: > > Hello Wayne, > > Am 11.10.18 um 13:51 schrieb Wayne Stambaugh: > > What is the issue here? Do we just need a 5.0.1 tag or do we need > > something else? > > I mainly need a tag. The tag is the version I will use for my needed > tarballs. The tag should happen on the correct branch so it's easy to > see what things are belonging together. > > > I doubt there are any documentation changes that are > > specific to 5.1 so it seems easy enough to tag the documentation at > > 5.0.1 as it stands but maybe I'm not understanding the issue. > > I don't know if there has something changed against 5.0.0 because I > don't know what's the branch I need to look. OTOH there are just two > branches. > > -- > Regards > Carsten Schoenert > > -- > 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
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
Hello Wayne, Am 11.10.18 um 13:51 schrieb Wayne Stambaugh: > What is the issue here? Do we just need a 5.0.1 tag or do we need > something else? I mainly need a tag. The tag is the version I will use for my needed tarballs. The tag should happen on the correct branch so it's easy to see what things are belonging together. > I doubt there are any documentation changes that are > specific to 5.1 so it seems easy enough to tag the documentation at > 5.0.1 as it stands but maybe I'm not understanding the issue. I don't know if there has something changed against 5.0.0 because I don't know what's the branch I need to look. OTOH there are just two branches. -- Regards Carsten Schoenert -- 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
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
What is the issue here? Do we just need a 5.0.1 tag or do we need something else? I doubt there are any documentation changes that are specific to 5.1 so it seems easy enough to tag the documentation at 5.0.1 as it stands but maybe I'm not understanding the issue. On 10/11/2018 5:35 AM, Marco Ciampa wrote: > On Thu, Oct 11, 2018 at 11:20:34AM +0200, Nick Østergaard wrote: >> There is a plan. > > Is it somewhere in the dev docs? > I do not see anything the like where it should be, probably here: > > http://docs.kicad-pcb.org/doxygen/md_Documentation_development_stable-release-policy.html > -- 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
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
On Thu, Oct 11, 2018 at 11:20:34AM +0200, Nick Østergaard wrote: > There is a plan. Is it somewhere in the dev docs? I do not see anything the like where it should be, probably here: http://docs.kicad-pcb.org/doxygen/md_Documentation_development_stable-release-policy.html -- 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-doc-devs More help : https://help.launchpad.net/ListHelp
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
There is a plan. Tag the source first, then have a grace period to allow dependencies as libs, i18n and docs to check the last bits before tagging. Packagers should just use the tags or tarballs when ready. On Thu, 11 Oct 2018 at 10:42, Carsten Schoenert wrote: > > Hi, > > Am 11.10.18 um 10:13 schrieb Nick Østergaard: > > 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. > > well, currently I see just more time wasting on my side because of > confusion for me (and I'm probably not the only person here). And it > will not getting better in the future by staying on the bridge in the > middle. > > All the time we have talked about this is right now is more if it would > have been done in the past. :-( > kicad-doc is the same as the libraries, kicad-i18n, kicad-footprints ... > > Why not have a plan for this all and some straightforward way? Why do > often FOSS projects do make not needed work like this here. > > Yes, KiCad 5.0.1 will be probably the last 5.0 release, but I also > wouldn't bet on this. And the next goal will be 5.1.0 release. It's > quite not logical fore me to do some argumentation like above given for > the 4.0 release circle a branch was created anyway. Branches and Tags > are cheap. > > Maintaining all the KiCad packages for Debian is already taking a lot of > time, please don't make this more power consuming than necessary. > > -- > Regards > Carsten Schoenert > > -- > 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
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
On Thu, Oct 11, 2018 at 10:42:46AM +0200, Carsten Schoenert wrote: > Hi, > > Am 11.10.18 um 10:13 schrieb Nick Østergaard: > > 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. > > well, currently I see just more time wasting on my side because of > confusion for me (and I'm probably not the only person here). And it > will not getting better in the future by staying on the bridge in the > middle. > > All the time we have talked about this is right now is more if it would > have been done in the past. :-( > kicad-doc is the same as the libraries, kicad-i18n, kicad-footprints ... > > Why not have a plan for this all and some straightforward way? Why do > often FOSS projects do make not needed work like this here. > > Yes, KiCad 5.0.1 will be probably the last 5.0 release, but I also > wouldn't bet on this. And the next goal will be 5.1.0 release. It's > quite not logical fore me to do some argumentation like above given for > the 4.0 release circle a branch was created anyway. Branches and Tags > are cheap. > > Maintaining all the KiCad packages for Debian is already taking a lot of > time, please don't make this more power consuming than necessary. I completely agree with you. If there is no reason for not (as it seems to me) I am proceeding with the branch for tomorrow. -- 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-doc-devs More help : https://help.launchpad.net/ListHelp
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
Hi, Am 11.10.18 um 10:13 schrieb Nick Østergaard: > 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. well, currently I see just more time wasting on my side because of confusion for me (and I'm probably not the only person here). And it will not getting better in the future by staying on the bridge in the middle. All the time we have talked about this is right now is more if it would have been done in the past. :-( kicad-doc is the same as the libraries, kicad-i18n, kicad-footprints ... Why not have a plan for this all and some straightforward way? Why do often FOSS projects do make not needed work like this here. Yes, KiCad 5.0.1 will be probably the last 5.0 release, but I also wouldn't bet on this. And the next goal will be 5.1.0 release. It's quite not logical fore me to do some argumentation like above given for the 4.0 release circle a branch was created anyway. Branches and Tags are cheap. Maintaining all the KiCad packages for Debian is already taking a lot of time, please don't make this more power consuming than necessary. -- Regards Carsten Schoenert -- 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
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
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 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@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
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
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@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-doc-devs More help : https://help.launchpad.net/ListHelp
Re: [Kicad-doc-devs] Kicad 5.0.1 almost ready to go
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. -- Regards Carsten Schoenert -- 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
