[ANNOUNCE] Apache Subversion 1.13.0-rc1 released
I'm happy to announce the release of Apache Subversion 1.13.0-rc1. Please choose the mirror closest to you by visiting: https://subversion.apache.org/download.cgi#pre-releases SHA-512 checksums are available at: https://www.apache.org/dist/subversion/subversion-1.13.0-rc1.tar.bz2.sha512 https://www.apache.org/dist/subversion/subversion-1.13.0-rc1.tar.gz.sha512 https://www.apache.org/dist/subversion/subversion-1.13.0-rc1.zip.sha512 PGP Signatures are available at: https://www.apache.org/dist/subversion/subversion-1.13.0-rc1.tar.bz2.asc https://www.apache.org/dist/subversion/subversion-1.13.0-rc1.tar.gz.asc https://www.apache.org/dist/subversion/subversion-1.13.0-rc1.zip.asc For this release, the following people have provided PGP signatures: Julian Foad [4096R/1FB064B84EECC493] with fingerprint: 6011 63CF 9D49 9FD7 18CF 582D 1FB0 64B8 4EEC C493 Nathan Hartman (CODE SIGNING KEY) [4096R/583F00ADF981C39F] with fingerprint: 3F8E 467C B336 6E30 13E1 120D 583F 00AD F981 C39F Johan Corveleyn [4096R/B59CE6D6010C8AAD] with fingerprint: 8AA2 C10E EAAD 44F9 6972 7AEA B59C E6D6 010C 8AAD This is a pre-release for what will eventually become version 1.13.0 of the Apache Subversion open source version control system. It may contain known issues, a complete list of 1.13.0-blocking issues can be found here: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SVN%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.13.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC A pre-release means the Subversion developers feel that this release is ready for widespread testing by the community. There are known issues (and unknown ones!), so please use it at your own risk, though we do encourage people to test this release thoroughly. Of particular note, please remember that persistent data, such as the working copy or repository formats may change before the final release, and there may not be an upgrade path from the pre-releases to the final. As a note to operating system distro packagers: while we wish to have this release candidate widely tested, we do not feel that it is ready for packaging and providing to end-users through a distro package system. Packaging a release candidate poses many problems, the biggest being that our policy lets us break compatibility between the release candidate and the final release, if we find something serious enough. Having many users depending on a release candidate through their distro would cause no end of pain and frustration that we do not want to have to deal with. However, if your distro has a branch that is clearly labeled as containing experimental and often broken software, and explicitly destined to consenting developers and integrators only, then we're okay with packaging the release candidate there. Just don't let it near the end users please. Release notes for the 1.13.x release series may be found at: https://subversion.apache.org/docs/release-notes/1.13.html You can find the list of changes between 1.13.0-rc1 and earlier versions at: https://svn.apache.org/repos/asf/subversion/tags/1.13.0-rc1/CHANGES Questions, comments, and bug reports to users@subversion.apache.org. Thanks, - The Subversion Team -- To unsubscribe, please see: https://subversion.apache.org/mailing-lists.html#unsubscribing
Re: Subversion and JIRA integration
Hi Ragu, Your question is sort of a tricky one. Well, at least parts of it are. But here's an attempt at an answer. On Sun, Sep 29, 2019 at 9:50 PM Ragu Nathan wrote: > > Hi, > > I would like to know the Subversion can be integrate with JIRA bug > tracking tool. > Yes, but it depends on your requirements, and how many development resources you're willing to throw at it, if a commercial vendor doesn't provide it already. > Ex: I found an issue in software coding and create a problem report to > address root cause, analysis, documents updates , etc and I will use the > JIRA to track all above, but Subversion is a configuration management tool > to store data ( source code, documents, etc). > Subversion is a version control tool, not a configuration management tool. While it may certainly be possible to use Subversion in the manner implied, the definition of "configuration management" may lead to requirements that Subversion is less than ideal for. > Questions: > 1. If I use the JIRA tool to address an issue , address all sort of > analysis, proposed solutions, implementation details and I want to update > the documents or source code in Subversion, is there any way to get into > Subversion from JIRA? Not hyperlink. Real integrate environment. In this > case I can check if any updates were made in to the documents or source > code , which problem reporting # was used to fix the issue. > As I understand it, JIRA includes an extension API. It certainly should be possible to extend JIRA to get more detailed information about links into Subversion, without, as you indicate "hyperlinking". There exist integrations into JIRA already for tighter coupling with Subversion, so you could start with those, to see if any of those meet your requirements. > 2. Are both tools integrate together? > It is left to one's imagination. Both have APIs, so it is possible to add tighter integration to both. For details of how to integrate from Subversion's perspective, check out the "hook" documentation: http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.hooks Atlassian definitely offers APIs from the JIRA side: https://developer.atlassian.com/server/framework/atlassian-sdk/ > 3. If so, how much would it cost for floating licence? > This mailing list isn't going to be a good source of information about that. And that assumes that you can find an existing commercial vendor of extension(s) that meet your needs. Eric. > > > Thanks > Ragu.P > >
correct API to get current textual WC modifications, for parsing postprocessing
I try to get all line changes in the current changeset. Not sure what the right API is. I have created a delta tree with the following to see if it is a file and textual modifications. How do I get the content? SVN_ERR(svn_fs_revision_root(&base_root, fs, base_rev, pool)); SVN_ERR(svn_repos_node_editor(&editor, &edit_baton, repos, base_root, root, pool, edit_pool))); SVN_ERR(svn_repos_replay2(root, "", SVN_INVALID_REVNUM, TRUE, editor, edit_baton, NULL, NULL, edit_pool)); *tree = svn_repos_node_from_baton(edit_baton); Jens
Re: Subversion and JIRA integration
The actual Atlassian product you're looking for is called FishEye. It works with all major repos including SVN, Git, etc., and its primary purpose is exactly what you're wanting. This is a different license, and runs as a different service than Jira -- which could potentially actually make it cheaper in theory than if it were an actual straight up Jira add-on only since you can license it to a subset of your overall Jira users whom may actually need it. FishEye is specifically meant for the purpose of integrating source control repositories into Jira. When you check an item in to SVN, as part of the checkin you would provide the Jira ticket # in the log, and then Fisheye indexes that, and then in turn Jira provides links/revision #s/etc. within the Jira ticket. If you then click that it will open in the FishEye interface and you can dive down further into what was checked, see the diff, etc., full source control, etc., in the Fisheye web interface. Another Atlassian product, Crucible, ties-in to that then to allow you to do a standard code review workflow if you wish, but that is another addon beyond Fisheye even. Anecdotal notes on this product are it works great *but *you should really make a good attempt at installing this on the same actual server your SVN server runs on, so you can access the repos by their file:// location -- the difference is 100x speed vs over the network w/ http/svn protocols, and may even be the difference between the product working and being able to index your repo or not. If you don't want to run it on your primary SVN, consider an active mirror sync to the box that fisheye then runs on and index that version locally. -Dane On Mon, Sep 30, 2019 at 1:35 PM Eric Johnson wrote: > Hi Ragu, > > Your question is sort of a tricky one. Well, at least parts of it are. But > here's an attempt at an answer. > > On Sun, Sep 29, 2019 at 9:50 PM Ragu Nathan wrote: > >> >> Hi, >> >> I would like to know the Subversion can be integrate with JIRA bug >> tracking tool. >> > > Yes, but it depends on your requirements, and how many development > resources you're willing to throw at it, if a commercial vendor doesn't > provide it already. > > >> Ex: I found an issue in software coding and create a problem report to >> address root cause, analysis, documents updates , etc and I will use the >> JIRA to track all above, but Subversion is a configuration management tool >> to store data ( source code, documents, etc). >> > > Subversion is a version control tool, not a configuration management tool. > While it may certainly be possible to use Subversion in the manner implied, > the definition of "configuration management" may lead to requirements that > Subversion is less than ideal for. > > >> Questions: >> 1. If I use the JIRA tool to address an issue , address all sort of >> analysis, proposed solutions, implementation details and I want to update >> the documents or source code in Subversion, is there any way to get into >> Subversion from JIRA? Not hyperlink. Real integrate environment. In this >> case I can check if any updates were made in to the documents or source >> code , which problem reporting # was used to fix the issue. >> > > As I understand it, JIRA includes an extension API. It certainly should be > possible to extend JIRA to get more detailed information about links into > Subversion, without, as you indicate "hyperlinking". > > There exist integrations into JIRA already for tighter coupling with > Subversion, so you could start with those, to see if any of those meet your > requirements. > > >> 2. Are both tools integrate together? >> > > It is left to one's imagination. Both have APIs, so it is possible to add > tighter integration to both. For details of how to integrate from > Subversion's perspective, check out the "hook" documentation: > > > http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.hooks > > Atlassian definitely offers APIs from the JIRA side: > https://developer.atlassian.com/server/framework/atlassian-sdk/ > > >> 3. If so, how much would it cost for floating licence? >> > > This mailing list isn't going to be a good source of information about > that. And that assumes that you can find an existing commercial vendor of > extension(s) that meet your needs. > > Eric. > > > >> >> >> Thanks >> Ragu.P >> >>
Re: Subversion and JIRA integration
Thanks for your responses Eric and Dan, So FishEye interfaces with JIRA and Subversion. Do you have the trail versions of these tools ? I could try and see how it works or you have some sort of online demo for me to see how it works. Your response is appreciated. Thanks Ragu.P Sent from my iPhone > On Sep 30, 2019, at 5:06 PM, Dane Kantner wrote: > > The actual Atlassian product you're looking for is called FishEye. It works > with all major repos including SVN, Git, etc., and its primary purpose is > exactly what you're wanting. This is a different license, and runs as a > different service than Jira -- which could potentially actually make it > cheaper in theory than if it were an actual straight up Jira add-on only > since you can license it to a subset of your overall Jira users whom may > actually need it. > > FishEye is specifically meant for the purpose of integrating source control > repositories into Jira. When you check an item in to SVN, as part of the > checkin you would provide the Jira ticket # in the log, and then Fisheye > indexes that, and then in turn Jira provides links/revision #s/etc. within > the Jira ticket. If you then click that it will open in the FishEye interface > and you can dive down further into what was checked, see the diff, etc., full > source control, etc., in the Fisheye web interface. Another Atlassian > product, Crucible, ties-in to that then to allow you to do a standard code > review workflow if you wish, but that is another addon beyond Fisheye even. > > Anecdotal notes on this product are it works great but you should really make > a good attempt at installing this on the same actual server your SVN server > runs on, so you can access the repos by their file:// location -- the > difference is 100x speed vs over the network w/ http/svn protocols, and may > even be the difference between the product working and being able to index > your repo or not. If you don't want to run it on your primary SVN, consider > an active mirror sync to the box that fisheye then runs on and index that > version locally. > > -Dane > >> On Mon, Sep 30, 2019 at 1:35 PM Eric Johnson wrote: >> Hi Ragu, >> >> Your question is sort of a tricky one. Well, at least parts of it are. But >> here's an attempt at an answer. >> >>> On Sun, Sep 29, 2019 at 9:50 PM Ragu Nathan wrote: >>> >>> Hi, >>> >>> I would like to know the Subversion can be integrate with JIRA bug tracking >>> tool. >> >> Yes, but it depends on your requirements, and how many development resources >> you're willing to throw at it, if a commercial vendor doesn't provide it >> already. >> >>> Ex: I found an issue in software coding and create a problem report to >>> address root cause, analysis, documents updates , etc and I will use the >>> JIRA to track all above, but Subversion is a configuration management tool >>> to store data ( source code, documents, etc). >> >> Subversion is a version control tool, not a configuration management tool. >> While it may certainly be possible to use Subversion in the manner implied, >> the definition of "configuration management" may lead to requirements that >> Subversion is less than ideal for. >> >>> Questions: >>> 1. If I use the JIRA tool to address an issue , address all sort of >>> analysis, proposed solutions, implementation details and I want to update >>> the documents or source code in Subversion, is there any way to get into >>> Subversion from JIRA? Not hyperlink. Real integrate environment. In this >>> case I can check if any updates were made in to the documents or source >>> code , which problem reporting # was used to fix the issue. >> >> As I understand it, JIRA includes an extension API. It certainly should be >> possible to extend JIRA to get more detailed information about links into >> Subversion, without, as you indicate "hyperlinking". >> >> There exist integrations into JIRA already for tighter coupling with >> Subversion, so you could start with those, to see if any of those meet your >> requirements. >> >>> 2. Are both tools integrate together? >> >> It is left to one's imagination. Both have APIs, so it is possible to add >> tighter integration to both. For details of how to integrate from >> Subversion's perspective, check out the "hook" documentation: >> >> http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.hooks >> >> Atlassian definitely offers APIs from the JIRA side: >> https://developer.atlassian.com/server/framework/atlassian-sdk/ >> >>> 3. If so, how much would it cost for floating licence? >> >> This mailing list isn't going to be a good source of information about that. >> And that assumes that you can find an existing commercial vendor of >> extension(s) that meet your needs. >> >> Eric. >> >> >>> >>> >>> Thanks >>> Ragu.P >>>
Re: Subversion and JIRA integration
See https://www.atlassian.com/software/fisheye Also note that the pricing for *new *licenses will be going up a not insignificant percentage October 3rd -- https://www.atlassian.com/licensing/future-pricing -- so if you are thinking about buying it you may just skip the trial :( On Mon, Sep 30, 2019 at 7:35 PM Ragu Nathan wrote: > Thanks for your responses Eric and Dan, > > So FishEye interfaces with JIRA and Subversion. > Do you have the trail versions of these tools ? I could try and see how it > works or you have some sort of online demo for me to see how it works. > > Your response is appreciated. > > Thanks > Ragu.P > > Sent from my iPhone > > On Sep 30, 2019, at 5:06 PM, Dane Kantner wrote: > > The actual Atlassian product you're looking for is called FishEye. It > works with all major repos including SVN, Git, etc., and its primary > purpose is exactly what you're wanting. This is a different license, and > runs as a different service than Jira -- which could potentially actually > make it cheaper in theory than if it were an actual straight up Jira add-on > only since you can license it to a subset of your overall Jira users whom > may actually need it. > > FishEye is specifically meant for the purpose of integrating source > control repositories into Jira. When you check an item in to SVN, as part > of the checkin you would provide the Jira ticket # in the log, and then > Fisheye indexes that, and then in turn Jira provides links/revision #s/etc. > within the Jira ticket. If you then click that it will open in the FishEye > interface and you can dive down further into what was checked, see the > diff, etc., full source control, etc., in the Fisheye web interface. > Another Atlassian product, Crucible, ties-in to that then to allow you to > do a standard code review workflow if you wish, but that is another addon > beyond Fisheye even. > > Anecdotal notes on this product are it works great *but *you should > really make a good attempt at installing this on the same actual server > your SVN server runs on, so you can access the repos by their file:// > location -- the difference is 100x speed vs over the network w/ http/svn > protocols, and may even be the difference between the product working and > being able to index your repo or not. If you don't want to run it on your > primary SVN, consider an active mirror sync to the box that fisheye then > runs on and index that version locally. > > -Dane > > On Mon, Sep 30, 2019 at 1:35 PM Eric Johnson wrote: > >> Hi Ragu, >> >> Your question is sort of a tricky one. Well, at least parts of it are. >> But here's an attempt at an answer. >> >> On Sun, Sep 29, 2019 at 9:50 PM Ragu Nathan wrote: >> >>> >>> Hi, >>> >>> I would like to know the Subversion can be integrate with JIRA bug >>> tracking tool. >>> >> >> Yes, but it depends on your requirements, and how many development >> resources you're willing to throw at it, if a commercial vendor doesn't >> provide it already. >> >> >>> Ex: I found an issue in software coding and create a problem report to >>> address root cause, analysis, documents updates , etc and I will use the >>> JIRA to track all above, but Subversion is a configuration management tool >>> to store data ( source code, documents, etc). >>> >> >> Subversion is a version control tool, not a configuration management >> tool. While it may certainly be possible to use Subversion in the manner >> implied, the definition of "configuration management" may lead to >> requirements that Subversion is less than ideal for. >> >> >>> Questions: >>> 1. If I use the JIRA tool to address an issue , address all sort of >>> analysis, proposed solutions, implementation details and I want to update >>> the documents or source code in Subversion, is there any way to get into >>> Subversion from JIRA? Not hyperlink. Real integrate environment. In this >>> case I can check if any updates were made in to the documents or source >>> code , which problem reporting # was used to fix the issue. >>> >> >> As I understand it, JIRA includes an extension API. It certainly should >> be possible to extend JIRA to get more detailed information about links >> into Subversion, without, as you indicate "hyperlinking". >> >> There exist integrations into JIRA already for tighter coupling with >> Subversion, so you could start with those, to see if any of those meet your >> requirements. >> >> >>> 2. Are both tools integrate together? >>> >> >> It is left to one's imagination. Both have APIs, so it is possible to add >> tighter integration to both. For details of how to integrate from >> Subversion's perspective, check out the "hook" documentation: >> >> >> http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.hooks >> >> Atlassian definitely offers APIs from the JIRA side: >> https://developer.atlassian.com/server/framework/atlassian-sdk/ >> >> >>> 3. If so, how much would it cost for floating licence? >>> >> >> This mailing list isn't goin
unsubscribe
unsubscribe
unsubscribe
> unsubscribe > > >
unsubscribe
unsubscribe
Re: correct API to get current textual WC modifications, for parsing postprocessing
On 30.09.2019 22:20, Jens Frederich wrote: > I try to get all line changes in the current changeset. Not sure what > the right API is. I have created a delta tree with the following to > see if it is a file and textual modifications. How do I get the content? > > SVN_ERR(svn_fs_revision_root(&base_root, fs, base_rev, pool)); > SVN_ERR(svn_repos_node_editor(&editor, &edit_baton, repos, > base_root, root, pool, edit_pool))); > SVN_ERR(svn_repos_replay2(root, "", SVN_INVALID_REVNUM, TRUE, > editor, edit_baton, NULL, NULL, edit_pool)); > *tree = svn_repos_node_from_baton(edit_baton); You should be looking at the svn_client API, specifically, one of the svn_client_diff variants. The functions you mentioned above are reading data from the repository, not from the working copy. -- Brane
