Present: jdsn, jw, lnussel, lrupp, mrueckert Topics: 1) doc.opensuse.org vs. activedoc.opensuse.org 2) Who is responsible for the update of the release-notes 3) Who is responsible for the index.html with the current release notes list 4) New layout for openSUSE release notes 5) Future plans for (open)SUSE release notes ---- Problems: * activedoc is the planned successor of doc.opensuse.org * what we release now (release-notes wise), needs to stay at least 2 years Solution: * activedoc will sooner or later replace the doc.opensuse.org (doc.opensuse.org will be activedoc.opensuse.org, the static content of doc.opensuse.org will be integrated into the activedoc front page) * as the release notes are below a /release-notes/ directory, this will be a simple apache alias and can stay whatever we do with the front page * old names (like docs.opensuse.org) will stay as long as they make sense and will just become an DNS alias that points to the "right" name 2) Who is responsible for the update of the release-notes * technical documentation and packaging will stay in the hands of the openSUSE team and doc team respectively. * once a new release-notes package is ready, it should go the current standard way via maintenance * autobuild will take care of the sync to all needed places (esp. http://doc.opensuse.org/release-notes/) 3) Who is responsible for the index.html with the current release notes list http://doc.opensuse.org/release-notes/ is currently empty, but should contain a list of release notes for the current openSUSE distributions. The openSUSE Team will take care to deliver (and update) an index.html to the autobuild team, which will integrate the page into the sync process. 4) New layout for openSUSE release notes The new layout developed for the SUSE Linux Enterprise distribution will also be used for upcomming release-notes packages of openSUSE (including old distributions, if an update is scheduled). 5) Future plans for (open)SUSE release notes The current setup is now at least 10 years old: YaST downloads the RPM package mentioned in the content file of the installation media. This is - for historical reasons - a special place, not identical to the standard repositories that are used for installation or update. Pro: * there is only one authoritative source: the package living in the (update) repository Con: * the downloaded release-notes package is just "installed" in the inst-sys system and therefor must be downloaded again from the update repository after the installation finished. * to adapt the release-notes, a new package has to be created and a maintenance workflow has to be started Releated feature entries: * Fate #315266: Download release notes in 1st stage Ideas: * use activedoc to create, update and publish the current release notes * YaST should download the current release-notes from activedoc directly * to get an offline version of the release-notes, either activedoc should provide an RPM version or each update should create such an RPM to be processed by the maintenance engine -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org