Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Re: TSVN release cycles

Project highlights: :. Download .: :. Support .: :. FAQ .: :. Translations .: :. Donate .: :. Report Bug .:

tortoisesvn
Discussion topic

Hide all messages in topic

All messages in topic

Re: TSVN release cycles

Author "Hans-Emil Skogh" <Hans-Emil dot Skogh at tritech dot se>
Full name "Hans-Emil Skogh" <Hans-Emil dot Skogh at tritech dot se>
Date 2010-05-16 23:46:32 PDT
Message >> I've made a copy of the last full nightly build that's linked against
>> svn 1.6.x. So all those who want the new features without having to
>> upgrade their working copies can get them from the nightly builds folder.
> Apologies for being dense, but does that mean that the nightlies under
> the usual win32/full folder are now linked against SVN trunk, rather
> than the 1.6.x branch?

Yes. The regular nightlies now link against SVN trunk.
 
The last nightly that linked against 1.6.x is located here:
http://nightlybuilds​.tortoisesvn.net/lat​est/win32/full-1.6.x​/
 
Hans-Emil
Attachments

Re: TSVN release cycles

Author Daniel Becroft <djcbecroft at gmail dot com>
Full name Daniel Becroft <djcbecroft at gmail dot com>
Date 2010-05-16 16:16:35 PDT
Message On Sun, May 16, 2010 at 7:23 PM, Stefan Küng <tortoisesvn at gmail dot com> wrote:
> On 13.05.2010 10:15, Simon Large wrote:
>
>> This general scheme sounds good to me, but I would go for the new
>> policy regardless of estimated SVN release time frames.
>>
>> But why wait until after the 1.7 release? We could do the same now
>> with a 1.6.10 release branch, although I realise the "plenty of time
>> to inform / educate" will not happen. Realistically 1.7 is still
>> several months away, and based on past release cycles my guess would
>> be another 6 months and there are features on TSVN trunk that people
>> want.
>
> I've made a copy of the last full nightly build that's linked against
> svn 1.6.x. So all those who want the new features without having to
> upgrade their working copies can get them from the nightly builds folder.

Apologies for being dense, but does that mean that the nightlies under
the usual win32/full folder are now linked against SVN trunk, rather
than the 1.6.x branch?

Cheers,
Daniel B.

Re: TSVN release cycles

Author steveking
Full name Stefan Küng
Date 2010-05-16 02:23:04 PDT
Message On 13.05.2010 10:15, Simon Large wrote:

> This general scheme sounds good to me, but I would go for the new
> policy regardless of estimated SVN release time frames.
>
> But why wait until after the 1.7 release? We could do the same now
> with a 1.6.10 release branch, although I realise the "plenty of time
> to inform / educate" will not happen. Realistically 1.7 is still
> several months away, and based on past release cycles my guess would
> be another 6 months and there are features on TSVN trunk that people
> want.

I've made a copy of the last full nightly build that's linked against
svn 1.6.x. So all those who want the new features without having to
upgrade their working copies can get them from the nightly builds folder.

Stefan

--
        ___
   oo // \\ "De Chelonian Mobile"
  (_,\/ \_/ \ TortoiseSVN
    \ \_/_\_/> The coolest Interface to (Sub)Version Control
    /_/ \_\ http://tortoisesvn.net

Re: TSVN release cycles

Author simonlarge
Full name Simon Large
Date 2010-05-13 01:15:30 PDT
Message On 12 May 2010 11:31, Stefan Fuhrmann <stefanfuhrmann@a​lice-dsl.de> wrote:
> Stefan Küng wrote:
>>
>> On 11.05.2010 20:22, Tobias Schaefer wrote:
>> /> On 11.05.2010 19:42, Stefan Küng wrote: /
>> />> Sometime this or maybe next week, the svn library will get rid of
>> the /
>> />> double property handling. That means the speed of the new wc
>> format will /
>> />> finally be so that we can use it. /
>> />> So I'll soon switch the TSVN trunk to link against the svn trunk
>> so I /
>> />> can start implementing the new features. Once that's done, we
>> can't make /
>> />> a TSVN release without waiting for the svn release. /
>> /> /
>> /> You surely mean "can make" ;-) /
>> /> /
>> /> If we link to the svn trunk we will not have a stable Subversion
>> basis /
>> /> for a while and will IMHO not be able to release stable TortoiseSVN
>> builds. /
>> /> /
>> /> Why not release the current TSVN-trunk based on the current 1.6.x
>> branch /
>> /> now (after a short beta)? However, the question is if this will be /
>> /> called 1.6.10, 1.7.0, 2.0, or 2010-05 (see prevision discussions). /
>>
>> Sure, we could do that. But as you know, the previous discussion
>> couldn't come to an agreement about what to call such a release.
>> Every one of the suggestions has at least one big drawback, so basically
>> what we do now seems to be the best solution.
>>
> Maybe, I got yet another idea:
>
> * stick with the SVN release schedule for 1.7
> * once 1.7.0 got released, request a guesstimate for 1.8
>    a) believable 6 month time-frame -> stay in sync w/ SVN
>    b) likely to be 9 month or more -> announce change in TSVN release
> policy
> * new release policy (if applicable):
>    - a feature release about every 6 months
>    - the last feature release may be rather close to the next SVN release
>      (but stop releasing new features when SVN enters stabilization)
>    - name releases closely to SVN version numbering:
>       * 1.8.0, 1.8.1, ... for the initial feature set releases
>       * 1.8.10, 1.8.11, ... for the second feature releases
>       * 1.8.20, etc for the third feature release etc.
>      (we don't release more frequently than every 3 weeks,
>      so patch level numbers won't overlap)
>
> That way we wouldn't appear to change policies at a "whim"
> but have plenty of time to inform / educate users upfront, instead.

This general scheme sounds good to me, but I would go for the new
policy regardless of estimated SVN release time frames.

But why wait until after the 1.7 release? We could do the same now
with a 1.6.10 release branch, although I realise the "plenty of time
to inform / educate" will not happen. Realistically 1.7 is still
several months away, and based on past release cycles my guess would
be another 6 months and there are features on TSVN trunk that people
want.

Simon

--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net

Re: TSVN release cycles

Author galb
Full name Joseph Galbraith
Date 2010-05-12 12:38:15 PDT
Message On 5/12/2010 12:07, Stefan Küng wrote:
> On 12.05.2010 12:31, Stefan Fuhrmann wrote:
>
>> Maybe, I got yet another idea:
>>
>> * stick with the SVN release schedule for 1.7
>> * once 1.7.0 got released, request a guesstimate for 1.8
>> a) believable 6 month time-frame -> stay in sync w/ SVN
>> b) likely to be 9 month or more -> announce change in TSVN release
>> policy
>> * new release policy (if applicable):
>> - a feature release about every 6 months
>> - the last feature release may be rather close to the next SVN release
>> (but stop releasing new features when SVN enters stabilization)
>> - name releases closely to SVN version numbering:
>> * 1.8.0, 1.8.1, ... for the initial feature set releases
>> * 1.8.10, 1.8.11, ... for the second feature releases
>> * 1.8.20, etc for the third feature release etc.
>> (we don't release more frequently than every 3 weeks,
>> so patch level numbers won't overlap)
>>
>> That way we wouldn't appear to change policies at a "whim"
>> but have plenty of time to inform / educate users upfront, instead.
>
> +1 from me.

I like this (or +1 from me too.)

It seems like I just saw something from the SVN crew that
basically said they were giving up on the 6-month release
cycle because the easy problems were solved and they were
now left with problems that just didn't fit a 6-month
release cycle.

Thanks,

Joseph

Re: TSVN release cycles

Author steveking
Full name Stefan Küng
Date 2010-05-12 11:07:19 PDT
Message On 12.05.2010 12:31, Stefan Fuhrmann wrote:

> Maybe, I got yet another idea:
>
> * stick with the SVN release schedule for 1.7
> * once 1.7.0 got released, request a guesstimate for 1.8
> a) believable 6 month time-frame -> stay in sync w/ SVN
> b) likely to be 9 month or more -> announce change in TSVN release
> policy
> * new release policy (if applicable):
> - a feature release about every 6 months
> - the last feature release may be rather close to the next SVN release
> (but stop releasing new features when SVN enters stabilization)
> - name releases closely to SVN version numbering:
> * 1.8.0, 1.8.1, ... for the initial feature set releases
> * 1.8.10, 1.8.11, ... for the second feature releases
> * 1.8.20, etc for the third feature release etc.
> (we don't release more frequently than every 3 weeks,
> so patch level numbers won't overlap)
>
> That way we wouldn't appear to change policies at a "whim"
> but have plenty of time to inform / educate users upfront, instead.

+1 from me.

Stefan

--
        ___
   oo // \\ "De Chelonian Mobile"
  (_,\/ \_/ \ TortoiseSVN
    \ \_/_\_/> The coolest Interface to (Sub)Version Control
    /_/ \_\ http://tortoisesvn.net

Re: TSVN release cycles

Author sf
Full name Stefan Fuhrmann
Date 2010-05-12 03:31:37 PDT
Message Stefan Küng wrote:
>
> On 11.05.2010 20:22, Tobias Schaefer wrote:
> /> On 11.05.2010 19:42, Stefan Küng wrote: /
> />> Sometime this or maybe next week, the svn library will get rid of
> the /
> />> double property handling. That means the speed of the new wc
> format will /
> />> finally be so that we can use it. /
> />> So I'll soon switch the TSVN trunk to link against the svn trunk
> so I /
> />> can start implementing the new features. Once that's done, we
> can't make /
> />> a TSVN release without waiting for the svn release. /
> /> /
> /> You surely mean "can make" ;-) /
> /> /
> /> If we link to the svn trunk we will not have a stable Subversion
> basis /
> /> for a while and will IMHO not be able to release stable TortoiseSVN
> builds. /
> /> /
> /> Why not release the current TSVN-trunk based on the current 1.6.x
> branch /
> /> now (after a short beta)? However, the question is if this will be /
> /> called 1.6.10, 1.7.0, 2.0, or 2010-05 (see prevision discussions). /
>
> Sure, we could do that. But as you know, the previous discussion
> couldn't come to an agreement about what to call such a release.
> Every one of the suggestions has at least one big drawback, so basically
> what we do now seems to be the best solution.
>
Maybe, I got yet another idea:

* stick with the SVN release schedule for 1.7
* once 1.7.0 got released, request a guesstimate for 1.8
    a) believable 6 month time-frame -> stay in sync w/ SVN
    b) likely to be 9 month or more -> announce change in TSVN release
