[jira] [Commented] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-11472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082187#comment-17082187 ]

ASF subversion and git services commented on OFBIZ-11472:
---------------------------------------------------------

Commit 6b47283d1fa5f78d8e76f9eba0e93949d7636337 in ofbiz-tools's branch refs/heads/master from Swapnil Mane
[ https://gitbox.apache.org/repos/asf?p=ofbiz-tools.git;h=6b47283 ]

Implemented: Updated the deployment scripts

(OFBIZ-11472)
As we are working on setting up the demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo, make the changes in deployment scripts to honor this.

> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> -------------------------------------------------------------------
>
>                 Key: OFBIZ-11472
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11472
>             Project: OFBiz
>          Issue Type: Task
>          Components: Demo
>            Reporter: Swapnil Mane
>            Assignee: Swapnil Mane
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07.
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at https://demo-stable.ofbiz.apache.org
>  
> For this, we will need to make changes in the deployment scripts.

--
This message was sent by Atlassian Jira
(v8.3.4#803005)