9:13 p.m.
Hello there, all.
I believe our roadmap may be unrealistic and need adjustment.
The following items are necessary for the release of 1.0 and are
included in some way in the official roadmap:
KDE theme (2 days)
Have to ensure everything is properly set and test on new and upgraded
systems.
Wallpapers (1 day)
Connect with Horst, ensure availability in Plasma, LXQt, XFCE pickers.
Dev handbook (7 days)
Write.
User handbook (10-14 days)
Write.
image.git (2 days)
Connect squashroot search code to getenv("squashpath"). Test with
multi-arch CDs on physical machines and Qemu.
Fake horizon (4-12 weeks)
Write and test everywhere.
Marketing (1-3 weeks)
Write copy, organise release event, contact individuals, press, companies.
alpha2 list (5-10 days)
Package.
alpha7 list (3-7 days)
Package.
Java (2-10 days)
Port to ELFv2, package.
Rust (bump) (1 day)
Will block builders while building (2-3 hours depending on arch); review
failures if any; gather data for arm64 if necessary.
Rust (arm64) (2+ weeks)
Fix compiler build failure.
Firefox 60 (ppc64) (1+ week)
Fix launch failure.
Parcel: http (3 days)
Learn cURL API; learn libarchive API; learn BearSSL API; write code to
fetch, take, and verify APKINDEX from APKINDEX.tar.gz on internet location.
Parcel: digraph (5-8 days)
Write acyclic digraph in C++.
POSIX: VSC (10-14 days)
Set up tests on all architectures (arm64, ppc32, ppc64, i586, x86_64).
Run tests on all architectures. Verify test results. Attempt to make
fixes, if possible.
Total: Best case: 107 days, worst case: 226 days
The following items are necessary for the release of 1.0 and are *NOT*
included in any way in the official roadmap - these are collected from
just the past week of IRC logs and open browser tabs on my workstation:
More TrueType fonts (2-3 days)
Identify libre fonts. Package and test in X11.
Fix GRUB 2 package (3-5 days)
Create new configuration system. Integrate script from
https://bts.adelielinux.org/show_bug.cgi?id=49 in to new system.
Package the handbooks in .apk format (1-2 days)
Create a release tarball of handbooks. Ensure packaging is successful.
Ensure all handbooks are readable in a screen pager at 80 cols and full
1080p Konsole.
Fix KDE card decks (1 day)
Remove errant decks that cause Qt crash. Test KPat on all architectures
to ensure correct functionality with QT_QUICK_BACKEND="software" and
QT_QUICK_BACKEND="".
ConsoleKit 2 segfault (3-7 days)
Identify source of crash. Fix.
Sort out kernel options between architectures (5-10 days)
Identify differences and similarities between Kconfig options in each
architecture. Identify which config options should be shared across all
arches (uprobes, Wacom tablets are a start). Networking config options.
Ship new kernels for each architecture with fixed kernel options.
At least one more KDE bump (1-2 days)
Frameworks 5.54, or possibly 5.55. Decide 18.08.4 vs 18.12.x. If
roadmap extends into May, 19.04.0.
https://gcc.gnu.org/ml/gcc-patches/2018-12/msg00886.html (1-2 days)
Integrate POSIX conformance patch into system/gcc.
Package rdesktop (2 days)
Package. Acquire a Windows machine for testing. Test.
Fix AltiVec detection code in GCC (2-5 days)
Determine why GCC is emitting mtvrsave instructions in function
prologues for functions that need to catch SIGILL to determine if
AltiVec is supported on a CPU. Fix.
Add _NPROCESSORS_ONLN to getconf(1) (1-2 days)
Write.
Fix PolicyKit / udisks2 to allow user disk mounting (1-5 days)
May be as simple as fixing ConsoleKit bug (above). May not be.
Total: Best case: 23 days, worst case: 46 days
The following items *should* be completed for the release of 1.0 but may
be skipped:
X.Org null pointer dereference fix (2-5 days)
Create AMI for AWS (2 days)
European mirror (3 days)
Xaw/Xt text mirroring issue (2-5 days)
eterm, glx-dock, mktrayicon, netsurf, powernowd, qastools (1 day)
Package Node.js (2-4 days)
Try to port Go to ELFv2 and back out POWER8 requirement (3-10 days)
Total: Best case: 15 days, worst case: 30 days
Grand total:
Best case: 130 (145 with optional) days
Worst case: 272 (302 with optional) days
That puts us right around the last week of May for a best case scenario,
and the first week of November 2019 for a worst case scenario.
First of all, I think that perhaps we should have a BETA3 release with
some of the more pressing issues fixed. Scratch Fake Horizon and we're
still looking at 102 days or mid-April.
Suggested BETA3 goals:
KDE theme (2 days)
Wallpapers (1 day)
User handbook (10-14 days)
image.git (2 days)
alpha2 list (5-10 days)
alpha7 list (3-7 days)
Rust (bump) (1 day)
Firefox 60 (ppc64) (1+ week)
POSIX: VSC (10-14 days)
More TrueType fonts (2-3 days)
Fix GRUB 2 package (3-5 days)
Fix KDE card decks (1 day)
Sort out kernel options between architectures (5-10 days)
At least one more KDE bump (1-2 days)
Package rdesktop (2 days)
Fix AltiVec detection code in GCC (2-5 days)
Add _NPROCESSORS_ONLN to getconf(1) (1-2 days)
This has a best case of 58 days (a fox gestation cycle, or 6 March
2019), and a worst case of 95 days (12 April 2019). Pad it out a little
and BETA3 would have a Wish of 9 March, and a Due of 14 April.
This would also leave the rest of 1.0 to be best case 72 days, worst
case 177 days:
Dev handbook (7 days)
Fake horizon (4-12 weeks)
Marketing (1-3 weeks)
Java (2-10 days)
Rust (arm64) (2+ weeks)
Parcel: http (3 days)
Parcel: digraph (5-8 days)
Package the handbooks in .apk format (1-2 days)
ConsoleKit 2 segfault (3-7 days)
https://gcc.gnu.org/ml/gcc-patches/2018-12/msg00886.html (1-2 days)
Fix PolicyKit / udisks2 to allow user disk mounting (1-5 days)
My preference for this thread would be one discussion about whether a
BETA3 should be added or not, and another thread about item discussion.
Is there something missing from this list that needs to be in 1.0?
Maybe something I forgot, or something you feel is critical? (Perhaps
armhf/armv6 should be added; that could be running in the background
while real work is done on all the other items, since it shouldn't need
much in the way of hand-holding.) Perhaps you feel that one or more of
these items is not critical for release.
Let's discuss.
Best,
--arw
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org