This is the plan for integration of the GNOME 2.20 release into factory/10.3.
As you know, the GNOME-2.20 release date is Wednesday, September 19. These updates will clearly not make RC1 but they will make it in for RC2 and/or the final build of 10.3.
The upstream GNOME tarballs, however, are due on Monday, September 17. Which means the GNOME packaging team at Novell will be starting to submit the updates to factory next Monday, and will declare it finished on Wednesday.
Keep in mind that GNOME-2.20 has been in hard code freeze since September 10 with only a few code changes approved by the release team since then. These updates will largely be no-ops (just a version bump) and translation or doc updates.
This is the plan:
We have the package list here: http://spreadsheets0.google.com/ccc?key=pXWjzV1g7sCqH0NY9PgddOg&hl=en_GB
It is a public doc, editable by the SUSE team.
sbrabec will start early in Prague, followed by mw, mauropm and myself in the US. We will update spreadsheet to indicate that a package is being worked on, and then mark it as updated once submitted to our internal build system. We may even solicit some help from other well known packaging superstars such as jpr, coolo, etc.
We will be taking the tarballs from upstream as they are submitted by the maintainers to the FTP tree; grabbing them from here, as that's where they show up the quickest: http://ftp.acc.umu.se/pub/gnome/sources/
When you build packages place them in $HOME/Export/yyyy/mmdd/arch so others building packages can pull them into the $BUILD_ROOT with --prefer-rpms
We're all looking forward to a great 10.3!
-los paqueteros (mw,mauropm, gekker)
On Fri, 2007-14-09 at 09:51 -0600, Gary Ekker wrote:
When you build packages place them in $HOME/Export/yyyy/mmdd/arch so
others building packages can pull them into the $BUILD_ROOT with --prefer-rpms
I feel horribly pedantic for even bringing this up :), but you put an extra slash there: I use $HOME/Export/yyyymmdd/arch.