sgrogan wrote: ↑Tue Mar 12, 2019 8:42 pm
14.04 and 16.04 are still QT4/PY2, so I can work on releasing these once we decide what to do about the docs.
I forgot, yeah, I guess 14.04 and 16.04 will have to remain Qt4/Py2 (14.04 reaches EOL next month anyway, as you wrote in another topic).
I think we should look at removing the freecad-doc package from the freecad packaging and use Kurt's work on Debian, if that's not too much work. Knowing we'll almost certainly have to make a few iterations of the package (we always do), this will save a lot of bandwidth. I wonder if that would mean duplicating the work Yorik just did to extract the wiki into html (probably, since he didn't generate the fr/it pages). We should have a discussion about making this method the "official" one starting with 0.19... If not on salsa.debian.org, then on Github under the FreeCAD project.
sgrogan wrote: ↑Tue Mar 12, 2019 8:42 pm
master is already 1 commit ahead of 0.18, but hasn't switched to 0.19 yet. If this commit was backported, I would build the daily against master and the latest daily would = 0.18 release. This would buy time for the rest of the work.
Unless Kurt says there are big hurdles preventing this, how about this:
- Build a last freecad-daily-018 package - maybe change the beta label to RC (release candidate)?
- Build freecad-doc-en/fr/it packages separately (Kurt's Debian method)
- Build Ubuntu 14.04/16.04 freecad-stable Qt4/Py2 packages without doc
- Build Ubuntu 18.04/18.10 freecad-stable Qt5/Py2-Py3 packages using Kurt's Debian method