Search results
Jump to navigation
Jump to search
Page title matches
- 24 bytes (2 words) - 01:27, 3 July 2009
- 31 bytes (2 words) - 16:36, 4 July 2009
- 24 bytes (2 words) - 21:33, 23 February 2010
- 24 bytes (2 words) - 21:33, 23 February 2010
Page text matches
- {{Latest Releases | rc = inline }} ...able below shows details of OLPC OS releases for the XO laptops (including releases that are in the planning or in-development stages).4 KB (605 words) - 19:47, 12 November 2016
- [[Fedora:Releases/31/Schedule | Fedora 31 Schedule]] - 2019-07-15 - Proposal submission deadl [[Fedora:Releases/31/ChangeSet | Fedora 31 Accepted Changes]]443 bytes (57 words) - 22:57, 19 May 2019
- # Sucrose included in official distribution releases by these distributors: #* [[ALT Linux]] (FIXME: which official releases?)2 KB (300 words) - 18:14, 15 July 2012
- ...c_logo.png|middle|200px|link=OLPC:Releases]]||<span class="weblink">[[OLPC:Releases|OLPC OS 16.04]]</span>||OLPC OS for OLPC NL3 laptops based on Ubuntu 16.04 ...c_logo.png|middle|200px|link=OLPC:Releases]]||<span class="weblink">[[OLPC:Releases|OLPC OS 13.x]]</span>||OLPC OS for OLPC XO laptops based on Fedora 182 KB (229 words) - 18:57, 8 June 2021
- == Releases == ...e Roadmap follows Fedora's schedule, since SoaS is a Fedora Spin: [[Fedora:Releases/26/Schedule]]2 KB (262 words) - 01:12, 26 February 2017
- * Packaging Sugar releases, including the Sugar infrastructure (Glucose) and activities (Fructose) ==Sugar Releases==2 KB (322 words) - 04:26, 25 January 2012
- | [http://wiki.sugarlabs.org/go/Development Team/Release/Releases/Sucrose/0.81.1 Release News] | [http://wiki.sugarlabs.org/go/Development Team/Release/Releases/Sucrose/0.81.2 Release News]6 KB (643 words) - 21:48, 14 September 2009
- ==Releases== No releases at the moment.2 KB (369 words) - 20:17, 12 December 2014
- ** after releases ** solicit distributions for testing of new releases2 KB (368 words) - 20:16, 24 February 2010
- == Releases == We have defined the role of the release manager for the past 3 releases as the following:3 KB (497 words) - 19:13, 27 November 2019
- ==Releases==2 KB (301 words) - 16:55, 18 December 2013
- ...tart polishing process in close interaction with downstreams.<br>Minor 1.x releases should be ready for using in the field.433 bytes (62 words) - 16:28, 8 October 2012
- == Releases ==2 KB (362 words) - 21:42, 1 July 2012
- ...s developing the activity on Launchpad to be easier on students. Official releases will be posted to the sugarlabs gitorious repository.978 bytes (144 words) - 18:53, 6 June 2009
- ...aving stable code base and infra to fulfil deployment needs in further 1.x releases. ...o 1K)</strike> sounds like more deployment related task, thus moved to 1.x releases2 KB (369 words) - 16:28, 8 October 2012
- * support Ubuntu, and all its derivates, releases in time. | style="http://old-releases.ubuntu.com/releases/text-align: center;" bgcolor="lightgreen" | {{OBS/monitor|SweetsDistributio6 KB (742 words) - 18:07, 18 May 2016
- * #TODO SeanDALY is now Press Release Guru - sends out press releases, maintains press list * #TODO SeanDALY post "how to handle SL press releases!" stuff on the MarketingTeam wiki, and then poke the marketing mailing list3 KB (528 words) - 20:07, 24 February 2010
- ==Releases== *http://old-releases.ubuntu.com/releases/4 KB (482 words) - 18:01, 18 May 2016
- ...low regular release schedules, e.g., 6-month, support, long-term supported releases, etc. But, there may be cases where Sugar has its own specific needs: ...'t rely on the chance that all these activities will work on so many Sugar releases. For example, someone may take the Record activity (maybe not the last vers5 KB (756 words) - 10:13, 3 July 2011
- Extend the activity version numbering scheme to allow major and minor releases. ...1, 1.2, 1.4.5, 2.5.7.4). You can still use an integer number only for your releases.3 KB (484 words) - 14:59, 5 November 2013
- This page documents known API changes in OLPC releases. ...uses Sugar (sucrose) release 0.82. See http://sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.821 KB (203 words) - 21:32, 23 February 2010
- 2. List of education publications I have added for press releases - discussing the possibility of doing press releases in languages other3 KB (555 words) - 20:07, 24 February 2010
- ...t objects only, set if previously checked-in Context might have more fresh releases on the node; it is not possible to filter Contexts by this value; ...mple, ''activity'' type assumes activity bundles uploaded to the ''Context.releases'' property, or, [[#post-type|Post.type]] depends on Context type it was cre5 KB (818 words) - 02:59, 4 September 2014
- ...i contains specific requests to incorporate new design features into Sugar releases. ...a number of features either currently implemented or planned for upcoming releases.2 KB (318 words) - 19:15, 27 November 2019
- feedback. Additionally, the releases will be available as Soas, an easy2 KB (272 words) - 20:16, 24 February 2010
- * [[Sugar_Server_Kit/Release_plan|Statement of purpose for releases]]1 KB (146 words) - 10:57, 12 June 2013
- [[fedora:Releases/15 | Fedora 15 Schedule]] - 25 January 2011 - Feature submission deadline1 KB (176 words) - 01:32, 29 January 2011
- ...r dx related packages. The automated yum updater is supposed to update the releases accordingly.2 KB (317 words) - 00:37, 17 May 2016
- == Tasks for future releases ==3 KB (436 words) - 12:44, 2 August 2010
- ==Releases==3 KB (478 words) - 08:05, 22 May 2012
- * Stability (looking towards current and future releases) * No regressions w.r.t earlier dx-2 or olpc.au releases6 KB (1,105 words) - 00:37, 17 May 2016
- ...ere are no Long Term Support, [[wikipedia:Long_Term_Support|LTS]], Sucrose releases. It makes coordination difficult between Sugar deployments. :** Among the 6 months Sucrose releases, there will be Long Term Supported releases.4 KB (601 words) - 16:32, 8 October 2012
- We approved a budget request for 10 PR releases from ERELEASES.COM. The cost is US $2390.00. Sean Daly will oversee the use771 bytes (110 words) - 08:54, 15 January 2013
- ...(LTS)<br>Targeting to Sugar deployments that can't switch between Sucrose releases every six months. ...SweetsDistribution SweetsDistribution:<SUCROSE-RELEASE>]<br>Stable STS/LTS releases of Harmonic Distribution.5 KB (646 words) - 23:16, 26 November 2012
- ...per could release, not only stable releases, e.g., development, or testing releases, (users will know the release stability status, without reading it somewher3 KB (470 words) - 14:49, 25 November 2010
- ...recipes, using the versions available in foresight or the latest upstream releases otherwise.1 KB (164 words) - 21:38, 1 July 2012
- ...ecify which versions of Sugar a page is valid for. When referring to Sugar releases, use "Sugar X.XX" - eg. "Sugar 0.82".3 KB (464 words) - 00:34, 5 December 2011
- ...status (and needs) of short-term deadlines: the upcoming Fedora and Ubuntu releases; the press release; documentation rebase948 bytes (135 words) - 23:39, 1 March 2011
- ...s be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?" ...s be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"3 KB (411 words) - 23:41, 1 March 2011
- * The version bump is to allow for stable releases after Chat-48 which is the current stable release.1 KB (150 words) - 00:39, 3 July 2009
- ...ble Release}}| release page]] has as links to the release pages of earlier releases. * [[OLPC:Releases]]3 KB (461 words) - 02:35, 27 July 2012
- ...submit a Cinnamon spin for review and possible inclusion in future Fedora releases, though I am sure it is too late to include in F22. It is a spin simply usi ...submit a Cinnamon spin for review and possible inclusion in future Fedora releases, though I am sure it is too late to include in F22. It is a spin simply usi4 KB (555 words) - 21:28, 29 June 2015
- * Are you willing to provide regular source releases? (releases need to be done as well when there are only changes in translations) * Maintainer responsiveness and willingness to provide regular releases.11 KB (1,705 words) - 19:51, 16 January 2018
- ...development and head of stable. And to leave a trail behind of all stable releases for others to spawn off from if they so choose."3 KB (544 words) - 19:37, 27 July 2010
- Benefits coming in future releases will be: ...ork will be the base for improvements in the collaboration stack in future releases.4 KB (610 words) - 16:05, 5 November 2013
- |Development and testing releases.2 KB (246 words) - 17:16, 14 September 2017
- ...the env variable exists or not, because activities can run in older Sugar releases, where this env variable is not available (check the Browse example).1 KB (224 words) - 22:10, 12 October 2015
- ...tting help''' section. If the home page were generated (as it was in OLPC releases see ticket {{bug|574}}) then it could detect if the Help content is install ...se; or it could dynamically built from a template as it was in the OLPC OS releases, and detect if the user has local help pages. You can also detect in JavaS4 KB (726 words) - 08:58, 11 December 2017
- ...s be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?" ...s be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"4 KB (664 words) - 23:41, 5 March 2011
- * Support for future releases2 KB (318 words) - 20:10, 24 February 2010