HI Swapnil, Your update of OFBIZ-11472 made me wonder about the OFBiz sprints. See [1]. Shoul tickets in the section 'Issues not completed' not be pushed back to the backlog?
[1] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=318&projectKey=OFBIZ&view=reporting&chart=sprintRetrospective&sprint=601 Pierre Smits ORRTIZ.COM <http://www.orrtiz.com> OFBiz based solutions & services OEM - The OFBiz Extensions Marketplace1 http://oem.ofbizci.net/oci-2/ 1 not affiliated to (and not endorsed by) the OFBiz project On Wed, May 20, 2020 at 8:12 PM Swapnil Mane (Jira) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/OFBIZ-11472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Swapnil Mane updated OFBIZ-11472: > --------------------------------- > Sprint: OFBiz Community Day (May 2020) > > > 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) >
