From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [gentoo-dev-announce] Release Engineering meeting tomorrow
Date: Wed, 23 Jan 2008 09:01:52 +0930 [thread overview]
Message-ID: <1201044712.1816.109.camel@orpheus> (raw)
In-Reply-To: <1201040417.8046.37.camel@inertia.twi-31o2.org>
since there's been a lot of discussion lately about releases, I thought
I'd forward this FYI:
On Tue, 2008-01-22 at 14:20 -0800, Chris Gianelloni wrote:
> Apologies for the late notice, but Release Engineering is having a
> meeting tomorrow (Wednesday, January 23rd) at 2000 UTC. The meeting is
> being held on IRC at #gentoo-releng on irc.freenode.net and will be open
> to the public, but will be moderated. A question and answer/open floor
> session will follow the meeting. All users and developers are welcome
> and encouraged to attend.
>
> We will be discussing the following items:
>
> - 2008.0 release time line and goals, features
> - Automated regular internal release builds
> - How to more involve the community in our release process
> - How to more involve the developer community in our release process
> - What do we want to do with the Gentoo Store
> - What financial needs do we have, or where are we hurting for hardware
> - What failed with 2007.1 and what can we do to improve
>
> If you have further ideas that you would like to see discussed, please
> reply on the gentoo-releng@lists.gentoo.org mailing list. We will be
> posting logs of the meeting on the http://www.gentoo.org/proj/en/releng
> project space after the meeting, in case any of you miss it.
>
--
Iain Buchanan <iaindb at netspace dot net dot au>
Where does it go when you flush?
--
gentoo-user@lists.gentoo.org mailing list
parent reply other threads:[~2008-01-22 23:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1201040417.8046.37.camel@inertia.twi-31o2.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1201044712.1816.109.camel@orpheus \
--to=iaindb@netspace.net.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox