Change Proposals for Fedora 23

Stephen Gallagher sgallagh at redhat.com
Thu Jun 4 16:31:13 UTC 2015



> On Jun 4, 2015, at 12:21 PM, Josh Boyer <jwboyer at fedoraproject.org> wrote:
> 
>> On Thu, Jun 4, 2015 at 8:21 AM, Stephen Gallagher <sgallagh at redhat.com> wrote:
>> 
>> 
>> Some items I forgot yesterday:
>> 
>> ==============================
>> == Stable API Documentation ==
>> ==============================
>> 
>> === Benefits ===
>> Having a Fedora-provided repository of the specific set of API (and
>> ABI) that we guarantee stability or backwards-compatibility will go a
>> long way towards addressing the concerns around our lack of an LTS
>> release. Additionally, it will make life easier for our users to have a
>> single source to look for documentation, rather than the current
>> situation of having to search out each upstream for documentation.
>> 
>> === Issues/Risks ===
>> * Requires a large time commitment from someone on the Fedora Docs
>> team to collate the documentation and post it to the Fedora
>> Documentation site.
>> * Requires developer effort to locate and identify the stable APIs
>> * Almost certainly cannot all be done in a single release
>> 
>> === Recommendations ===
>> * Locate someone from Fedora Docs to do the collation
>> * Start with a set of known-stable APIs (such as glibc and systemd)
>> and publish those for Fedora 23.
>> 
>> 
>> 
>> =========================
>> == API break detection ==
>> =========================
>> 
>> === Benefits ===
>> Provide a taskotron process that will identify API and ABI breaks for
>> common languages when updates are submitted to Bodhi. If such are
>> detected, we should disable autopush-by-karma. This will allow us to be
>> able to better avoid incompatible updates in stable releases of Fedora.
>> 
>> === Issues/Risks ===
>> * Tooling needs to be implemented. (Some help may be available from
>> libabigail[1])
>> * Someone needs to write a taskotron process that will run when
>> updates are created
>> * Available tools for this are currently limited to C/C++ ELF
>> libraries
>> 
>> === Recommendations ===
>> Search out someone to do this work. It is high value for comparatively
>> little work (since much of the hard work has been solved by
>> libabigail). Volunteers highly requested.
>> 
>> It would be worthwhile to start with C/C++ and see how things progress
>> from there.
> 
> Wouldn't both of these be better served by the Base WG?  Particularly
> for very low-level components like systemd and glibc.  I don't see why
> Server would be the only Edition to have such documentation when it is
> common across all of them.
> 
> josh
> _______________________________________________
> server mailing list
> server at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/server


I suppose a better explanation would be hat the Server SIG has a strong interest and is attempting to drive the effort. It certainly needs not be restricted to Server. 


More information about the server mailing list