policy
* new release policy (if applicable):
    - a feature release about every 6 months
    - the last feature release may be rather close to the next SVN release
      (but stop releasing new features when SVN enters stabilization)
    - name releases closely to SVN version numbering:
       * 1.8.0, 1.8.1, ... for the initial feature set releases
       * 1.8.10, 1.8.11, ... for the second feature releases
       * 1.8.20, etc for the third feature release etc.
      (we don't release more frequently than every 3 weeks,
      so patch level numbers won't overlap)

That way we wouldn't appear to change policies at a "whim"
but have plenty of time to inform / educate users upfront, instead.
>
> /> Immediately after that TSVN-trunk may be switched to SVN-trunk. /
> /> /
> /> Don't get me wrong. I'm always working with nightly builds from /
> /> TSVN-trunk and am quite comfortable with that, but releasing based on /
> /> Subversion trunk seems a bit risky to me. /
>
> We linked our trunk against the svn trunk before without any problems.
> Of course not for the releases but for the nightly builds. And that's
> what we will do again.
>
Looking forward to it ;)

-- Stefan^2.

Re: TSVN release cycles

Author steveking
Full name Stefan Küng
Date 2010-05-11 12:22:35 PDT
Message On 11.05.2010 20:22, Tobias Schaefer wrote:
> On 11.05.2010 19:42, Stefan Küng wrote:
>> Sometime this or maybe next week, the svn library will get rid of the
>> double property handling. That means the speed of the new wc format will
>> finally be so that we can use it.
>> So I'll soon switch the TSVN trunk to link against the svn trunk so I
>> can start implementing the new features. Once that's done, we can't make
>> a TSVN release without waiting for the svn release.
>
> You surely mean "can make" ;-)
>
> If we link to the svn trunk we will not have a stable Subversion basis
> for a while and will IMHO not be able to release stable TortoiseSVN builds.
>
> Why not release the current TSVN-trunk based on the current 1.6.x branch
> now (after a short beta)? However, the question is if this will be
> called 1.6.10, 1.7.0, 2.0, or 2010-05 (see prevision discussions).

Sure, we could do that. But as you know, the previous discussion
couldn't come to an agreement about what to call such a release.
Every one of the suggestions has at least one big drawback, so basically
what we do now seems to be the best solution.

> Immediately after that TSVN-trunk may be switched to SVN-trunk.
>
> Don't get me wrong. I'm always working with nightly builds from
> TSVN-trunk and am quite comfortable with that, but releasing based on
> Subversion trunk seems a bit risky to me.

We linked our trunk against the svn trunk before without any problems.
Of course not for the releases but for the nightly builds. And that's
what we will do again.

Stefan

--
        ___
   oo // \\ "De Chelonian Mobile"
  (_,\/ \_/ \ TortoiseSVN
    \ \_/_\_/> The coolest Interface to (Sub)Version Control
    /_/ \_\ http://tortoisesvn.net

Re: TSVN release cycles

Author schaefer
Full name Tobias Schaefer
Date 2010-05-11 11:22:48 PDT
Message On 11.05.2010 19:42, Stefan Küng wrote:
> Sometime this or maybe next week, the svn library will get rid of the
> double property handling. That means the speed of the new wc format will
> finally be so that we can use it.
> So I'll soon switch the TSVN trunk to link against the svn trunk so I
> can start implementing the new features. Once that's done, we can't make
> a TSVN release without waiting for the svn release.

You surely mean "can make" ;-)

If we link to the svn trunk we will not have a stable Subversion basis
for a while and will IMHO not be able to release stable TortoiseSVN builds.

Why not release the current TSVN-trunk based on the current 1.6.x branch
now (after a short beta)? However, the question is if this will be
called 1.6.10, 1.7.0, 2.0, or 2010-05 (see prevision discussions).

Immediately after that TSVN-trunk may be switched to SVN-trunk.

Don't get me wrong. I'm always working with nightly builds from
TSVN-trunk and am quite comfortable with that, but releasing based on
Subversion trunk seems a bit risky to me.

Tobias

