I think we currently require APR >= 1.3 on trunk and 1.9, so feel free to
remove outdated references to older versions.
Bert
From: Stefan
Sent: donderdag 17 september 2015 03:08
To: dev@subversion.apache.org
Subject: Dropping APR 0.9.x specifics from INSTALL doc
Hi,
before I'm making that
Hi,
before I'm making that change want to check here whether this is ok:
The intend is to drop the sections about compatibility issues between
APR 0.9.x and APR 1.x from the INSTALL documentation.
Reasoning is that APR 0.9.x is no longer supported since SVN 1.9.
Furthermore, Apache HTTPD >=
Stefan Hett writes:
> What would u say about this other scheme:
> 1.9.1.1 -> 1.9.1-1-r1694136-dev
> 1.9.1.2 -> 1.9.1-2
> 1.9.2.1 -> 1.9.2-1-r1701493-dev
>
> i.e. 1.9.1.2 is a tag-based build on the 1.9.1 branch (therefore it won't
> suffix the revision number and dev suffix).
>
> Given that chang
Hi Ivan,
On 7 September 2015 at 18:47, Stefan wrote:
Hi,
I'm pleased to announce the availability of a new distribution of SVN
called: "MaxSVN".
In contrast to other SVN distributions this one is a bit different since
it
aims towards being used primarily to support SVN development rather than
On 16 September 2015 at 23:12, Greg Stein wrote:
> Could I offer an opinion: the time stamps DO NOT MATTER.
>
> If a comment was posted at 15:00 or at 21:00 ... I don't care. If it was a
> Monday or a Tuesday ... I don't care. I believe I'd rather stick a fork in
> my eye, than ask somebody to spe
On Wed, Sep 16, 2015 at 11:12 PM, Greg Stein wrote:
> Could I offer an opinion: the time stamps DO NOT MATTER.
>
> If a comment was posted at 15:00 or at 21:00 ... I don't care. If it was a
> Monday or a Tuesday ... I don't care. I believe I'd rather stick a fork in
> my eye, than ask somebody to
Could I offer an opinion: the time stamps DO NOT MATTER.
If a comment was posted at 15:00 or at 21:00 ... I don't care. If it was a
Monday or a Tuesday ... I don't care. I believe I'd rather stick a fork in
my eye, than ask somebody to spend even 5 minutes on timestamps.
Cheers,
-g
On Wed, Sep 1
Ivan Zhakov wrote:
> Julian Foad wrote:
>> The time zone offset appears not to be handled correctly in converting
>> time stamps (on Dates: Created, Updated; and on Comments).
>>
>> # http://subversion.tigris.org/issues/show_bug.cgi?id=1532
>> Opened: Tue Sep 23 10:02:00 -0700 2003
>> --- Addit
On 16 September 2015 at 16:17, Julian Foad wrote:
> Stefan Hett wrote:
>> Ivan Zhakov:
>>> Please report me any problems or suggestions. Current TODO list:
>>> - Migrate attachments
>>> - Preserve history of changes
>>
>> - released versions should be marked as such (preferably with their release
Stefan Hett wrote:
> Ivan Zhakov:
>> Please report me any problems or suggestions. Current TODO list:
>> - Migrate attachments
>> - Preserve history of changes
>
> - released versions should be marked as such (preferably with their release
> date) (as stated on IRC I can lend a hand if that needs t
Overall the migration looks pretty good I would agree. I was impressed to
see things like dependencies come through pretty cleanly.
The one problem I have that I assume is related to this formatting is that
it seems like line wrapping does not happen as it normally would. So
descriptions etc see
On 16 September 2015 at 15:10, Greg Stein wrote:
> Well, the noformat in the test import looks just fine. It works, may as well
> leave that. ... But end the work there. I'm with Mark: having the issues in
> JIRA is *way* more important than further refinements and the time involved.
>
I completel
Well, the noformat in the test import looks just fine. It works, may as
well leave that. ... But end the work there. I'm with Mark: having the
issues in JIRA is *way* more important than further refinements and the
time involved.
On Wed, Sep 16, 2015 at 8:00 AM, Mark Phippard wrote:
> If what Jo
If what Johan says is all true (which I assume it is) then why not just do
a straight-up migration of issues and let things be proportional? You
could then manually correct the parts of descriptions or comments that
would be better be formatted differently ... but only if someone cares
enough.
If
Tigris runs Issuezilla which was a fork of Bugzilla.
Scarab is another tracker CollabNet started and is or was a project on
tigris. It is also included in the product but not turned on for tigris
projects. It is called "Project Tracker" in the CEE product line.
Mark
On Wed, Sep 16, 2015 at 7:07
On 9/16/2015 2:44 PM, Ivan Zhakov wrote:
On 15 September 2015 at 22:20, Ivan Zhakov wrote:
On 15 September 2015 at 20:02, Greg Stein wrote:
You can do it. File an INFRA ticket for porting our issues into JIRA, and
note that you have some content for a test load. They do test loads often
for i
That is just not true, Bert.
Subversion uses "IssueZilla" which is a CollabNet derivation of Bugzilla.
On Wed, Sep 16, 2015 at 6:07 AM, Bert Huijben wrote:
> Just noting: The issue tracker we used on tigris is based on Scarab, not
> on bugzilla.
>
> So we are not converting from bugzilla... Bug
On 15 September 2015 at 22:20, Ivan Zhakov wrote:
> On 15 September 2015 at 20:02, Greg Stein wrote:
>> You can do it. File an INFRA ticket for porting our issues into JIRA, and
>> note that you have some content for a test load. They do test loads often
>> for incoming, so they have a runbook fo
Just noting: The issue tracker we used on tigris is based on Scarab, not on
bugzilla.
So we are not converting from bugzilla... Bugzilla is just another option that
would need a different migration.
Bert
-Original Message-
From: "Johan Corveleyn"
Sent: 16-9-2015 12:08
To: "Ivan Zha
On 16 September 2015 at 12:07, Johan Corveleyn wrote:
> On Wed, Sep 16, 2015 at 11:59 AM, Ivan Zhakov wrote:
>> On 16 September 2015 at 11:32, Stefan Hett wrote:
>>> Hi,
>
> Speaking about Ivan's suggested monospace-renderer-plugin and the concern
> that it might break with a future
On Wed, Sep 16, 2015 at 12:07 PM, Johan Corveleyn wrote:
> On Wed, Sep 16, 2015 at 11:59 AM, Ivan Zhakov wrote:
>> On 16 September 2015 at 11:32, Stefan Hett wrote:
>>> Hi,
>
> Speaking about Ivan's suggested monospace-renderer-plugin and the concern
> that it might break with a futu
On Wed, Sep 16, 2015 at 11:59 AM, Ivan Zhakov wrote:
> On 16 September 2015 at 11:32, Stefan Hett wrote:
>> Hi,
Speaking about Ivan's suggested monospace-renderer-plugin and the concern
that it might break with a future version of JIRA: My experience with
JIRA
(which date
On 16 September 2015 at 11:32, Stefan Hett wrote:
> Hi,
>>>
>>> Speaking about Ivan's suggested monospace-renderer-plugin and the concern
>>> that it might break with a future version of JIRA: My experience with
>>> JIRA
>>> (which dates back to around 2005 I guess) is that Atlassian is quite
>>>
Hi,
Speaking about Ivan's suggested monospace-renderer-plugin and the concern
that it might break with a future version of JIRA: My experience with JIRA
(which dates back to around 2005 I guess) is that Atlassian is quite
reluctant with introducing changes which break plugins. So it's quite rare
On 13 September 2015 at 23:52, Stefan wrote:
> Hi Ivan,
>
Hi Stefan!
>> On 7 September 2015 at 18:47, Stefan wrote:
>>>
>>> Hi,
>>>
>>> I'm pleased to announce the availability of a new distribution of SVN
>>> called: "MaxSVN".
>>> In contrast to other SVN distributions this one is a bit differe
On 16 September 2015 at 02:43, Stefan wrote:
> Hi,
>>
>> [...]
>>
>> As to "format all descriptions as " in jira: honestly, it feels
>> like a round peg in a square hole. Jira is designed around ajax and and
>> html; I'd be concerned that future releases of jira might break the
>> renderer plugin
On 16 September 2015 at 02:19, Branko Čibej wrote:
> On 15.09.2015 23:31, Daniel Shahaf wrote:
>> Julian Foad wrote on Tue, Sep 15, 2015 at 14:23:53 +0200:
>>> First, I'd like to say I'd be happy with either of these options, and
>>> I think making a conversion to one of these at the ASF is much b
27 matches
Mail list logo
