Small proposal for X11R6.8.2 release schedule / was: Re: Call Today

Roland Mainz <[email protected]>
Newsgroups gmane.comp.freedesktop.release-wranglers
Message-ID <[email protected]>
Jim Gettys wrote:
> 
> Please send agenda items.
> 
> Call Friday, 11:00EDT, 8:00PDT, 5:00PM CDT

Umpf... sorry that I wasn't able to catch the call (the time ) ... ;-(

> Agenda:
> X11R6.8.2 maintenance release
> maintenance release bug nomination/check in policy and process
> can we choose a wrangler for the release?  We have one volunteer, are
> there others?

BTW: Ignore my comment with "...if noone else wants the job ..." - I've
rearranged my work queue that I can spend the whole november with the
X11R6.8.2 release... :)

How do we proceed how ? I'd really like to start working on the branch
as soon as possible, cutting the release schedule in 1-2week pieces -
which are:
1. Nominations for patches (via requesting approval via bugzilla) [one
week from the beginning]
2. Getting the requests triaged per the rules I posted in another email
here [can be done in parallel to [1] and [3]]
3. Getting patches commited [max. two weeks]
4. Getting a release canidate out (after [3] is done)
5. Wait two or three weeks for feedback
6. Integrate feedback
7. Release it

Notes:
- [5] and [6] may need to be repeated multiple times depending on what
is commited per feedback from testers
- I would target mid-december as release date (which means: The release
canidate should be shipped within less than three weeks from today
(erm... yes... I know... it's a _tight_ schedule. But all patches have
been commited to "trunk" already so there shouldn't be a big problem
with that (I am slightly worried about testing on non-maintream
platforms like AIX or IRIX)))

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) [email protected]
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.