From Fedora Project Wiki
No edit summary
 
(7 intermediate revisions by 2 users not shown)
Line 37: Line 37:
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: pbrobinson at fedoraproject dot org
* Email: pbrobinson at fedoraproject dot org
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
* Release notes ticket: [https://pagure.io/fedora-docs/release-notes/issue/118 #118]
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 57: Line 57:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracking bug:
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1515517 #1515517]


== Detailed Description ==
== Detailed Description ==
Line 81: Line 81:
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Release engineering: N/A (not a System Wide Change) [[https://pagure.io/releng/issue/7134 | rel-eng ticket 7134]] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: N/A (not a System Wide Change) : [https://pagure.io/releng/issue/7134 rel-eng ticket 7134] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook  -->
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook  -->
Line 149: Line 149:
-->
-->


[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAcceptedF28]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 15:11, 2 March 2018



Sugar 0.112

Summary

Update Sugar to the new upstream 0.112 stable feature release.

Owner

Current status

Detailed Description

We want to provide the new version of the Sugar desktop environment as well as more activities to allow further building upon the collaborative environment.

Users curious about the Sugar interface can test out Sugar on an existing Fedora system by selecting the Sugar environment from their display manager.

Developers interested in working on the Sugar interface or writing activities can have a development platform without needing an XO laptop.

Benefit to Fedora

This feature will let all involved projects like Fedora and Sugar Labs profit, as it brings the latest and greatest bits from the Sugar community for education into Fedora. By making Sugar more readily available, it's easier for users to play with it, become involved, and contribute back. It will allow us to capture the interest in developing for OLPC and Sugar Labs on the Fedora platform.

Scope

  • Proposal owners: Update to the latest Sugar UX, update and test Activities and other integration with the distro.
  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

It's a simple and clean upgrade from previous Sugar releases that shipped with Fedora such as Sugar 110 in F-26/F-27 or Sugar 108 in F-25 using standard Fedora upgrade tools.

How To Test

Download a SoaS F-28 nightly, Beta or RC x86 live image or ARM disk image.

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) Feature is already mostly complete, upstream stable release is scheduled will within the required release window
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes