Folks,
I'm going to propose something radical. Although Jeff's recent commit points
out
a potentially serious problem (discrepancy between the file size and file
offset types)
in the Win32 APR, which I will look at today, this server appears rather
stable, and
buildable, and rbb will have 't
There are a couple of bugs in the STATUS file that I started hunting
today. Can we shoot for a tarball roll of sometime on Thursday or Friday?
I agree, the no-freeze model just doesn't work in this environment.
Ryan
On Wed, 7 Mar 2001, William A. Rowe, Jr. wrote:
> Folks,
>
> I'm going to
william,
the apache project is, i assume, suffering from the effects of many
developers using cvs at the same time?
if so, can i recommend reading the description of how to ease the pain of
#3 below, described in http://advogato.org/article/247.html
it outlines how to use cvs to do one or more s
I'm tagging and rolling right now. The tree currently builds on Windows
and Linux, and I believe based on Jeff's recent commits, I have to believe
that it compiles everyplace else. It also works on OS/2 and BeOS AFAIK.
Tag and roll coming in the next hour or so.
Ryan
On Wed, 7 Mar 2001, Will
"William A. Rowe, Jr." <[EMAIL PROTECTED]> writes:
> Can we begin a code freeze, excepting _minor_ build and code fixes, until
> we have
> a stable tarball ready to share? I have win32 folks trying to make
> apache2.0a9 build,
> this just doesn't make any sense. Once Ryan's patch is in, let'
> I agree, the no-freeze model just doesn't work in this environment.
The no-freeze model hasn't even been tested in this environment.
It is necessary for the code to be in a stable state in order to do
a release at any time, regardless of a freeze. At no time in the past
six months has the code
> create a release based on an ongoing frantic development tree, all you
> have to do is selectively tag the repository to include only those
> revisions that you consider to be stable. There is no rule that requires
> the entire HEAD to be tagged at once, and there is nothing wrong with
> moving
I don't think it has anything to do with mechanics, nor will throwing more
process at the problem fix it. (more process will simply bog down what we
can accomplish)
No... the problem is about perception. The rate of change recently has just
been quite high. It just isn't very conceivable to make a
On Fri, 9 Mar 2001, Greg Stein wrote:
> I don't think it has anything to do with mechanics, nor will throwing more
> process at the problem fix it. (more process will simply bog down what we
> can accomplish)
...? if nothing else:
cd apr
cvs tag -b apr_dev [needs recursive option]
cd ..
mkdir
On Sat, 10 Mar 2001, Luke Kenneth Casson Leighton wrote:
> On Fri, 9 Mar 2001, Greg Stein wrote:
>
> > I don't think it has anything to do with mechanics, nor will throwing more
> > process at the problem fix it. (more process will simply bog down what we
> > can accomplish)
>
> ...? if nothing e
On Fri, Mar 09, 2001 at 06:54:29AM -0800, [EMAIL PROTECTED] wrote:
> On Sat, 10 Mar 2001, Luke Kenneth Casson Leighton wrote:
> > On Fri, 9 Mar 2001, Greg Stein wrote:
> >
> > > I don't think it has anything to do with mechanics, nor will throwing more
> > > process at the problem fix it. (more pro
> > surely that's not too much process to cause more pain than the benefits
> > are worth, neh?
>
> There is a lot of resistance to using tags and branches the way you
> suggest Luke.
okay: i have to admit - i made a mistake in "oversimplifying" what i
suggested [full branching of an entire sub-t
sorry: this suggestion - a full tagging of an entire project - was a
mistake.
i repeat, i am NOT advocating that the use of branching like this is a
good idea. in fact, it is an extremely dangerous one. imo.
luke
On Sat, 10 Mar 2001, Luke Kenneth Casson Leighton wrote:
> On Fri, 9 Mar 2001, G
> > > _however_ :)
>
> Saw that coming :-)
oh, darn :)
> > > once you _get_ to the point where cvs main is
> > > always-releasable, then using this multi-tag process could help make cvs
> > > main _remain_ always-releasable.
>
> We only need it releasable when we want to release :-)
>
> Serio
> ... i've worked in long-term branches.
>
> i do not recommend it.
afterthought. just to clarify, the above sentence is a serious
understatement.
luke
- Luke Kenneth Casson Leighton <[EMAIL PROTECTED]> -
"i want a world of dreams, run by near-sighted visionaries"
"good. that's them
greg et al,
just to let you know.
i just had to set up, here, a second "partial tag", this time quite
a significant rewrite of my database modules and the way they're being
used in the project i'm doing.
i tagged just the db.py, monitord.py and sql2000xmldb.py files.
i then found whoops, a bug
16 matches
Mail list logo
