On Tue, Sep 01, 2009 at 09:12:20PM +0200, ermo | Rune Morling wrote: > We had an impromptu release crunch in #foresight-qa today where we > discussed potential blockers (user guide, PackageKit not updating > systems?) and how to track the releases going forward. There was some > talk about having such crunches in #foresight-devel instead (to have the > most exposure). What do you think?
i think anything that needs any kind of exposure should be on this list. the irc channels can be pretty busy at times and then they are hard to follow when one is not online. (reading the backlog a few hours ago, after being offline only for a few hours felt like a real chore) > António will be on vacation next week, so we need to think about whether > we want to cut a release within days or hang back and wait until he > returns. if by release mean to promote things from qa to stable then by all means, if it is good enough, do it. if it means a big announcement and all that, then i'd opt for waiting. jesse started working on updating gnome, and there is a reasonable chance that we can have release with gnome soon after the new gnome release is out. greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix searching contract jobs: programming, training and administration - anywhere -- pike programmer working in china community.gotpike.org foresight developer foresightlinux.org open-steam.org unix sysadmin iaeste.(tuwien.ac|or).at caudium.org Martin Bähr http://www.iaeste.or.at/~mbaehr/ is.schon.org _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
