Rich Bowen wrote:
> I suspect that you could do this with a combination of:
>
> * mod_rewrite RewriteRule [P] (proxy) rules [...]
> * mod_substitute, or mod_proxy_html rules to munge the content [...]
I did spend some time playing around with that sort of magic and managed to get
some parts of J
There's two possible approaches that come to mind
I suspect that you could do this with a combination of:
* mod_rewrite RewriteRule [P] (proxy) rules
RewriteRule ^/issue[^A-Za-z0-9]?(\d+)$
https://issues.apache.org/jira/browse/SVN-$1 [P,L]
ProxyPassReverse /issue https://issues.apache.org/ji
In Apache Subversion's .htaccess we have this RedirectMatch rule:
RedirectMatch ^/issue[^A-Za-z0-9]?(\d+)$
https://issues.apache.org/jira/browse/SVN-$1
It redirects a URL like
https://subversion.apache.org/issue/4567
to
https://issues.apache.org/jira/browse/SVN-4567
Why? Human-friendly, tec
er only tracks Jira issues for FINERACT, not FINCN
> --
>
> Key: COMDEV-297
> URL: https://issues.apache.org/jira/browse/COMDEV-297
> Project: Community Development
sy Board Report helper only tracks Jira issues for FINERACT, not FINCN
> --
>
> Key: COMDEV-297
> URL: https://issues.apache.org/jira/browse/COMDEV-297
> Project
Whimsy Board Report helper only tracks Jira issues for FINERACT, not FINCN
> --
>
> Key: COMDEV-297
> URL: https://issues.apache.org/jira/browse/COMDEV-297
> Pro
quot;none". The project category for FINERACT is
correct.
I can't change that setting though; the note says I would need to be a Jira
administrator. So back to INFRA?
> Whimsy Board Report helper only tracks Jira issues f
JIRA.
> Whimsy Board Report helper only tracks Jira issues for FINERACT, not FINCN
> --
>
> Key: COMDEV-297
> URL: https://issues.apache.org/jira/browse/COMDEV-297
>
Myrle Krantz created COMDEV-297:
---
Summary: Whimsy Board Report helper only tracks Jira issues for
FINERACT, not FINCN
Key: COMDEV-297
URL: https://issues.apache.org/jira/browse/COMDEV-297
Project
On Tue, Jan 23, 2018 at 02:41:12PM +0100, Bertrand Delacretaz wrote:
> On Tue, Jan 23, 2018 at 1:39 PM, Isabel Drost-Fromm wrote:
> > ...Would it
> > make sense to close the ones that haven't received any activity since
> > 2016?...
>
> +1, if needed they can be reopened or recreated.
Done - it
On Tue, Jan 23, 2018 at 1:39 PM, Isabel Drost-Fromm wrote:
> ...Would it
> make sense to close the ones that haven't received any activity since 2016?...
+1, if needed they can be reopened or recreated.
-Bertrand
-
To unsubscri
Isabel Drost-Fromm wrote on 1/23/18 7:39 AM:
> Hi,
>
> within the COMDEV Jira there are a couple JIRA issues that haven't received
> any
> comments in the past few years, in addition there are a couple issues that
> based
> on their description or labels were created
+1
On Tue, Jan 23, 2018 at 7:39 PM, Isabel Drost-Fromm
wrote:
> Hi,
>
> within the COMDEV Jira there are a couple JIRA issues that haven't
> received any
> comments in the past few years, in addition there are a couple issues that
> based
> on their description or la
Hi,
within the COMDEV Jira there are a couple JIRA issues that haven't received any
comments in the past few years, in addition there are a couple issues that based
on their description or labels were created for GSoC in previous years. Would it
make sense to close the ones that haven'
On 05/11/17 16:34, Shane Curcuru wrote:
Question: What to do about past GSOC issues that have had some work done
on them? There are a few GSOC issues for *other* projects in the COMDEV
JIRA - from the project perspective, they're no longer valid, but I'd
hate to blindly close an issue if some
Question: What to do about past GSOC issues that have had some work done
on them? There are a few GSOC issues for *other* projects in the COMDEV
JIRA - from the project perspective, they're no longer valid, but I'd
hate to blindly close an issue if some student is still hoping for
feedback or some
Hi All
I think it would be good for us to start reviewing and tidying up the list of
open issues we have in our ComDev Jira to see if they are still valid, need
updating or simply need to be closed.
Having visible tasks that we need to focus on or are currently working on in
our Jira also open
On Sat, Mar 23, 2013 at 9:46 AM, Bertrand Delacretaz
wrote:
> On Fri, Mar 22, 2013 at 6:46 PM, Luciano Resende wrote:
>> I noticed the JIRA issues are being mailed to our ComDev committs list
>> instead of dev list.
>>
>> Is this the expected behavior ?
>
>
d Delacretaz <
> bdelacre...@apache.org> wrote:
>
>> On Fri, Mar 22, 2013 at 6:46 PM, Luciano Resende
>> wrote:
>> > I noticed the JIRA issues are being mailed to our ComDev committs list
>> > instead of dev list.
>> >
>> > Is this the expected
Is there any guidelines on what goes to ComDev commits list and dev list
for newcomers?
On Sun, Mar 24, 2013 at 12:46 AM, Bertrand Delacretaz <
bdelacre...@apache.org> wrote:
> On Fri, Mar 22, 2013 at 6:46 PM, Luciano Resende
> wrote:
> > I noticed the JIRA issues are being ma
On Fri, Mar 22, 2013 at 6:46 PM, Luciano Resende wrote:
> I noticed the JIRA issues are being mailed to our ComDev committs list
> instead of dev list.
>
> Is this the expected behavior ?
Personally I like it, it avoids cluttering this list's archives.
-Bertrand
I noticed the JIRA issues are being mailed to our ComDev committs list
instead of dev list.
Is this the expected behavior ?
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
22 matches
Mail list logo
