Login | Register
My pages Projects Community openCollabNet

Discussions > dev > [Subclipse-dev] Release and branch plans

subclipse
Discussion topic

Hide all messages in topic

All messages in topic

Re: [Subclipse-dev] Release and branch plans

Author markphip
Full name Mark Phippard
Date 2009-02-18 14:02:18 PST
Message I have made these changes. I am holding off on 1.4.8 for now, because
I just saw a Subversion 1.5.6 release may happen next week. I'd
rather just do one release.

So maybe, I will put out a 1.6.0 release before then, depending on
when 1.6 RC comes out.

Mark



On Wed, Feb 18, 2009 at 11:35 AM, Mark Phippard <markphip at gmail dot com> wrote:
> Subversion 1.6 RC process is started and the first RC should be out
> soon. The major change in SVN 1.6 for Subclipse is the tree conflicts
> feature. This has required a lot of new work to support the feature
> and the changes in the notifications etc. Here is my overall release
> plan.
>
> * Wrap up review and applying recent patches that have come in.
> * Make a 1.4.x branch from trunk and cut 1.4.8 release from branch.
> * Merge the current tree-conflicts branch to trunk and issue a 1.6.0
> release from trunk.
>
> 1.6 release will require SVN 1.6. It will not currently support
> SVNKit. I am pretty sure I already have the plugin dependencies right
> so that we can trust our 1.6 release to not try to load older versions
> of our plugins for JavaHL etc. If not, I will fix this for 1.4.8.
>
> Since trunk will be tracking the new release and SVN 1.5 support is
> likely to be needed for a while, we will keep the 1.4.x branch
> supporting SVN 1.5 clients and we will be agressive in backporting
> fixes to that branch and issuing new releases.
>
> But as always, work should be done on trunk and only backported to the
> release branch.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>



--
Thanks

Mark Phippard
http://markphip.blogspot.com/

Re: [Subclipse-dev] Release and branch plans

Author markphip
Full name Mark Phippard
Date 2009-02-18 09:28:27 PST
Message On Wed, Feb 18, 2009 at 12:14 PM, jcompagner <jcompagner at gmail dot com> wrote:
> is it needed that subclipse 1.6 will require on the server SVN1.6?
> cant it also supported lower version on the server like 1.5?

No, it will not need 1.6 on the server. In fact, none of the new
features in 1.6 require this (with the exception of some new
repository storage options which are invisible to clients). But from
the standpoint of a client, the new features will work against any SVN
server version.

> Because that would really block me from using subclipse 1.6 it is not that i
> dont want SVN1.6
> but i dont control all the servers where i have connections too. Some could
> be 1.6 others will stay at 1.5 for a while.

SVN 1.6 does bring a new WC format to support the tree conflicts
feature, so the main issue, as always, will be that you cannot mix SVN
clients on the same WC.

--
Thanks

Mark Phippard
http://markphip.blogspot.com/

Re: [Subclipse-dev] Release and branch plans

Author jcompagner
Full name jcompagner
Date 2009-02-18 09:14:35 PST
Message is it needed that subclipse 1.6 will require on the server SVN1.6?
cant it also supported lower version on the server like 1.5?

Because that would really block me from using subclipse 1.6 it is not that i
dont want SVN1.6
but i dont control all the servers where i have connections too. Some could
be 1.6 others will stay at 1.5 for a while.

johan

On Wed, Feb 18, 2009 at 17:35, Mark Phippard <markphip at gmail dot com> wrote:

> Subversion 1.6 RC process is started and the first RC should be out
> soon. The major change in SVN 1.6 for Subclipse is the tree conflicts
> feature. This has required a lot of new work to support the feature
> and the changes in the notifications etc. Here is my overall release
> plan.
>
> * Wrap up review and applying recent patches that have come in.
> * Make a 1.4.x branch from trunk and cut 1.4.8 release from branch.
> * Merge the current tree-conflicts branch to trunk and issue a 1.6.0
> release from trunk.
>
> 1.6 release will require SVN 1.6. It will not currently support
> SVNKit. I am pretty sure I already have the plugin dependencies right
> so that we can trust our 1.6 release to not try to load older versions
> of our plugins for JavaHL etc. If not, I will fix this for 1.4.8.
>
> Since trunk will be tracking the new release and SVN 1.5 support is
> likely to be needed for a while, we will keep the 1.4.x branch
> supporting SVN 1.5 clients and we will be agressive in backporting
> fixes to that branch and issuing new releases.
>
> But as always, work should be done on trunk and only backported to the
> release branch.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> --------------------​--------------------​--------------
>
> http://subclipse.tig​ris.org/ds/viewMessa​ge.do?dsForumId=1043​&dsMessageId=118​6893
>
> To unsubscribe from this discussion, e-mail: [
> dev-unsubscribe@subc​lipse.tigris.org].
>
Attachments

[Subclipse-dev] Release and branch plans

Author markphip
Full name Mark Phippard
Date 2009-02-18 08:35:31 PST
Message Subversion 1.6 RC process is started and the first RC should be out
soon. The major change in SVN 1.6 for Subclipse is the tree conflicts
feature. This has required a lot of new work to support the feature
and the changes in the notifications etc. Here is my overall release
plan.

* Wrap up review and applying recent patches that have come in.
* Make a 1.4.x branch from trunk and cut 1.4.8 release from branch.
* Merge the current tree-conflicts branch to trunk and issue a 1.6.0
release from trunk.

1.6 release will require SVN 1.6. It will not currently support
SVNKit. I am pretty sure I already have the plugin dependencies right
so that we can trust our 1.6 release to not try to load older versions
of our plugins for JavaHL etc. If not, I will fix this for 1.4.8.

Since trunk will be tracking the new release and SVN 1.5 support is
likely to be needed for a while, we will keep the 1.4.x branch
supporting SVN 1.5 clients and we will be agressive in backporting
fixes to that branch and issuing new releases.

But as always, work should be done on trunk and only backported to the
release branch.

--
Thanks

Mark Phippard
http://markphip.blogspot.com/
Messages per page: