Activity
From 21/08/2017 to 19/09/2017
19/09/2017
-
11:43 am action #24766 (Resolved): sync 15.0 staging:dvd have the same config like ring2
- done.
-
- all sub-package was created in the main project, now everything should fulfill up to ring2. but 000product is a probl...
13/09/2017
-
- 1) build against ring0 was removed
2) lua changes were in
3) php7 was in
4) several missed packages were in
12/09/2017
-
07:23 pm action #24756 (Feedback): enable iso syncing to openQA
- MR not merged, haven't received any feedback so far.
07/09/2017
-
02:35 pm action #25102: enable bots/tools
- manager42 is enabled
-
- enable bots
* totest manager
* snapshot announcer (make sure to fix links in the template)
* leaper
* manager_4... -
- prjconf etc still needs to be created/checked
-
- Almost done except for staging. The method was a different one for this major release though. used osc copypac to cop...
-
- First, ask an obs admin to prepare the "partitioning" setup of OBS for the new release and to copy the signing keys i...
-
- initial bootstrap done. need to redo after fork now
-
- * build ring0 against ring0 of the previous release
* when ring0 is built remove the bootstrap aid
* bootstrap ring... -
- preparations done
https://github.com/openSUSE/package-lists/pull/19
still need to run on packagelists once it b... -
- The content of the DVDs is autogenerated. The new release needs to be integrated in the loop
https://github.com/op... -
-
- done
-
- https://et.innerweb.novell.com/project_pages/prod_bugz_edit_vrsms.jsp?bcid=1&lid=0&pid=53824
-
- https://gitlab.suse.de/openqa/scripts/merge_requests/125
-
- the rsync.pl script needs to be adjust to sync the isos to openQA
when doing that the directory for changes needs ... -
- already done
-
- tell SLE release engineers to sync SLE15 to OBS
-
- does not apply to 15.0.
-
- 00Meta/lookup.yml needs to be adjusted. All references to Factory, FORK or Devel; need point to 42.2.
-
- the release needs to be be announced on the opensuse-announce list
-
- * rename iso and .sha256 file to not include Build* anymore
* fix name in .sha256 files
* ask autobuild to sign the... -
- * switch off bots
* totest manager
* snapshot announcer
* leaper
* manager_42
* update_crawler
* bu... -
- - tag the GM build
- reduce job group size
- delete obsolete assets -
- add tags or branches for all translations in git, in case they need to be updated from that specific branch later
... -
- last translation packages should be submitted Monday of the GM week. So the deadline should be Sunday.
-
Need to reject requests to the new distro and set update project if not done already:
osc meta attribute ope...-
- send anounncement internally and externally to warn about the package freeze
-
- maintenance probably released several packages that are new in the previous release. We need to make sure to collect ...
-
- the javascript countdown on www.opensuse.org needs to be enabled
-
- rpm-groups.pot is not created automatically. Run once to generate the pot file
https://github.com/yast/yast-transl... -
- the instlux files on the isos need to be updated to show the current version
-
- There is a number of clouds/3rd party hosting out there where openSUSE is
available as option. The responsible peopl... -
- lock the main project and NonFree
<lock>
<enable/>
</lock>
-
- upload schedule to projects.suse.de
-
- A branch for new distribution needs to be created in the release notes git and the package adjusted accordingly.
T... -
- #opensuse-project (and maybe also other channels) mention 42.1 in the channel /topic
This needs to be updated to 4... -
- notify studio team about GM and release time
-
- both landing page and search page got translations for new languages. The languages need to be added to index.html
... -
- Packages that contain translations may need to be updated and submitted
* package-translations
* desktop-translat... -
- Plan for 42.3:
* log in to download.opensuse.org
* hardlink files from 42.3/iso into e.g. 42.3/iso-devel in ftp-s... -
- To branch the current ftp tree and isos for a milestone, log in to download.opensuse.org as mirror user and run:
... -
- The :Update project needs to have
<attributes>
<attribute name="Maintained" namespace="OBS"/>
<attri... -
- Since we use openSUSE-EULAs for a warning text we also need a translation for it:
https://github.com/openSUSE/openSU... -
- * remove %_with_betatest from prjconf
* remove beta tag from openSUSE.product
* remove BETA=1 from openQA -
- release number needs to be higher than in previous distributions. Make sure the are. mls knows how to.
-
- devel:openSUSE:Factory/openSUSE-EULAs needs to be up to date to include all relevant licenses. Ie licenses that requi...
-
- Packages that contain translations may need to be updated and submitted
- package-translations : system:install:he... -
- the maintenance tests expect a goldmaster DVD. A hard or symlink was installed during beta phase at /var/lib/openqa/f...
-
- openQA and the bot needs to be set up to also test maintenance updates for the new release
-
- Packages that contain translations may need to be updated and submitted
* package-translations
* desktop-translat... -
- create a test plan for people to manually test the distribution
New Plan for Leap 42.3:
https://docs.google.com/s... -
-
- mark milestone as released in https://en.opensuse.org/openSUSE:Roadmap
-
- prepare software.opensuse.org for the milestone
* https://github.com/openSUSE/software-o-o, app/controllers/main_c... -
- openSUSE:Leap:42.2/_product/*.product need to refer to the correct snapshot name in the <betaversion> tag
Changes ... -
- Ping everyone listed in https://en.opensuse.org/OpenSUSE_Localization_Teams to make sure translation teams are aware ...
-
- Update https://en.opensuse.org/openSUSE:Localization_guide to document the Weblate workflow
When done, link it fro... -
- disable the FCC submitter
-
- Packages that contain translations may need to be updated and submitted
-
- Packages that contain translations may need to be updated and submitted
* package-translations
* desktop-translat... -
- call for translators for the social media messages
-
- Wiki page with social media contact people:
https://en.opensuse.org/openSUSE:Social_media_contacts
Contact them, ... -
- Create social media messages based on our release announcement & top features. See the openSUSE wiki:
https://en.ope... -
- There used to be poster for release parties to be used in e.g. universities:
https://en.opensuse.org/openSUSE:Launch... -
- Create event pages for the release on facebook, G+ and other social media!
-
- Update https://en.opensuse.org/openSUSE:Launch_parties
-
- Base it on the article(s) in the last years.
https://en.opensuse.org/openSUSE:Launch_parties
https://news.opensus... -
- Organize release parties!
* Write release party invitation article
* Update release party wiki pages
* Organize re... -
- Prepare local software.o.o checkout with final build information. Test all changes and verify them **on the release d...
-
- as usual, we need ping translators to translate release announcement, e.g.
http://lists.opensuse.org/opensuse-tran... -
- RC1 is out, so we know what we will ship.
Get the KDE stuff from the KDE announcement, the GNOME stuff from the GN... -
- Check the packages from http://distrowatch.com/table.php?distribution=suse and add what's new. Check other sources, s...
-
- The technical people in the openSUSE team need to go over the feature guide, check if it is correct and tell you what...
-
- Time to get that feature page finished.
Remember, try to talk at least about the packages from http://distrowatch.co... -
- Move content from https://en.opensuse.org/openSUSE:Major_features to https://en.opensuse.org/Features_42.2. Make sure...
-
- The Feature Guide forms the base of our release marketing. It is a large list of the most important features in openS...
-
- Get our list of press contacts and create SEPARATE mails for each of them. If you know them personally, try to add a ...
-
- Gather everything and put it in a zip file in github (or somewhere else)
-
- We send the press a 'personalized' email. It contains some personal notes from whoever sends it (usually Jos/the CM)....
-
- Release team, board members etc.
Ask them, get times and dates which are convenient (in the week between GM and GA... -
- This is the thing which gets us awesome reviews and "blogs like this":http://www.linux-magazine.com/Online/Blogs/Off-...
-
- We usually quote one 'important' SUSE person first, putting the release into perspective. The second quote is usually...
-
- After this it should be really ready to get into the press kit... No more changes!
-
- Show the announce to people both engineering and in SUSE marketing for feedback. Incorporate changes.
-
- Take the feature highlights and use them to compose a first draft press announcement.
Some tips:
* Remember the 3x3... -
- Take the feature highlights and use them to compose a press announcement. Look at earlier announcements for the how
-
- Based on the announcement and the feature guide & esp highlights, write a draft announcement for news.opensuse.org. T...
-
- Bug the openSUSE Artwork team and get help from the openSUSE team: we need screenshots. See https://en.opensuse.org/S...
-
- This is about creating a short-list of the best, most awesome, coolest features in openSUSE Leap 42.2. It is CRUCIAL ...
-
- Main task for everything around the release announcement:
* Press announcement
* Community announcement mail
* Com... -
- * https://en.opensuse.org/Buy_openSUSE
* https://de.opensuse.org/openSUSE_kaufen -
- source code is at
https://github.com/openSUSE/shop.o.o -
- request new box image to put on the home page
request link to shop
contact is Gerlinde Regensburger <gr@opensourc... -
-
- notify mirror@opensuse.org about the release
-
- the update test repo needs to be set up
-
- adjust the knapsack for GM
-
- change symlink openSUSE-current in distribution/, update/, source/ and debug/ to point to new release
-
- Remind darix to switch the cron job that renders the countdown to hourly if not already done.
-
- several parties need access to the GM images
Usually via password protected place on http://download.opensuse.org/... -
- install google alerts in order to measure press impact later
keywords e.g. "opensuse release", "opensuse 13.2", "s... -
- We have rsync-160hotstuff module and we need to make sure ISOs and repo of the new release is included. at least the ...
-
- Write an article like https://news.opensuse.org/2013/10/07/help-promote-opensuse-13-1/ and promote our badges, backgr...
-
- Adapt the mirrorbrain "markers" and the index header template to list which mirrors provide the new release
Templa... -
- There is a number of clouds/3rd party hosting out there where openSUSE is
available as option. Leap needs to be uplo... -
- security@suse.de and maintenance@opensuse.org should know that the new release is in maintenance mode now. Also remin...
-
- the test updates need to be removed from the update channel at some point before GA. Ask maintenance@opensuse.org
-
- follow instructions in Sync-Opensuse.txt
-
- put torrent in separate directories, ask for volunteers to seed
Torrents are created using /work/cd/bin/torrent-wr... -
- remind opensuse.org admins about the upcoming release and to verify that the HA proxy can handle the load
-
- create a hangout with all the marketing guys to come up with creative things how to promote the release (to find idea...
-
- If there are any known issues in GM marketing needs to know about them to decide how to communicate them
-
- doc.opensuse.org
https://en.opensuse.org/SDB:Official_documentation
Ping Frank Sundermeyer about it -
- http://en.opensuse.org/Upgrade needs to be adjusted for new release
-
- Create the portal page https://en.opensuse.org/Portal:15.0 and template pages for pages that are expected to change. ...
-
- make sure all 15.0 pages are in good shape and the links between pages work
-
- move e.g. https://en.opensuse.org/Features_42.1 to https://en.opensuse.org/Features
-
- Make sure all pages reference $VERSION correctly
* http://en.opensuse.org/Welcome_to_openSUSE.org
* http://en.ope... -
- move all $VERSION-1 articles to Archive
-
-
- Security needs to take a look at the current snapshot
-
- Security needs to take a look at the current snapshot
-
- Security needs to take a look at the current snapshot
https://bugzilla.suse.com/show_bug.cgi?id=1090647 -
- smartypants go to openQA to download the final iso. Needs to be disable to avoid overloading the server.
Either by... -
- Some packages in 42.2 turned into a Fork after the lookup file for 42.3 was created. Update crawler would therefore c...
-
- The results of the manual testing initiative should be talked over with the release manager to determine whether the ...
-
- ask people to review and update https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.3/ via https://github....
-
- maintenance updates from the update project need to be merged back into the main repo
* use osc checkupdate (https... -
- verify that the Supplements in the test update pattern is gone. Should happen automatically via betatest macro but pa...
-
- the job to create ARCHIVES.gz, ChangeLog, ls-lR.gz etc needs to be enabled
--- openSUSE.product (revision 20)
+++... -
-
- create IPRQ document
Some information about IPRQ document:
The IPRQ document is a SUSE internal document used... -
- the nvidia drivers need to be uploaded as soon as the kernel ABI is stable enough
-
- send the information that 42.3 is Gold to opensuse-factory
-
- ping docu team and ask if the pdf was generated and sent to OSP
-
- we should announce the GM deadline internally just as SLE does
-
- create a test plan for people to manually test the distribution
New Plan for Leap 42.2:
https://docs.google.com/s... -
-
-
-
-
-
- for all packages that were added to Factory after the last leap release, set up https://build.opensuse.org/project/sh...
-
- mark milestone as released in https://en.opensuse.org/openSUSE:Roadmap
-
- mark milestone as released in https://en.opensuse.org/openSUSE:Roadmap
-
- prepare software.opensuse.org for the milestone
* https://github.com/openSUSE/software-o-o, app/controllers/main_c... -
- prepare software.opensuse.org for the milestone
https://github.com/openSUSE/software-o-o
app/controllers/main_c... -
- openSUSE:Leap:42.2/_product/*.product need to refer to the correct snapshot name in the <betaversion> tag
Changes ... -
- Packages that contain translations may need to be updated and submitted
- package-translations : system:install:he... -
- the nvidia packager needs to be available to create matching drivers for the release
-
- maintenance updates from the update project need to be merged back into the main repo
* use osc checkupdate (https... -
- the default patterns should include the update test packages so test updates actually get installed.
-
- https://counter.opensuse.org/link/ should point to https://en.opensuse.org/Portal:15.0?pk_campaign=counter
-
- Make sure the community repo list gets created:
https://opensuse-community.org/openSUSE_Leap_150_Community_Additiona... -
- prepare software.opensuse.org for RC1
* https://github.com/openSUSE/software-o-o, app/controllers/main_controller.... -
- Talk to security to request and submit a properly signed shim
-
- create a test plan for people to manually test the distribution
New Plan for Leap 42.3:
https://docs.google.com/s... -
- The most important languages in the distro, esp those on the DVD need to be translated. Remind translation teams.
... -
- make sure release notes for the new release appear in
https://doc.opensuse.org/release-notes/x86_64/openSUSE/ -
- Start kicking the artwork team: we need the release counter updated!
https://github.com/openSUSE/countdown.o.o -
- the slide show needs to be adjusted for each release
https://github.com/openSUSE/yast-slide-show/
to make sure ... -
- Ask Legal to review and potentially adjust the EULA.
The request form can be found in innerweb
Current license ... -
- the weak provides for the list needs to be generated/updated
Tools to do that are on github:
https://github.com/o... -
- obs needs a button to easily add the new distro as build repo. Eg. https://build.opensuse.org/project/add_repository_...
-
- http://download.opensuse.org/YaST/Repos/openSUSE_Leap_42.2_Servers.xml (defined in https://github.com/yast/skelcd-con...
-
- /etc/products.d/openSUSE.prod should have the endoflife option set
-
- We need a series of badges and social media backgrounds. Think twitter, facebook, G+ and website banners in various s...
-
- Create a social media plan and social media messages; and get them translated. Also, prepare our social media channel...
-
- The maintenance pages need some updating to reflect the current work flow
https://en.opensuse.org/openSUSE:Mainten... -
- maintenance needs to release test updates in the update channel
-
- The update projects need to be created, including attributes (excl OBS:Maintained which will be added later).
Also... -
- ie. don't disable those stuff in staging:dvd
Macros:
%_without_vnc 0
%_without_java 0
%_without_mono 0
%_witho... -
- compile a list of packages that are on SP2 but got updated in 42.2, like e.g. texlive. Those need to be submitted for...
-
- Set up OBS and Mirror system to handle the new distribution
The ISOs and ftp tree needs to be set to be publish=en... -
- All packages that hardcode the distribution version somehow need to be updated with the current version number
* o... -
- update job group for new release: https://openqa.opensuse.org/parent_group_overview/3
adjust description and link ... -
- Leap 15 uses leap150 in release counters. Need to discuss with mls again if that is useful as it's a downgrade for al...
-
- we should have some openSUSE-release-appliance package with e.g. flavor(appliance) to separate real installations fro...
Also available in: Atom