--
         ___
    oo // \\ "De Chelonian Mobile"
   (_,\/ \_/ \ TortoiseSVN
     \ \_/_\_/> The coolest Interface to (Sub)Version Control
     /_/ \_\ http://tortoisesvn.net

Re: TSVN release cycles

Author steveking
Full name Stefan Küng
Date 2010-05-11 10:42:28 PDT
Message On 11.05.2010 01:00, Simon Large wrote:
> On 10 May 2010 18:03, Stefan Küng<tortoisesvn@​gmail.com> wrote:
>> On 09.05.2010 22:58, Simon Large wrote:
>>> Hi guys,
>>>
>>> I just read this quote from CMike on the CollabNet newsletter,
>>> referring to the SVN roadmap.
>>>
>>> "An admitted shortcoming of this roadmap is its lack of associated
>>> release dates. Realistically speaking, I think the myth of returning
>>> to six-month release cycles in Subversion has been dispelled by
>>> experience. The relatively easy work we were doing years ago is all
>>> done, leaving only the challenging stuff. I suspect this means we'll
>>> have roughly 9-15 month release cycles, at least until more of the
>>> larger plumbing-type tasks are completed."
>>>
>>> That's a very long release cycle for TSVN to follow. Is it worth
>>> trying again at breaking the link between SVN's version numbers and
>>> ours?
>>
>> Have you read this?
>> http://tortoisesvn.t​igris.org/ds/viewMes​sage.do?dsForumId=75​7&dsMessageId=24​47244
>
> Yes, I contributed to that thread. I know there was some dissent but I
> thought there were more for than against, and that we were starting to
> converge on some sort of numbering scheme.

Sometime this or maybe next week, the svn library will get rid of the
double property handling. That means the speed of the new wc format will
finally be so that we can use it.
So I'll soon switch the TSVN trunk to link against the svn trunk so I
can start implementing the new features. Once that's done, we can't make
a TSVN release without waiting for the svn release.

Stefan


--
        ___
   oo // \\ "De Chelonian Mobile"
  (_,\/ \_/ \ TortoiseSVN
    \ \_/_\_/> The coolest Interface to (Sub)Version Control
    /_/ \_\ http://tortoisesvn.net

Re: TSVN release cycles

Author simonlarge
Full name Simon Large
Date 2010-05-10 16:00:31 PDT
Message On 10 May 2010 18:03, Stefan Küng <tortoisesvn at gmail dot com> wrote:
> On 09.05.2010 22:58, Simon Large wrote:
>> Hi guys,
>>
>> I just read this quote from CMike on the CollabNet newsletter,
>> referring to the SVN roadmap.
>>
>> "An admitted shortcoming of this roadmap is its lack of associated
>> release dates. Realistically speaking, I think the myth of returning
>> to six-month release cycles in Subversion has been dispelled by
>> experience. The relatively easy work we were doing years ago is all
>> done, leaving only the challenging stuff. I suspect this means we'll
>> have roughly 9-15 month release cycles, at least until more of the
>> larger plumbing-type tasks are completed."
>>
>> That's a very long release cycle for TSVN to follow. Is it worth
>> trying again at breaking the link between SVN's version numbers and
>> ours?
>
> Have you read this?
> http://tortoisesvn.t​igris.org/ds/viewMes​sage.do?dsForumId=75​7&dsMessageId=24​47244

Yes, I contributed to that thread. I know there was some dissent but I
thought there were more for than against, and that we were starting to
converge on some sort of numbering scheme.

Simon

--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net

Re: TSVN release cycles

Author steveking
Full name Stefan Küng
Date 2010-05-10 10:03:30 PDT
Message On 09.05.2010 22:58, Simon Large wrote:
> Hi guys,
>
> I just read this quote from CMike on the CollabNet newsletter,
> referring to the SVN roadmap.
>
> "An admitted shortcoming of this roadmap is its lack of associated
> release dates. Realistically speaking, I think the myth of returning
> to six-month release cycles in Subversion has been dispelled by
> experience. The relatively easy work we were doing years ago is all
> done, leaving only the challenging stuff. I suspect this means we'll
> have roughly 9-15 month release cycles, at least until more of the
> larger plumbing-type tasks are completed."
>
> That's a very long release cycle for TSVN to follow. Is it worth
> trying again at breaking the link between SVN's version numbers and
> ours?

Have you read this?
http://tortoisesvn.t​igris.org/ds/viewMes​sage.do?dsForumId=75​7&dsMessageId=24​47244

Stefan

--
        ___
   oo // \\ "De Chelonian Mobile"
  (_,\/ \_/ \ TortoiseSVN
    \ \_/_\_/> The coolest Interface to (Sub)Version Control
    /_/ \_\ http://tortoisesvn.net

TSVN release cycles

Author simonlarge
Full name Simon Large
Date 2010-05-09 13:58:10 PDT
Message Hi guys,

I just read this quote from CMike on the CollabNet newsletter,
referring to the SVN roadmap.

"An admitted shortcoming of this roadmap is its lack of associated
release dates. Realistically speaking, I think the myth of returning
to six-month release cycles in Subversion has been dispelled by
experience. The relatively easy work we were doing years ago is all
done, leaving only the challenging stuff. I suspect this means we'll
have roughly 9-15 month release cycles, at least until more of the
larger plumbing-type tasks are completed."

That's a very long release cycle for TSVN to follow. Is it worth
trying again at breaking the link between SVN's version numbers and
ours?

Simon

--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
Messages per page: