You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Hyrum K. Wright" <hy...@mail.utexas.edu> on 2009/03/16 21:45:49 UTC
URGENT: Last call for 1.6.0
We've got CHANGES for 1.6.0 in trunk and updated. I'm going to give
people 24 hours to review and edit it, and to raise any pending
issues which may block a public 1.6.0 release on Friday. Speak now,
or forever hold your peace! (Or, at least hold it until next week
when we go to work on 1.6.1. :) )
After the 24 hours, assuming no critical show-stopper issues are
raised, I'll roll the final release candidate, collect sigs, publish
it, and then get to work rolling the final tarball from the same magic
rev. I'd like to have that tarball ready for a Friday morning (~1500
UTC) release. Please let me know if there are any questions or
concerns with this plan.
Also, please edit and update the release notes so they are accurate
when the release goes live. Thanks again to everybody for all the
effort that has gone into making 1.6.0 the best Subversion release yet!
-Hyrum
PS - I'll be afk for most of the day tomorrow (hence the 24 hour
period), but I don't anticipate that causing any problems.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1335549
Re: URGENT: Last call for 1.6.0
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Mar 17, 2009, at 9:49 AM, Philip Martin wrote:
> Mark Phippard <ma...@gmail.com> writes:
>
>>> On Mar 17, 2009, at 3:40 AM, Philip Martin wrote:
>>>
>>>> The resolution of issue 2461 (r33417) changed the behaviour of
>>>> svn:externals containing a backslash, see the discussion here:
>>>>
>>>> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=86142
>>>
>>> So, does this constitute a showstopper? Beyond just mentioning
>>> issues, it would be useful to point out the impact, and to justify
>>> why
>>> a particular bug or feature would hold up the release.
>>>
>>> (For the record, I *don't* think this is a showstopper, but this
>>> ain't
>>> my project. I'm just saying there'd better be some compelling
>>> evidence before stopping the release train.)
>>
>> Based on the thread he pointed to, I'd say Philip is reminding us to
>> include this in CHANGES and the release notes.
>
> That's right. As I understand it Windows and Unix did not have the
> same behaviour as each other in the past, the behaviour of both has
> changed and they are still not the same as each other. This is user
> visible and we know about it; so we should tell people what has
> changed, what they can do to get the old behaviour with new clients,
> and whether or not both old and new clients can be supported.
Ah, thanks for the clarification. Based upon that, I prefer to leave
the single-line entry in CHANGES as is, but we need to be sure to
mention this in the Release Notes.
-Hyrum
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1345157
Re: URGENT: Last call for 1.6.0
Posted by Philip Martin <ph...@codematters.co.uk>.
Mark Phippard <ma...@gmail.com> writes:
>> On Mar 17, 2009, at 3:40 AM, Philip Martin wrote:
>>
>>> The resolution of issue 2461 (r33417) changed the behaviour of
>>> svn:externals containing a backslash, see the discussion here:
>>>
>>> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=86142
>>
>> So, does this constitute a showstopper? Beyond just mentioning
>> issues, it would be useful to point out the impact, and to justify why
>> a particular bug or feature would hold up the release.
>>
>> (For the record, I *don't* think this is a showstopper, but this ain't
>> my project. I'm just saying there'd better be some compelling
>> evidence before stopping the release train.)
>
> Based on the thread he pointed to, I'd say Philip is reminding us to
> include this in CHANGES and the release notes.
That's right. As I understand it Windows and Unix did not have the
same behaviour as each other in the past, the behaviour of both has
changed and they are still not the same as each other. This is user
visible and we know about it; so we should tell people what has
changed, what they can do to get the old behaviour with new clients,
and whether or not both old and new clients can be supported.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1341654
Re: URGENT: Last call for 1.6.0
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, Mar 17, 2009 at 9:06 AM, Hyrum K. Wright
<hy...@mail.utexas.edu> wrote:
> On Mar 17, 2009, at 3:40 AM, Philip Martin wrote:
>
>> "Hyrum K. Wright" <hy...@mail.utexas.edu> writes:
>>
>>> We've got CHANGES for 1.6.0 in trunk and updated. I'm going to give
>>> people 24 hours to review and edit it, and to raise any pending
>>> issues which may block a public 1.6.0 release on Friday. Speak now,
>>> or forever hold your peace! (Or, at least hold it until next week
>>> when we go to work on 1.6.1. :) )
>>
>> The resolution of issue 2461 (r33417) changed the behaviour of
>> svn:externals containing a backslash, see the discussion here:
>>
>> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=86142
>
> So, does this constitute a showstopper? Beyond just mentioning
> issues, it would be useful to point out the impact, and to justify why
> a particular bug or feature would hold up the release.
>
> (For the record, I *don't* think this is a showstopper, but this ain't
> my project. I'm just saying there'd better be some compelling
> evidence before stopping the release train.)
Based on the thread he pointed to, I'd say Philip is reminding us to
include this in CHANGES and the release notes.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1341093
Re: URGENT: Last call for 1.6.0
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Mar 17, 2009, at 3:40 AM, Philip Martin wrote:
> "Hyrum K. Wright" <hy...@mail.utexas.edu> writes:
>
>> We've got CHANGES for 1.6.0 in trunk and updated. I'm going to give
>> people 24 hours to review and edit it, and to raise any pending
>> issues which may block a public 1.6.0 release on Friday. Speak now,
>> or forever hold your peace! (Or, at least hold it until next week
>> when we go to work on 1.6.1. :) )
>
> The resolution of issue 2461 (r33417) changed the behaviour of
> svn:externals containing a backslash, see the discussion here:
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=86142
So, does this constitute a showstopper? Beyond just mentioning
issues, it would be useful to point out the impact, and to justify why
a particular bug or feature would hold up the release.
(For the record, I *don't* think this is a showstopper, but this ain't
my project. I'm just saying there'd better be some compelling
evidence before stopping the release train.)
-Hyrum
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1340954
Re: URGENT: Last call for 1.6.0
Posted by Philip Martin <ph...@codematters.co.uk>.
"Hyrum K. Wright" <hy...@mail.utexas.edu> writes:
> We've got CHANGES for 1.6.0 in trunk and updated. I'm going to give
> people 24 hours to review and edit it, and to raise any pending
> issues which may block a public 1.6.0 release on Friday. Speak now,
> or forever hold your peace! (Or, at least hold it until next week
> when we go to work on 1.6.1. :) )
The resolution of issue 2461 (r33417) changed the behaviour of
svn:externals containing a backslash, see the discussion here:
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=86142
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1339263
RE: URGENT: Last call for 1.6.0
Posted by Chris Foote <ca...@yahoo.com>.
One more for the changes file if no one else beats me to it.
[[[
Mention the new 'svnsync info' subcommand.
]]
Regards
Chris
P.S. Moderators, please remove the other mail I sent without logging in on tigris.org.
Index: CHANGES
===================================================================
--- CHANGES (revision 36629)
+++ CHANGES (working copy)
@@ -28,6 +28,7 @@
* new 'svnadmin pack' command to compress FSFS filesystems
* new SVNAllowBulkUpdates mod_dav_svn directive (issue #3121)
* new public mod_dav_svn URI syntax: path?[p=PEG][&r=REV] (r34076)
+ * new 'svnsync info' command to show synchronization information (r35053)
- Client-side bugfixes:
* faulty reflexive merges (issue #2897)
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1342383
Re: URGENT: Last call for 1.6.0
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Mar 19, 2009, at 8:33 PM, Konstantin Kolinko wrote:
> 2009/3/18 Hyrum K. Wright <hy...@mail.utexas.edu>:
>>
>> Eh, no problem. Just like code, it typically takes a few reviewers
>> to
>> get everything right. Thanks for helping out!
>>
> Totally agree.
>
>
> The following new feature is missing from CHANGES:
> better support for sparse checkouts.
>
> 1. Fixing issue
> http://subversion.tigris.org/issues/show_bug.cgi?id=2843
>
> That is, I understand that all those command line options, that are
> mentioned in a big bold frame inside /notes/sparse-directories.txt
> should work now.
>
> 2. New feature:
> svn update --set-depth exclude PATH
>
> I wonder, that it is not mentioned in /notes/sparse-
> directories.txt, but here
> is a description:
>
> http://blogs.open.collab.net/svn/2009/03/sparse-directories-now-with-exclusion.html
>
> Citing from there:
>> This value tells Subversion to exclude the target from the working
>> copy,
>> immediately and until further notice.
>
> 'svn help update' mentions that new --set-depth option value.
>
>
> Also, a minor change:
> There is no more .svn/format file in WCs.
>
>
> Though it is probably too late for CHANGES, may be the above may
> find its
> way into release notes?
I can't believe I forgot this feature. We can always add it CHANGES
retroactively, but something in the release notes would be helpful.
Care to submit a patch?
-Hyrum
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1360619
Re: URGENT: Last call for 1.6.0
Posted by Konstantin Kolinko <kn...@gmail.com>.
2009/3/18 Hyrum K. Wright <hy...@mail.utexas.edu>:
>
> Eh, no problem. Just like code, it typically takes a few reviewers to
> get everything right. Thanks for helping out!
>
Totally agree.
The following new feature is missing from CHANGES:
better support for sparse checkouts.
1. Fixing issue
http://subversion.tigris.org/issues/show_bug.cgi?id=2843
That is, I understand that all those command line options, that are
mentioned in a big bold frame inside /notes/sparse-directories.txt
should work now.
2. New feature:
svn update --set-depth exclude PATH
I wonder, that it is not mentioned in /notes/sparse-directories.txt, but here
is a description:
http://blogs.open.collab.net/svn/2009/03/sparse-directories-now-with-exclusion.html
Citing from there:
> This value tells Subversion to exclude the target from the working copy,
> immediately and until further notice.
'svn help update' mentions that new --set-depth option value.
Also, a minor change:
There is no more .svn/format file in WCs.
Though it is probably too late for CHANGES, may be the above may find its
way into release notes?
Best regards,
Konstantin Kolinko
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1359803
Re: URGENT: Last call for 1.6.0
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Mar 17, 2009, at 8:16 PM, Edmund Wong wrote:
> Konstantin Kolinko wrote:
>
>>> The same issue, mentioned twice, both as client-side and as server-
>>> side fix.
>>> What server-side fix was there?
>>> The changes in rev. 33236 look like client-side to me,
>>> and I see nothing else is mentioned in the issue tracker, or in
>>> the mail
>>> threads mentioned there.
>
> I believe this is my fault. Doing it both at work and at home (and
> being new at this whole thing; not that it's a good reason for this
> screw up) made me lose track of where I was all the time. I think
> Karl helped me there and I didn't know so I most likely added the
> same thing without checking. Again, my apologies.
>
> If given another chance and hopefully with more time, I'll get it
> right.
Eh, no problem. Just like code, it typically takes a few reviewers to
get everything right. Thanks for helping out!
-Hyrum
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1348227
Re: URGENT: Last call for 1.6.0
Posted by Edmund Wong <ed...@belfordhk.com>.
Konstantin Kolinko wrote:
>> The same issue, mentioned twice, both as client-side and as server-side fix.
>> What server-side fix was there?
>> The changes in rev. 33236 look like client-side to me,
>> and I see nothing else is mentioned in the issue tracker, or in the mail
>> threads mentioned there.
I believe this is my fault. Doing it both at work and at home (and
being new at this whole thing; not that it's a good reason for this
screw up) made me lose track of where I was all the time. I think
Karl helped me there and I didn't know so I most likely added the
same thing without checking. Again, my apologies.
If given another chance and hopefully with more time, I'll get it
right.
Edmund
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1344466
Re: URGENT: Last call for 1.6.0
Posted by Konstantin Kolinko <kn...@gmail.com>.
2009/3/17 Hyrum K. Wright <hy...@mail.utexas.edu>:
> We've got CHANGES for 1.6.0 in trunk and updated. I'm going to give
> people 24 hours to review and edit it, and to raise any pending
> issues which may block a public 1.6.0 release on Friday. Speak now,
> or forever hold your peace! (Or, at least hold it until next week
> when we go to work on 1.6.1. :) )
>
Some minor glitches
* don't repeat merge if target has explict mergeinfo (issue #2821)
s/explict/explicit/
* fix a potential a buffer overrun (r34374)
s/a buffer/buffer/
* faulty reflexive merges (issue #2897)
* mod_dav_svn runs pre-revprop-change twice (issue #3085)
* mod_dav_svn ignores pre-revprop-change failure on delete (issue #3086)
The issue tracker does not mention those issues as resolved. Should
they be listed as RESOLVED, or at least STARTED there? Do not know the
actual status.
* scheme and domain name in urls handled case insensitive (issue #2475)
* case-sensitivity in hostname bug in libsvn_repos (issue #2475)
The same issue, mentioned twice, both as client-side and as server-side fix.
What server-side fix was there?
The changes in rev. 33236 look like client-side to me,
and I see nothing else is mentioned in the issue tracker, or in the mail
threads mentioned there.
Best regards,
Konstantin Kolinko
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1343761
Re: URGENT: Last call for 1.6.0
Posted by Ben Collins-Sussman <su...@red-bean.com>.
Great job Karl & manyhands! I used to do the CHANGES entry all by
myself in the old days, and it would take me 10+ hours of solid
focused work.
I committed a few tweaks -- also mentioning the new *public* URI
syntax for looking at old versions of files. I can't wait to change
the svnbook and remove the sidebar that says this is impossible. :-)
On Mon, Mar 16, 2009 at 4:45 PM, Hyrum K. Wright
<hy...@mail.utexas.edu> wrote:
> We've got CHANGES for 1.6.0 in trunk and updated. I'm going to give
> people 24 hours to review and edit it, and to raise any pending
> issues which may block a public 1.6.0 release on Friday. Speak now,
> or forever hold your peace! (Or, at least hold it until next week
> when we go to work on 1.6.1. :) )
>
> After the 24 hours, assuming no critical show-stopper issues are
> raised, I'll roll the final release candidate, collect sigs, publish
> it, and then get to work rolling the final tarball from the same magic
> rev. I'd like to have that tarball ready for a Friday morning (~1500
> UTC) release. Please let me know if there are any questions or
> concerns with this plan.
>
> Also, please edit and update the release notes so they are accurate
> when the release goes live. Thanks again to everybody for all the
> effort that has gone into making 1.6.0 the best Subversion release yet!
>
> -Hyrum
>
> PS - I'll be afk for most of the day tomorrow (hence the 24 hour
> period), but I don't anticipate that causing any problems.
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1335549
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1341633
RE: URGENT: Last call for 1.6.0
Posted by we...@tigris.org.
One more addition for the changes file, if someone hasn't beaten me to it.
[[[
Mention the new 'svnsync info' subcommand.
]]]
Regards
Chris
Index: CHANGES
===================================================================
--- CHANGES (revision 36629)
+++ CHANGES (working copy)
@@ -28,6 +28,7 @@
* new 'svnadmin pack' command to compress FSFS filesystems
* new SVNAllowBulkUpdates mod_dav_svn directive (issue #3121)
* new public mod_dav_svn URI syntax: path?[p=PEG][&r=REV] (r34076)
+ * new 'svnsync info' command to show synchronization information (r35053)
- Client-side bugfixes:
* faulty reflexive merges (issue #2897)
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1342352