[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Patch needed for javahl in release 0.34

From: Jostein Chr. Andersen <jostein_at_josander.net>
Date: 2003-11-29 14:45:42 CET

On Saturday 29 November 2003 11.44, Ben Reser wrote:
> I'll admit I haven't been around much so my opinion probably doesn't
> carry much weight. And perhaps my limited observations are wrong
> about the way things work.

Your opinion counts.

> As it seems to me the release procedures are rather haphazard and
> unclear. It is clear how to make the tarball, but it's unclear how
> the branch is to be handled and what changes qualify as "absoluetely
> necessary."

If the release was done at once after branching, would we have to do a
new x.xx.1 release because of a bug (in this case the merge of r7868?

I would say that if we must make a new release because of a bug/fix, then
the change qualify as "absolutely necessary".
So let's say that we did release 0.34.0 some days ago: -Do we need to
make a 0.34.1 release because of r7868?

> If you follow the notes/releases.txt the CHANGES file, svn_version.h
> etc should have been done before the branch was made.

True, it's me to blame. I hope no one have a problem with this :-)

You have many good points and views in your posting. I'll wait and see
what happends on this list (giving people on the other side of the globe
a chance to say something about it).

Now, I need some time off this subject (I'm starting to loose the focus
on what I shall do here).

Everyone know what I mean here, nothing should be unclear about that.

Jostein

-- 
http://www.josander.net/kontakt/ ||
http://www.josander.net/en/contact/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 29 14:48:32 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.