On 11/12/2017 23:46, luke1...@apache.org wrote:
> Author: luke1410
> Date: Mon Dec 11 22:46:17 2017
> New Revision: 1817862
>
> URL: http://svn.apache.org/viewvc?rev=1817862&view=rev
> Log:
> * site/staging/docs/release-notes/1.4.html: Replace a dead link to the
> Berkeley DB upgrade guide.
>
> M
On 11/12/2017 18:15, Daniel Shahaf wrote:
> julianf...@apache.org wrote on Mon, 11 Dec 2017 13:41 +:
>> Modified:
>> subversion/site/publish/docs/community-guide/releasing.part.html
> Could you backport this to staging/ so future changes to staging don't
> merge conflict when they are publi
I started writing a create-a-release-branch script to automate the part
of the procedure documented in
http://subversion.apache.org/docs/community-guide/releasing.html#release-branches
Attached, in early draft form:
tools/dist/create-minor-release-branch.py
(contains bits from release.py)
Sugg
julianf...@apache.org wrote on Mon, 11 Dec 2017 21:18 +:
> Increment the trunk version number, and introduce a new CHANGES
> section for the upcoming 1.10.0 release.
> +++
> subversion/trunk/subversion/bindings/javahl/src/org/apache/subversion/javahl/NativeResources.java
> Mon Dec 11 21:18:29
Julian Foad wrote on Mon, 11 Dec 2017 19:51 +:
> Daniel Shahaf wrote:
> > I think we should enable this warning by default in maintainer mode in
> > supporting compilers, but that's a separate discussion to just fixing
> > these error leaks in trunk (& 1.10.x).
>
> +1. I was going to say that,
Daniel Shahaf wrote:
[...]
svn_element__tree_set(branch->priv->element_tree, old_eid, NULL);
svn_element__tree_set(branch->priv->element_tree, new_eid, element);
svn_element__tree_set(branch->priv->element_tree, eid, element);
svn_element__tree_set(new_subtree, new_sub
Daniel Shahaf wrote:
The release branch creation checkpoints calls for checking for error
leaks, so here's the output of tools/dev/warn-unused-result.sh (after
removing the __attribute__ from svn_error__malfunction()):
[about 41 instances]
Thank you, Daniel!
Anyone volunteering to fix them?
The release branch creation checkpoints calls for checking for error
leaks, so here's the output of tools/dev/warn-unused-result.sh (after
removing the __attribute__ from svn_error__malfunction()):
[[[
subversion/libsvn_delta/branch.c:485:11: warning: ignoring return value of
function declared wi
julianf...@apache.org wrote on Mon, 11 Dec 2017 13:41 +:
> Modified:
> subversion/site/publish/docs/community-guide/releasing.part.html
Could you backport this to staging/ so future changes to staging don't
merge conflict when they are published?
> +++ subversion/site/publish/docs/communi
Would anyone volunteer to update
http://subversion.apache.org/roadmap
to reflect the current status regarding what's ready for 1.10?
- Julian
Jira feature request needed to capture anything from this thread? Maybe
not, if plans were already in action anyway...
11 matches
Mail list logo
