After 11.3.0, 11.3.1 - notes
The 11.3.0 cycle is coming to a close. Hopefully without distracting too much from it, I wanted to circulate some brief notes on what follows. The steering goals for 11.3.0 have been to have a good quality release for deployments using XO-1 and XO-1.5, and a known-stable stack to serve as scaffolding to the XO-1.75 efforts. We haven't finished 11.3.0 yet but I think there is ample evidence that it is working. On the XO-1.75 front, we are clearly a little further from finished -- our release candidates for XO-1.75 aren't really. But that's natural with software changes riding on top of hardware changes. So our plan is to release 11.3.0 as planned; and open a second deep-freeze bugfix window that will lead to 11.3.1 . During this period we will accept - XO-1.75 platform improvements -- namely drivers and kernel fixes. - High importance regression bugs elsewhere in the stack, only after careful triaging. After the 11.3.0 cycle, we don't expect any here. The timeframe for this bugfix window is still unclear. The dashing Daniel will be released from his release management duties once he releases 11.3.0. For the 11.3.1, I will drive the release process, and will be begging for help from experienced RMs (hi Simon!) and Peter for the build process. Not only we are losing a widely feared RM, but also a fantastic debugger and across-the-stack hacker. Hoping Daniel continues to work with us going forward. After 11.3.x, we have a major leap ahead. The next development cycle breaks all of our toys, with systemd, gtk/PyGO, GNOME3, NetworkManager, Linux 3.x on x86 and F-16-ARMv7HL. Too bad Debian has the Lenny name taken. cheers, m -- mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: After 11.3.0, 11.3.1 - notes
On Mon, Oct 17, 2011 at 2:50 PM, Martin Langhoff mar...@laptop.org wrote: The 11.3.0 cycle is coming to a close. Hopefully without distracting too much from it, I wanted to circulate some brief notes on what follows. The steering goals for 11.3.0 have been to have a good quality release for deployments using XO-1 and XO-1.5, and a known-stable stack to serve as scaffolding to the XO-1.75 efforts. We haven't finished 11.3.0 yet but I think there is ample evidence that it is working. On the XO-1.75 front, we are clearly a little further from finished -- our release candidates for XO-1.75 aren't really. But that's natural with software changes riding on top of hardware changes. So our plan is to release 11.3.0 as planned; and open a second deep-freeze bugfix window that will lead to 11.3.1 . During this period we will accept - XO-1.75 platform improvements -- namely drivers and kernel fixes. - High importance regression bugs elsewhere in the stack, only after careful triaging. After the 11.3.0 cycle, we don't expect any here. The timeframe for this bugfix window is still unclear. Query: Some of the 11.2.0 targeted languages (presumably the same in 11.3.0) are still a good way from completion. I would like to know if I should press for L10n of those specifically, as there is a reasonable chance we could pick up some coverage if the L10n whip is wielded judiciously. L10n commits will need to be checked for build-breakers (printf and terminal newlines are the common culprits), but otherwise is not generally going to introduce unexpected issues. cjl [1] http://lists.laptop.org/pipermail/devel/2011-February/031016.html en_US es ar pt pt_BR fr ht mn mr_IN am_ET km_KH ne_NP ur_PK rw ps fa_AF si de zh_CN ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: After 11.3.0, 11.3.1 - notes
On Mon, Oct 17, 2011 at 3:36 PM, Chris Leonard cjlhomeaddr...@gmail.com wrote: Some of the 11.2.0 targeted languages (presumably the same in 11.3.0) are still a good way from completion. Which ones are some way from completion? Where do you expect progress to be made? newlines are the common culprits), but otherwise is not generally going to introduce unexpected issues. In the 10.1.x series we had some fun with dialogs not resizing correctly, so the risk *is* there :-/ If languages progress over over time, even if they don't fit our cycle, deployments can pull them in for a custom build. This is right now fairly awkward, but perhaps we can automate it a bit with some improvements to OOB. cheers, m -- mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: After 11.3.0, 11.3.1 - notes
On Mon, Oct 17, 2011 at 4:10 PM, Martin Langhoff mar...@laptop.org wrote: On Mon, Oct 17, 2011 at 3:36 PM, Chris Leonard cjlhomeaddr...@gmail.com wrote: Some of the 11.2.0 targeted languages (presumably the same in 11.3.0) are still a good way from completion. Which ones are some way from completion? Where do you expect progress to be made? See attached spreadsheet for details. As with many things, progress seems to get made where attention is focused and where resources can be begged, borrowed or stolen. I can't do the translations myself, and attempts at rallying the troops has differing impacts and differing rates of return on effort depending on the language. These are all selected as OLPC deployment langs, so I guess one question is what can OLPC do to encourage L10n efforts in these langs by the local deployment partners. newlines are the common culprits), but otherwise is not generally going to introduce unexpected issues. In the 10.1.x series we had some fun with dialogs not resizing correctly, so the risk *is* there :-/ So the time for testing these issues would be now, across as many langs as possible (not just the 11.3.0 selection). Advanced testing by the local deployment partners of these langs would be most critical for this subset. If languages progress over over time, even if they don't fit our cycle, deployments can pull them in for a custom build. This is right now fairly awkward, but perhaps we can automate it a bit with some improvements to OOB. Yes, we are also working to re-establish the language pack generation script that used to work back in the 0.82 days, this would provide another means of picking up newer L10n bits. I'm not suggesting the inclusion of any given L10n bits in the 11.3.0 build as a blocker, just trying to determine if it is worth trying to make a focused effort on that language subset (to the exclusion of the other ~110 or so) to drive L10n to the extent possible before the 11.3.1 release or not. It is an allocation of effort question on my part. cjl 11.3.0_L10n_status.ods Description: application/vnd.oasis.opendocument.spreadsheet ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
