[gjs] (2 commits) Created branch gnome-3-10
The branch 'gnome-3-10' was created. Summary of new commits: 5787be8... build: dist-xz is the new black 49ae623... Release 1.38.0 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: About the role of the Release (again)
On Mon, 2013-08-05 at 23:27 +0200, Matthias Clasen wrote: We have been quite a bit more active in setting direction, in the past year. Big decisions: - replacing fallback mode by classic mode - wayland Yes...but we're talking about like the nautilus redesign that wasn't posted or discussed in that way. I have the impression that the current discussion is about unhappiness in certain circles with decisions that have been made in individual modules. I have zero interest in turning the release team into a commit police, and I'm not going to participate in that kind of activity. Right, I don't think anyone wants to be the commit police. I think the role has to be structured such that changes *always* conceptually go through the design/release team i.e. we treat the git repos as pull requests, and both teams are consistently active in looking at the commits and assisting. Would that work? It'd be a big change from the modules are maintainer fiefdoms model, but I do think ultimately if we're talking about doing something here, that's what would have to change. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: About the role of the Release (again)
On Mon, 2013-08-05 at 19:17 +0200, Piñeiro wrote: IMHO, the first thing to debate if we are willing to expand our role and scope, assuming that is what the Foundation members want us to do. If we are, then let's ask the community if that is what they want. If not, we should document with more detail what we are, what we do, and how far we will go on our duties. I mention how far because that was raised by Colin on our meeting here at GUADEC with the specific example of bluez migration. Yeah...though I do think for that one our best bet is to highlight both the benefits of the transition (and the drawbacks). When there is a strong difference of opinion related to a change made within a core GNOME module, the Release Team has the authority to serve as mediator in the hopes of finding a solution which is agreeable to all parties. Failing that, the Release Team has the authority to veto the inclusion of the change in GNOME releases. I think it's our role to *always* be involved to some degree. Not that anyone is full time, but I mean the job naturally involves mediation since there are so many parts. A lot hinges here on what veto means. git revert? Letting the change stand in master and shipping an earlier branch? I guess some modules (mainly apps) could be dropped entirely. And of course ultimately, downstreams have their own veto. How would we decide? Would we vote? I know that I mentioned at the meeting we should consider possibly shipping earlier versions of things, but now that I consider it...there are a lot of details. Presently the release-team emits the modulesets with tarballs...so the natural tendency would lead us to something like earlier releases in there. But if it's not a short term thing, then it's a fork, and that leads us to the need for a git branch...but theoretically the maintainers are in control of the git repository. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: release team meeting
On Tue, 2013-05-14 at 18:06 +0200, Frederic Peters wrote: Or shall we try weekdays (that's probably a question to Matthias and Colin because of timezones)? Sat18Sun19Sat25Sun26Sat01Sat02 andre-- -- ?? ?? ?? ?? fred ok ok -- ok ok ok I'm OK with any date, and am quite flexible on time. Though I'd generally prefer Sunday over Saturday. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[gnome-session] Created branch gnome-3-8
The branch 'gnome-3-8' was created pointing to: 6e14faf... GsmAutostartApp: Don't return NULL from constructor, use GI ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[gobject-introspection] Created branch gnome-3-8
The branch 'gnome-3-8' was created pointing to: 0e708e9... Release 1.36.0 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: 3.9/3.10 Release Schedule Draft
On Thu, 2013-03-28 at 02:10 +0100, Andre Klapper wrote: I've dropped a quick draft at https://live.gnome.org/AndreKlapper/Sched1 Not totally happy about a release on May 1st (holiday) yet. As usual, quick feedback welcome, otherwise I'll announce it to d-a-l. I get You are not allowed to view this page. (logged in as walters). ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
glib freeze break request
Hi, https://bugzilla.gnome.org/show_bug.cgi?id=696014 This is pretty critical for ostree since it makes /etc/shadow world-readable. It can still be a less severe security issue in some cases such as making files in your home directory world-readable if they weren't originally. I've tested this patch a lot and believe it's quite low risk. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: gnome-shell hard code freeze break request
On Fri, 2013-03-22 at 05:44 -0400, Matthias Clasen wrote: On Thu, Mar 21, 2013 at 2:01 PM, Colin Walters walt...@verbum.org wrote: https://bugzilla.gnome.org/show_bug.cgi?id=691987 I'd characterize the risk of this change as low/medium. I tested the change of course (in gnome-ostree FWIW) but it's a nontrivial change to a nontrivial part of the code. The benefit is that we're less likely to leave the user's session in an unlocked state. I have been pushing to get this merged before, but I think we should leave this to 3.8.1 at this point. Ok. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
g-s-d code freeze break
gnome-settings-daemon's media keys plugin was broken: https://bugzilla.gnome.org/show_bug.cgi?id=696114 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break request: Rename .desktop files back to the 3.6 filenames
On Wed, 2013-03-13 at 12:49 -0400, Jeremy Bicha wrote: gnome-calculator and several of the gnome-games have been renamed this cycle (five-or-more, four-in-a-row, gnome-chess, gnome-klotski, gnome-mahjongg, gnome-mines, gnome-nibbles, gnome-robots, and tali). The issues this causes had been previously discussed [1] but we did not come to a final resolution. Hmm...this is just the games and the calculator? That seems relatively low risk to me, so 1/2 from the RT. However long term this is really just a hackaround for the fact that we don't have clear namespacing. Long term hopefully we can make everything look like e.g. org.gnome.Calculator (.desktop). ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
gnome-ostree now doing smoketests too
Hi, I wanted to highlight this: http://ostree.gnome.org/work/tasks/smoketest/current/output.txt The gnome-ostree system is now actually *testing* as well as building. The smoke test is presently fairly basic - it just sets up GDM for auto-login and boots. The source code is here: http://git.gnome.org/browse/gnome-ostree/tree/src/js/tasks/task-smoketest.js The nice thing about this test though is that unlike e.g. the screenshot checksums the OpenSUSE QA does, this test looks for unique MESSAGE_IDs in log files and thus should require no human maintenance over time. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: GNOME 3.7.90 beta release -- walters
Just a followup on this - if anyone else can help out, that'd be much appreciated. I'm unfortunately stuck behind a *very* *very* crappy hotel internet connection, like 10 k/s. On Sun, 2013-02-17 at 00:00 +, Release Team wrote: Hello all, GNOME 3.7.90 beta release For more information about 3.7, the full schedule, the official module lists and the proposed module lists, please see our colorful 3.7 page: http://www.gnome.org/start/unstable For a quick overview of the GNOME schedule, please see: http://live.gnome.org/Schedule Thanks, ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: About python 3.2vs3.3 and jhbuild working for Ubuntu LTS
On Fri, 2012-11-30 at 13:32 +0100, Piñeiro wrote: * Do we have an agreement to keep jhbuild working on last Ubuntu LTS? Historically, we've tried to keep jhbuild working on current stable versions of popular distributions. This is not always easy. Now honestly, I bet Ryan would be OK if Orca merely built, so he could say that all of jhbuild compiles. Whether or not it works at runtime is a different thing. There's also the fact that Orca is not in the critical path so to speak. Were it say GTK+ that had a hard dependency on Python 3.3, it'd be a quite different thing. Ultimately I'd say this is up to the Orca maintainers. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: harfbuzz commit 66ac2ff32e24f0d5658ca172147613081a133847
[cc release-team@ for notification] On Thu, 2012-11-15 at 00:23 -0800, Behdad Esfahbod wrote: Ugh. Pushed a fix to master, that will match the next harfbuzz release. The code in question is deprecated, and I need to find a way to phase it out more seriously. Thanks! So this actually introduced another problem because jhbuild is still using harfbuzz 0.9.5 (and pango master), while the gnome-ostree builder is tracking harfbuzz master and pango master. I'm trying to switch the jhbuild to track harfbuzz master too. Is this right? Or do you think we should just use harfbuzz releases? ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: continuing last weekends meeting
Any conclusion on this? Piñeiro apinhe...@igalia.com wrote: On 10/31/2012 03:43 PM, Javier Jardón wrote: Hi, On 31 October 2012 21:20, Olav Vitters o...@vitters.nl wrote: On Wed, Oct 31, 2012 at 07:37:00AM -0400, Matthias Clasen wrote: We didn't get to many important things last weekend, like fallback mode, feature review, etc. Shall we continue the meeting next weekend, same time ? Or what is the next possible time for everybody ? Id would prefer Sunday if possible And in my case I would prefer Saturday :| (except Saturday 10, that I'm also busy). BR -- Alejandro Piñeiro Iglesias ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: continuing last weekends meeting
On Wed, 2012-10-31 at 23:43 +0900, Javier Jardón wrote: Hi, On 31 October 2012 21:20, Olav Vitters o...@vitters.nl wrote: On Wed, Oct 31, 2012 at 07:37:00AM -0400, Matthias Clasen wrote: We didn't get to many important things last weekend, like fallback mode, feature review, etc. Shall we continue the meeting next weekend, same time ? Or what is the next possible time for everybody ? Id would prefer Sunday if possible Same here, but I can do either. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: moving gnome-power-manager to apps
On Tue, 2012-10-23 at 22:09 -0400, Matthias Clasen wrote: Nowadays, the gnome-power-manager module only includes the gnome-power-statistics app. Therefore, it should be moved to the apps moduleset. Yay, one less bit of crap in the Applications list in gnome-ostree. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Requiring systemd for the gnome-settings-daemon power plugin
On Fri, 2012-10-19 at 15:48 +0200, Bastien Nocera wrote: I would recommend that gnome-shell uses systemd to suspend, and I would recommend gnome-shell, gnome-session and gdm also drop their ConsoleKit session tracking code. At the end of the day, the decisions are not mine to make, so if the costs of keeping those options are low enough for you, then feel free to keep them. But in reality, the set of git repositories forms a whole. And if gnome-settings-daemon doesn't support !systemd, then the whole doesn't either. So if you decide to delete this code from g-s-d, it makes the work of anyone else completely pointless. Broadly speaking, I don't think it makes sense for this to be up to individual module maintainers as they please, because the result is incoherent. Now, this is obviously not a new debate. One option which I'd like to preserve at least is that !systemd platforms are able to build and run GNOME in basic window management mode. Basically the equivalent of thin client/remote X display. So we could say we don't support power management for example. In that case, you could support being compiled without systemd support (at present), and just do nothing if it doesn't exist. Or it could be runtime detection. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Requiring systemd for the gnome-settings-daemon power plugin
The other thing we can do (and really should do) is share more code relating to systemd/CK and in general system abstractions. It's really pretty silly how hard we make it to share code between gnome-settings-daemon and gnome-shell. I'd be happy to move more stuff into to gnome-desktop personally. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[gnome-desktop] Created branch gnome-3-6
The branch 'gnome-3-6' was created. Summary of new commits: ccd9313... Release 3.6.1 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break request for GNOME Shell
On Fri, 2012-10-05 at 17:52 +0200, Florian Müllner wrote: Hey, looks like I have to request another UI freeze break for GNOME Shell :-) https://bugzilla.gnome.org/show_bug.cgi?id=685201 is about a UI glitch in the login screen that was accidentally introduced when updating the lock screen style. Rather than just fixing the glitch in question, we think it makes sense to slightly change the layout and thereby bring it closer to the lock screen (and design mockups) - the change boils down to moving the password entry from its current position next to the user's avatar to a new one below avatar / username as in the lock screen[0]. Kind of a nontrivial amount of code change, but if it's been tested I'm OK with it. So that's RT 2/2 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[gobject-introspection] Created branch gnome-3-6
The branch 'gnome-3-6' was created pointing to: 460cef9... Release 1.34.0 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[gjs] Created branch gnome-3-6
The branch 'gnome-3-6' was created pointing to: 1f5d7a8... Release 1.34.0 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Gtk+ hard code freeze break request
On Wed, 2012-09-19 at 16:22 +0200, Marek Kasik wrote: Hi, I would like to commit patch http://bugzilla-attachments.gnome.org/attachment.cgi?id=224615 from https://bugzilla.gnome.org/show_bug.cgi?id=679883 to Gtk+ 3.5.x yet. RT 1/2 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: String freeze request for GNOME Shell
On Tue, 2012-09-18 at 14:02 +0200, Florian Müllner wrote: Hey, sorry for being late on this, but the patch in question depended on a Mutter change that only landed today. I'd like to commit the remaining patch in https://bugzilla.gnome.org/show_bug.cgi?id=671010, which will make the keybinding definitions for the screen recorder and the message tray show up in the keyboard shortcuts section in System Settings. Cross-module changes like this are tricky. Had to refresh my memory for how keybindings work - this X atom indirection is certainly tricky. Anyways, I don't see anything wrong with it. The strings aren't highly visible, but we should still see what the i18n people say. RT 2/2 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break request - IBus Anthy input source menu items
On Tue, 2012-09-18 at 14:18 +0200, Rui Tiago Cação Matos wrote: Hi, I'd like to request a freeze break for https://bugzilla.gnome.org/show_bug.cgi?id=682314 . This only has an impact for users of the Japanese input method by adding a few common entries to the input sources panel menu which allows users to switch between hiragana/katakana input modes and other similar knobs which are important for this input method's users. It's not entirely clear to me what the problem we're solving here is. Is it that some input engines have undesired action items? This is a quite nontrivial patch, but on the other hand, it just affects a subset of input methods support. I'd be happiest knowing that an active user tested this patch and it worked. But here's my tentative RT 1/2. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: 3.7 Schedule proposal
On Fri, 2012-09-14 at 02:15 +0200, Andre Klapper wrote: Please see https://live.gnome.org/AndreKlapper/Sched1 Nothing special, exactly the same as the 3.3 one. I get You are not allowed to view this page. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: String freeze break request for gnome-panel user menu
On Sun, 2012-09-09 at 08:45 -0400, Jeremy Bicha wrote: Hi, I'd like to request a string freeze exception for gnome-panel to bring the user menu more in line with the GNOME Shell 3.6 user menu. http://bugzilla-attachments.gnome.org/attachment.cgi?id=223834 Specifically, the patch removes the ellipses and changes Shut Down to Power Off. If it's exactly in line, that should be trivial for translators. RT 1/2 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Missing gnome-deskop 3.5.90 release
On Wed, 2012-08-22 at 10:19 +0200, Luca Ferretti wrote: Hi, currently we are missing an update gnome-desktop release. Latest is 3.5.5 but gnome-control-center needs gnome-desktop = 3.5.6. Could someone take care of it? Yeah, sorry I made one but forgot to upload it =) Thanks Frédéric! ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: recent nautilus changes [Re: 20120711 meeting minutes]
On Fri, 2012-07-27 at 10:12 +0200, Frederic Peters wrote: Recent discussions about Nautilus = We'll talk about it on the mailing list. jjardon will send an email. As I have been asked about this I'll note here that we discussed it in our live meeting a GUADEC yesterday; we concluded Andre will make sure there are individual bug reports about the different changes and mark them so we can evaluate the situation before 3.6.0 (off the top of my head, sushi integration, search in same directory, compact view, split view). I talked to Cosimo, and he'll do a blog entry. I'm also following up directly with some people like Adam to see whether they've had a chance to try the latest code, etc. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: meeting materials: what is gnome
On Wed, 2012-07-11 at 10:50 -0400, Matthias Clasen wrote: Since I put this on the agenda, I should provide some input. Here is a document (largely written by Ryan Lortie, with some edits and clarifications by me), which I would like us to adopt as a working definition for what it is that we release as the release team. At a high level, what are we trying to accomplish? It sounds like you were motivated by defining release better. But if we're trying to define GNOME, isn't that already covered by existing material like http://www.gnome.org/about/ ? If not, why not? On the contents of the document itself, first - it *must* mention Free Software. Of course, people here are of diverse motivations, but if it's not Free Software, it can't be part of GNOME. Or maybe this document isn't trying to *define* principles, it's more just attempting to *describe* the state of things as they happen to be today. This is the difference between the Declaration of Independence and a news article written about the event. But if it's just attempting to be descriptive, then it's going to have to change over time, and we can't really use it as *guidance*, which it seems like is the goal. For example, even just one more talented, motivated hacker working on GTK+/win32 could significantly shift the reality of the statement Most of the people hacking on GLib and GTK+ have expertise in programming for Linux-based systems. . Marc-André Lureau may even be on his way to being that person... ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Next R-T meeting
On Wed, 2012-07-04 at 03:08 +0900, Javier Jardón wrote: Time for another release team meeting!! Both dates are OK for me. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: bumping the pulseaudio requirement
On Thu, 2012-06-28 at 15:37 -0400, Matthias Clasen wrote: We have a nice sound panel simplification incoming in https://bugzilla.gnome.org/show_bug.cgi?id=674831 which relies on pa 2.0 api to get rid of the 'Hardware' tab. I propose that we bump the pulseaudio requirement to 2.0 so we can land this nice improvement. Pulseaudio 2.0 was released 2 month ago, which is admittedly fairly recent, but I suspect that 1.99.1 from March has all the required API already. The main issue is the impact on people using jhbuild on last stable distribution such as Ubuntu 12.04 or Fedora 17. Does pulseaudio build from jhbuild on those systems? Actually even trickier, can you build programs against the pulseaudio 2.0 libraries, but run gnome-shell --replace on a system which is running an older pulseaudio daemon? (We can punt on these issues of course, as we have in the past in some cases, but anything that breaks jhbuild on stable distributions has a serious negative impact on the workflow of a lot of contributors) ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
3.6: folks and e-d-s
I'm disabling the folks eds backend for now to keep the 3.6 build working. https://bugzilla.gnome.org/show_bug.cgi?id=675121 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: valadoc patch for jhbuild moduleset
On Wed, 2012-06-06 at 13:01 -0600, Jeremy Whiting wrote: Hello, In order for make distcheck to work in folks, valadoc is required, which isn't in the gnome moduleset in jhbuild. I've attached a patch to add it to gnome-suites-core-deps-3.6.modules. Looks like it has a dependency on libgvc which your patch is missing (it's also missing a dependency on other things like gmodule, but I know where to find those). ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: valadoc patch for jhbuild moduleset
On Wed, 2012-06-06 at 13:48 -0600, Jeremy Whiting wrote: Ah, libgvc is part of graphviz. Not sure if that's in jhbuild modules or not. I couldn't see it, so just installed graphviz from my distro and it built after that. jhbuild is not consistent about having external dependencies marked[1] but it'd help to at least try adding it. If you want to do this right in modern jhbuild since system dependencies landed, you can add graphviz as a module, and hopefully it has a pkg-config file. If so, then jhbuild will reuse the graphviz-dev or whatever from the distribution if available. Look at say nspr or libcroco for an example of an external tarball with a pkg-config element. [1] the dependency information in the moduleset is an out of date cache of the stuff in configure.ac in practice, which is really also an often out-of-date cache of the dependencies in the actual source code. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: valadoc patch for jhbuild moduleset
On Wed, 2012-06-06 at 16:39 -0600, Jeremy Whiting wrote: Ok, here's a new patch that seems to work here. Thanks for the pointers. The patch looks OK; thanks! But would you mind writing a commit message and submitting in git format-patch style? See https://live.gnome.org/GnomeLove/SubmittingPatches I don't mind too much doing it manually, but if you already have a git checkout, it's just a small step going from 'git diff' to 'git commit -a; git format-patch -1' If you're unfamiliar with git, I don't mind doing it, but it's well worth learning if you plan to submit more than one patch, which hopefully you do =) Thanks! ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Next r-t meeting
On Tue, 2012-04-24 at 12:14 +0100, Javier Jardón wrote: On 24 April 2012 10:21, Frederic Peters fpet...@gnome.org wrote: Andre Klapper wrote: Time for another release team meeting? Proposing 17:00UTC (19:00CEST). Add if you are available: Date: | Sat05 | Sun06 | Sat12 | Sun13 Alejandro | ✔ ✔ Andre | ✔ ✔ ✔ ✔ Colin | ✔ ✔ ✔ ✔ Frederic | ✔ ✔ ✔ ✔ Javier|✔ ✔ ✔ Kjartan | Luca | Matthias | ✔ ✔ ✔ ✔ Olav | ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Request freeze break for: fail whale extensions list looks bad
On Wed, 2012-03-21 at 07:51 -0400, Jasper St. Pierre wrote: Nothing too impressive. Just looks like: http://i.imgur.com/8SxPW.png (only with the new string and without the window decoration) That looks like the old ui? Anyways, patch looks OK, and clearly the old UI was insane, so: r-t approval 1/2 ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: meeting?
On Wed, 2012-02-29 at 17:01 +0100, Andre Klapper wrote: As usual I can do every day but Thursday. fredp andre walters 5× × x 6x 7× × 8× × x 9x 10× × x 11× × x ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: meeting?
On Thu, 2011-12-08 at 14:50 +0100, Andre Klapper wrote: On Thu, 2011-12-08 at 13:46 +, Javier Jardón wrote: It would be good to have a rt meeting before the end of the year, last meeting was on a Saturday, let's make this one on a weekday, next week? fredp elleuca jjardon andre walters 12× x × x 13 x - x 14x × x 15× x × x 16×x × x ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: gnome-shell freeze break request
On Mon, 2011-09-26 at 20:35 +0200, Florian Müllner wrote: Hey, we have a reported crasher bug[0] for which I'd like to push a quick fix; the patch is small and I consider it safe (given that it does not change the normal non-error code path), though a proper solution requires some investigation and would hopefully be included in time for 3.2.1. Discussed this on IRC; +1 from me given testing from the reporter. ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break request for gnome-shell
On Thu, 2011-09-22 at 15:57 +0200, Florian Müllner wrote: Hey, I'd like to request a freeze break for the following bug: https://bugzilla.gnome.org/show_bug.cgi?id=659827 Approval 2/2 ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break request for libpeas
On Thu, 2011-09-22 at 18:46 +0200, Nacho wrote: We need to change local to 0. You can see the reason for this in the BIND_LOCAL is basically always a terrible idea. So I'm fine with this patch...but someone really should do the digging for why it was changed in the first place. So that's 1/2 approvals. ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Next meeting [WAS: Re: GNOME 3.1.5 unstable tarballs due (and more)]
2011/8/25 Javier Jardón jjar...@gnome.org: On 25 August 2011 17:06, Andre Klapper ak...@gmx.net wrote: On Thu, 2011-08-25 at 17:38 +0200, Frederic Peters wrote: Luca Ferretti wrote: What about a non-weekend meeting? For instance August 31 o September 1, at 8PM UTC? So, this weekend looks impossible. I'll be at my sister's wedding, so can't make it on the weekend either. 31/8 1/9 Fred × × andre × × Javier x - walters x x But these days seem fine. ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: polkit-gnome and deprecated GtkHBox [WAS: Re: Any big problem? [WAS: Re: GNOME 3.1.4 unstable release -- walters-mclasen]]
On Tue, Aug 16, 2011 at 5:10 PM, David Zeuthen zeut...@gmail.com wrote: Done, just released version 0.102. Btw, Colin's patch didn't have the intended effect so I committed another fix so tarball builds don't default to --enable-default. Hm, yes it looks like you needed GNOME_MAINTAINER_MODE_DEFINES, and my patch is irrelevant. I ended up changing the jhbuild release scripts to explicitly specify --disable-maintainer-mode. ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
GNOME 3.1.4 Development Release
GNOME 3.1.4 Development Release = This is the fourth development release of the 3.1 cycle. There are some new notable features like a new media handling UI, but mainly infrastructural work. A number of modules I know didn't roll a tarball for 3.1.4 but nevertheless have exciting stuff in git - for example, gdm. The current list of notable features in progress for GNOME 3.2 is here: https://live.gnome.org/ThreePointOne/Features Remember, this is still an early development release. There are some known issues: seed crashes: https://bugzilla.gnome.org/show_bug.cgi?id=653903 To compile this release, you can the jhbuild [1] modulesets [2] (which use the exact tarball versions from the official release): [1] http://library.gnome.org/devel/jhbuild/ [2] http://download.gnome.org/teams/releng/3.1.4/ The release notes that describe the changes between 3.1.3 and 3.1.4 are available. Go read them to learn all the goodness of this release: core - http://download.gnome.org/core/3.1/3.1.4/NEWS apps - http://download.gnome.org/apps/3.1/3.1.4/NEWS The GNOME 3.1.4 release is available here: core sources - http://download.gnome.org/core/3.1/3.1.4 apps sources - http://download.gnome.org/apps/3.1/3.1.4 ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Any big problem? [WAS: Re: GNOME 3.1.4 unstable release -- walters-mclasen]
Ok, we need a new release of PolicyKit: util.o: In function `_polkit_subject_get_cmdline': /home/walters/releases/gnome-apps-3.2/accountsservice-0.6.13/src/util.c:86: undefined reference to `polkit_unix_process_get_uid' util.o: In function `get_caller_uid': /home/walters/releases/gnome-apps-3.2/accountsservice-0.6.13/src/util.c:269: undefined reference to `polkit_unix_process_get_uid' collect2: ld returned 1 exit status David can you do that this weekend please? ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Any big problem? [WAS: Re: GNOME 3.1.4 unstable release -- walters-mclasen]
On Sat, Jul 30, 2011 at 10:30 AM, David Zeuthen zeut...@gmail.com wrote: Why is accountsservice using API from unreleased polkit? I can maybe have something ready on Monday; it's not as easy as just rolling a tarball as there are yet unreviewed patches Because people only build and work from git, and then we have lots of last minute panics when we fail to increment versions in configure.ac scripts? Why can't you just make a tarball from what's there, and get to the unreviewed patches later? ___ release-team@gnome.org http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
