WebSVN 2.0 patches

Hey guys

I see that a lots of patches has been committed to the
WebSVN 
repository. Unfortunately, they are committed to trunk where
I also 
suspect that new & unstable features will be committed
in the future. I 
would like for a 2.0 branch to be created where patches for
2.0 are 
committed. Then, I'll be able to update my WebSVN 2.0
installations 
without waiting for a new version to be released, and
without getting 
new features from the trunk. Is this possible, or should I
consider 
trunk stable so that new features will be developed on
branches?

Best wishes,
Jan Normann Nielsen

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

Hi,

i planned to branch a "stable" 2.0 bugfix tree
soon for exactly the 
reasons you mentioned. To be honest, i nearly did this
yesterday, but 
since there has been no official stable release for some
time now, i was 
hoping to get some more feedback from the WebSVN users
before doing so. 
If there are no more major bugs, i'd like to create a branch
for 
potential bugfixes for the 2.0 release and continue
development of 
version 2.1 on the trunk.

Are there any fixes you'd like to see in a 2.0 branch? Since
there have 
been some smaller changes, maybe it'll also be time for a
2.0.1? What do 
you think?

Best regards,
Sebastian

Jan Normann Nielsen schrieb:
> Hey guys
> 
> I see that a lots of patches has been committed to the
WebSVN 
> repository. Unfortunately, they are committed to trunk
where I also 
> suspect that new & unstable features will be
committed in the future. I 
> would like for a 2.0 branch to be created where patches
for 2.0 are 
> committed. Then, I'll be able to update my WebSVN 2.0
installations 
> without waiting for a new version to be released, and
without getting 
> new features from the trunk. Is this possible, or
should I consider 
> trunk stable so that new features will be developed on
branches?
> 
> Best wishes,
> Jan Normann Nielsen

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

Sebastian Petters / 4wd media skrev:
> Hi,
>
> i planned to branch a "stable" 2.0 bugfix
tree soon for exactly the 
> reasons you mentioned. To be honest, i nearly did this
yesterday, but 
> since there has been no official stable release for
some time now, i 
> was hoping to get some more feedback from the WebSVN
users before 
> doing so. If there are no more major bugs, i'd like to
create a branch 
> for potential bugfixes for the 2.0 release and continue
development of 
> version 2.1 on the trunk.
>
> Are there any fixes you'd like to see in a 2.0 branch?
Since there 
> have been some smaller changes, maybe it'll also be
time for a 2.0.1? 
> What do you think?
All patches that fix problems or usability of the
application, e.g. the 
fix for retrieving all log messages, should be available on
the stable 
branch if you decide to create it.

Being a tool for Subversion, I think one can expect people
using WebSVN 
know how to use Subversion. Therefore, I don't see the point
of making 
releases as they are today. Tags in the repository as they
are today and 
a simple branch (e.g. named 'stable') that people can export
or checkout 
and update should be sufficient. It's much quicker and
easier (in my 
opinion), than going to the homepage, finding the download
page, 
downloading a tarball and unzipping it.

Best wishes,
Jan

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

Tim Armes skrev:
> Hi,
>
> Actually, this is the policy that I put in place ages
ago.  The 
> project page even tells you:
>
> To download the latest version, you should access the
WebSVN 
> subversion repository. The 'tags' folder contains the
official 
> releases of WebSVN. 'trunk' contains the development
version and is 
> used at your own risk.
>
Ok, but please consider creating a "stable" branch
so that it's easy to 
retrieve the current stable version including patches
committed since 
the last stable release tag was created.

