Probably will in some form or another.
-- DM
> On Mar 3, 2017, at 9:37 AM, David Haslam wrote:
>
> Why not make this a permanent URL in addition to the original one?
>
> David
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade
Why not make this a permanent URL in addition to the original one?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade-tp4656681p4656891.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
I can access that now. Thanks.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade-tp4656681p4656850.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel mailing list
The tracker did not restart when the server rebooted. I think I fixed that but
don’t want to reboot the server to find out.
Still at tracker.crosswire.org.
In Him,
DM
> On Feb 28, 2017, at 6:29 AM, David Haslam wrote:
>
> I cannot access the tracker at either URL today!
>
> http://tr
I cannot access the tracker at either URL today!
http://tracker.crosswire.org/
http://www.crosswire.org/tracker/
What's the problem that causes this to be 503 Unavailable?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade-tp4656681p46
Thanks, DM.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade-tp4656681p4656794.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel mailing list: sword-devel@cross
Temporary address tracker.crosswire.org.
Cent from my fone so theer mite be tipos. ;)
> On Feb 22, 2017, at 4:28 AM, David Haslam wrote:
>
> I still cannot access the CrossWire Bug Tracker.
>
> Please advise when this is going to be fixed.
>
> Best regards,
>
> David
>
>
>
> --
> View th
> Von: "David Haslam"
> Please advise when this is going to be fixed
I second this. Any discussion re a soon to come release leads usually to a
plethora of bug fixes. This is currently impossible
Peter
___
sword-devel mailing list: sword-devel@cros
I still cannot access the CrossWire Bug Tracker.
Please advise when this is going to be fixed.
Best regards,
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade-tp4656681p4656783.html
Sent from the SWORD Dev mailing list archive at Nabbl
Still unavailable to me!
503 error.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade-tp4656681p4656704.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel mailin
Still in process. Hoped to have it done last Sunday.
-- DM
> On Feb 14, 2017, at 2:00 PM, David Haslam wrote:
>
> Did the JIRA update go according to plan?
>
> David
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade-tp4656681p
Did the JIRA update go according to plan?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade-tp4656681p4656682.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel m
I’ll be in the process of upgrading Jira to the latest version. During that
time it won’t be available for creating or changing issues. It may be down.
In Him,
DM Smith
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mai
13 matches
Mail list logo
