shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kalle Korhonen <kalle.o.korho...@gmail.com>
Subject Re: [jira] Closed: (SHIRO-102) Set-up AutoExport of Shiro documentation to the appropriate location
Date Wed, 19 May 2010 18:01:56 GMT
On Wed, May 19, 2010 at 10:49 AM, Les Hazlewood <lhazlewood@apache.org> wrote:
> Won't the release plugin automatically create the 1.0.x branch?  That
> way we don't have to worry about it?

You can create a branch using the release plugin with mvn release:branch.

> Unless I'm missing something, it makes sense to me to create a 1.0.x
> because the trunk can be used for new feature (1.1) development -
> there are a few issues slated for 1.1 already and we would be able to
> work on those whenever we want without fear of screwing up the repo if
> there is already a 1.0.x branch, right?  I mean, the idea is that
> 1.0.x won't contain new features since it should be both forwards and
> backwards compatible with any 1.0.x release.  At least this has been
> my favorite way of thinking of releases:

Yes, like I said, creating the branch itself is cheap. It's the
additional overhead - two CI builds, periodic merges and co-ordination
that, while not much, makes sense to defer till the time you actually
need it. All I'm saying is that we can create the branch at any point
later once somebody wants to work on an issue that's targeted for 1.1.
But if you feel strongly about it, I can create the branch right away.

Kalle

Mime
View raw message