Best wishes,
Jan
>
>
> Tim
>
>
> On 30/08/2007, *Jan Normann Nielsen* <listsdubbekarl.dk 
> <mailto:listsdubbekarl.dk>> wrote:
>
>     Sebastian Petters / 4wd media skrev:
>     > Hi,
>     >
>     > i planned to branch a "stable" 2.0
bugfix tree soon for exactly the
>     > reasons you mentioned. To be honest, i nearly
did this
>     yesterday, but
>     > since there has been no official stable
release for some time
>     now, i
>     > was hoping to get some more feedback from the
WebSVN users before
>     > doing so. If there are no more major bugs, i'd
like to create a
>     branch
>     > for potential bugfixes for the 2.0 release and
continue
>     development of
>     > version 2.1 on the trunk.
>     >
>     > Are there any fixes you'd like to see in a 2.0
branch? Since there
>     > have been some smaller changes, maybe it'll
also be time for a
>     2.0.1?
>     > What do you think?
>     All patches that fix problems or usability of the
application,
>     e.g. the
>     fix for retrieving all log messages, should be
available on the stable
>     branch if you decide to create it.
>
>     Being a tool for Subversion, I think one can expect
people using
>     WebSVN
>     know how to use Subversion. Therefore, I don't see
the point of making
>     releases as they are today. Tags in the repository
as they are
>     today and
>     a simple branch (e.g. named 'stable') that people
can export or
>     checkout
>     and update should be sufficient. It's much quicker
and easier (in my
>     opinion), than going to the homepage, finding the
download page,
>     downloading a tarball and unzipping it.
>
>     Best wishes,
>     Jan
>
>    
------------------------------------------------------------
---------
>     To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris
>     <mailto:dev-unsubscribewebsvn.tigris>.org
>     For additional commands, e-mail: dev-helpwebsvn.tigris.org
>     <mailto:dev-helpwebsvn.tigris.org>
>
>
>
>  

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

> Date: Friday 31 Aug 2007 
> From: Jan Normann Nielsen <listsdubbekarl.dk>
> Tim Armes skrev:
> > Hi,
> >
> > Actually, this is the policy that I put in place
ages ago.  The
> > project page even tells you:
> >
> > To download the latest version, you should access
the WebSVN
> > subversion repository. The 'tags' folder contains
the official
> > releases of WebSVN. 'trunk' contains the
development version and is
> > used at your own risk.
>
> Ok, but please consider creating a "stable"
branch so that it's easy to
> retrieve the current stable version including patches
committed since
> the last stable release tag was created.

Agreed, it would be nice to have a stable branch for 2.0.x
that would be the 
base to create the release tags 2.0.1, 2.0.2 etc...

Thant way people can check out the stable branch and update
with svn up 
instead of having to change tags repeatidly.

Best regards,

JP



> Best wishes,
> Jan
>
> > Tim
> >
> >
> > On 30/08/2007, *Jan Normann Nielsen* <listsdubbekarl.dk
> > <mailto:listsdubbekarl.dk>>
wrote:
> >
> >     Sebastian Petters / 4wd media skrev:
> >     > Hi,
> >     >
> >     > i planned to branch a "stable"
2.0 bugfix tree soon for exactly the
> >     > reasons you mentioned. To be honest, i
nearly did this
> >
> >     yesterday, but
> >
> >     > since there has been no official stable
release for some time
> >
> >     now, i
> >
> >     > was hoping to get some more feedback from
the WebSVN users before
> >     > doing so. If there are no more major
bugs, i'd like to create a
> >
> >     branch
> >
> >     > for potential bugfixes for the 2.0
release and continue
> >
> >     development of
> >
> >     > version 2.1 on the trunk.
> >     >
> >     > Are there any fixes you'd like to see in
a 2.0 branch? Since there
> >     > have been some smaller changes, maybe
it'll also be time for a
> >
> >     2.0.1?
> >
> >     > What do you think?
> >
> >     All patches that fix problems or usability of
the application,
> >     e.g. the
> >     fix for retrieving all log messages, should be
available on the
> > stable branch if you decide to create it.
> >
> >     Being a tool for Subversion, I think one can
expect people using
> >     WebSVN
> >     know how to use Subversion. Therefore, I don't
see the point of
> > making releases as they are today. Tags in the
repository as they are
> > today and
> >     a simple branch (e.g. named 'stable') that
people can export or
> >     checkout
> >     and update should be sufficient. It's much
quicker and easier (in my
> >     opinion), than going to the homepage, finding
the download page,
> >     downloading a tarball and unzipping it.
> >
> >     Best wishes,
> >     Jan
> >
> >    
------------------------------------------------------------
---------
> >     To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris
> >     <mailto:dev-unsubscribewebsvn.tigris>.org
> >     For additional commands, e-mail: dev-helpwebsvn.tigris.org
> >     <mailto:dev-helpwebsvn.tigris.org>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
> For additional commands, e-mail: dev-helpwebsvn.tigris.org



-- 
JP Renaud

http://www.jprenaud.info


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

On 2007-08-31 20:45, JP Renaud wrote:
> > > To download the latest version, you should
access the WebSVN
> > > subversion repository. The 'tags' folder
contains the official
> > > releases of WebSVN. 'trunk' contains the
development version and is
> > > used at your own risk.
> >
> > Ok, but please consider creating a
"stable" branch so that it's easy to
> > retrieve the current stable version including
patches committed since
> > the last stable release tag was created.
> 
> Agreed, it would be nice to have a stable branch for
2.0.x that would be the 
> base to create the release tags 2.0.1, 2.0.2 etc...
> 
> Thant way people can check out the stable branch and
update with svn up 
> instead of having to change tags repeatidly.

Better still, treat trunk as "stable" and develop
in branches
then users can have the absolute simplest incremental
upgrade
path, without version numbers...

 cd /path/to/codebase && svn up

MediaWiki offers this "rolling release" upgrade
option.

--markc

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

On Friday 31 Aug 2007, Mark Constable wrote:
> Better still, treat trunk as "stable" and
develop in branches
> then users can have the absolute simplest incremental
upgrade
> path, without version numbers...
>
>  cd /path/to/codebase && svn up
>
> MediaWiki offers this "rolling release"
upgrade option.

You could use the same command line to upgrade from a
2.x-stable 
branch and leave trunk for development. Its a matter of
personal 
preference - except for one important difference. When
3.x-stable 
branches I will not accidentally upgrade to a major new
version when 
I'm not ready to take on the challenges of supporting new
features or 
config file changes.

-- 
> Nick Thompson

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

> Date: Friday 31 Aug 2007 
> From: Nick Thompson <nick.thompsonlsi.com>
> On Friday 31 Aug 2007, Mark Constable wrote:
> > Better still, treat trunk as "stable"
and develop in branches
> > then users can have the absolute simplest
incremental upgrade
> > path, without version numbers...
> >
> >  cd /path/to/codebase && svn up
> >
> > MediaWiki offers this "rolling release"
upgrade option.
>
> You could use the same command line to upgrade from a
2.x-stable
> branch and leave trunk for development. Its a matter of
personal
> preference - except for one important difference. When
3.x-stable
> branches I will not accidentally upgrade to a major new
version when
> I'm not ready to take on the challenges of supporting
new features or
> config file changes.

I personally prefer the trunk for development and branches
for stable 
features. Trunk is used for development purely and the users
checkout a 
release branch so that they can only get bugfixes when
running svn up. As 
Nick mentions if users checkout the trunk as a
"stable" codebase, the next 
time a development branch is merged into the trunk (for 2.1
or 3.0) then they 
will automatically be upgraded to the latest version. maybe
this is the 
desired outcome of such practice though, I don't know 

I think it's quite important for those who don't follow the
development 
closely and might not be aware that what they initially
checked out is now a 
completely new version.

-- 
JP Renaud

http://www.jprenaud.info


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

On 2007-08-31 21:51, JP Renaud wrote:
> I personally prefer the trunk for development and
branches for stable 
> features. Trunk is used for development purely and the
users checkout a 
> release branch so that they can only get bugfixes when
running svn up. As 
> Nick mentions if users checkout the trunk as a
"stable" codebase, the next 
> time a development branch is merged into the trunk (for
2.1 or 3.0) then they 
> will automatically be upgraded to the latest version.
maybe this is the 
> desired outcome of such practice though, I don't know


Yes, that is the idea. The very concept of having major 2.1
to 3.0
upgrade jumps doesn't apply in this case as the codebase
constantly
but gradually morphs. It encourages a different approach to
how a
project is managed and released. I've been using this
approach with
some wikimedia sites and my own projects and I would never
go back
to timed tarball releases. Far too disruptive and
unnecessary.

--markc

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org