1.2b plan of action

[Rob Hartill <ro...@imdb.com>]

"Ah, well, it's no use prevaricating about the bush..."
	- Wallace. "The Wrong Trousers".



(I know this is incomplete. It'll be biassed towards issues I'm aware
of until I see feedback).

Plan for Release of Apache 1.2 beta
===================================

Release Date: Dec 1st '96

Timetable:

	Sunday 17th - end of the day there's a feature freeze. No features
	will be added after that without a fight. Assume that all features
	are vetoed. Features added before the deadline need 3 x +1 votes
	BEFORE being committed.

	Now-24th - send bug patches/reports to the list. Don't commit
	patches until there are at least 3 +1 votes visible on the list.

	Sunday 24th - roll the last pre-beta tarball and make lots of
	noise on the list to get everyone to download it and try exactly
	the same version.

	At any time, send to the list a description of anything that needs
	doing and I'll try to summarise the state of affairs daily if there's
	anything new to report.

	Nov 30th, change the server name to 1.2b, create a public tarball.
	Dec  1st, move tarfile into place. Start a new release timetable
	for 1.2

Assume that only showstopper bugs will change the timetable... don't moan
if your pet project/gripe is overlooked if it can't meet the deadline - if
it has waited this long then it can wait for 1.3; if we can generate momentum,
1.3 could be only a few months away.

I'll try to post daily progress reports and maintain a 'to do' list. If there's
nothing to report, I won't. There's a to do list attached. Please send me
additions or more detail. 

CVS: Those of you with cvs priviliges on hyperreal, please commit whatever gets
approved (3 x +1) and nothing else. Also, what needs to be done CVS-wise
in order to create 1.2b and then prepare for 1.2 ? Let me know so I can put
it on the 'to do' list.

tarballs: Can someone volunteer to create a 1.2b tarball - I get the impression
that this is best done by someone with cvs privs. If there's no volunteer,
please explain the process so that it can be put on the to do list.

documentation: I'm easy on this (for 1.2b). The more the better, but I won't
treat it as a showstopper. If this frightens you, start writing documentation.

Bugs:
	(I know Brian setup a web bugtacking system but last time I tried it
	was way too slow (network delays) to be of any use.
	-=-=-=-=-=-
	SIGUSR1/graceful restarts 

	Problem: Under FreeBSD, this is lethal. USR1 followed by HUP takes down
	te server. Paul S (?) reported annoying processes after a USR1.
	
	Plan: I can't see this getting fixed any time soon so I recommend it
	stays undocumented or gets big flashing warning lights.

	To do: Is there any documentation on this ? If there is, add a huge
	warning. If someone offers some comments for the C source to warn about
	this I'll +1 them.
	-=-=-=--=-=-=-

Showstoppers:
	none


To do:
	ASAP	Find a patch for 'satisfy' that works well (tried and tested)
		 (before feature freeze)
		Prepare more documentation.
		Resolve all outstanding bugs (see above).
	Nov 17	Feature freeze.
	Nov 24	Create last pre-beta tarball.
		Test, test, test.
		Report back with positive as well as negative comments.
	Nov 30	Create 1.2b tarball.
	  "	Update CVS to reflect 1.2b release.
	Dec  1  Release 1.2b.
	  "	Put documentation online if there is any.
	  "	Hand 1.2 management over.



Note: this is how I think we should work to release 1.2b. I'm not making
any rules for future release managers to follow (if we ever have another one).
This is my best plan for 1.2b within the timeframe that most people
appear to agree with (i.e. ASAP).


-- 
Rob Hartill.       Internet Movie Database Ltd.    http://www.imdb.com/  

Re: 1.2b plan of action

[Alexei Kosut <ak...@nueva.pvt.k12.ca.us>]

On Sat, 16 Nov 1996, Rob Hartill wrote:

> (I know this is incomplete. It'll be biassed towards issues I'm aware
> of until I see feedback).
> 
> Plan for Release of Apache 1.2 beta
> ===================================

[...]

Looks good. I have only two nits:

1) Make it 1.2b1, not 1.2b. We should be consistent, and we quite
possibly will need several betas.

2) I am vetoing, right now, any mention of an Apache 1.3. Just get
that thought out of your head right now. After this, it's 2.0 or
bust. That was the agreement we made back in July when we decided to
do 1.2 (and remember, that was supposed to be done by the end of
August).

I'm going to try to work on the 1.2 docs today or tomorrow. Until
someone figures out something better, I'm going on the current plan:
docs/1.2/ has whats-new docs for 1.2. That's all we really need for a
beta, and it's important that we have it. We can rework the full docs
later (as I did for 1.1, just before the release of 1.1.0).

Anyone else find it ironic that we keep releasing things on my
birthday (1.1.0 was on December 1, 1995, and 1.2b1 may now be on
December 1, 1996.)

-- 
________________________________________________________________________
Alexei Kosut <ak...@nueva.pvt.k12.ca.us>      The Apache HTTP Server
URL: http://www.nueva.pvt.k12.ca.us/~akosut/   http://www.apache.org/

Re: 1.2b plan of action

[ra...@vex.net]

> Bugs:
>      (I know Brian setup a web bugtacking system but last time I tried it
>      was way too slow (network delays) to be of any use.

I ran across a new package called PTS.  Here is a blurb on it:

  What is PTS?  PTS is a web-based project/problem management system for use
  in a workgroup situation.  It uses PHP/FI and Msql for all processing, and
  requires no client software beyond a Web browser that supports tables and
  cookies. 

  PTS organizes data into projects, tasks, and followups.  A project has
  basic contact and user informatio, and consists of a list of tasks.  The
  tasks may be assigned, reprioritized, assigned, etc.  Each task has a
  history of followups associated with it, including status changes on the
  task, and other history affecting the it, all viewable through a web
  browser.

I plan on installing it over the weekend and if it doesn't suck too badly,
I can run it on my server here.  It can be had at: 
www.homeport.org/~shevett/pts/

-Rasmus

Re: 1.2b plan of action

[Brian Behlendorf <br...@organic.com>]

On Sat, 16 Nov 1996, Rob Hartill wrote:
> Assume that only showstopper bugs will change the timetable... don't moan
> if your pet project/gripe is overlooked if it can't meet the deadline - if
> it has waited this long then it can wait for 1.3; if we can generate momentum,
> 1.3 could be only a few months away.

Absolutely no 1.3, as Alexei said.  

> Bugs:
> 	(I know Brian setup a web bugtacking system but last time I tried it
> 	was way too slow (network delays) to be of any use.

We need to fix this.  If they are problems I can address, great.  We can
configure it such that folks get mail when a bug is submitted or a status
changed if that would help things.  I just don't see how we can live without
using a real bugtracking system.  Is the network between our places hosed?  I'd
like to know this in general anyways.

There are some unresolved bugs in the database, none of them showstoppers but
we should address them.  

	Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com  www.apache.org  hyperreal.com  http://www.organic.com/JOBS