Re: Which versions on new demo VM?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Which versions on new demo VM?

Jacques Le Roux
Administrator
Thanks Taher,

I finally see no reasons to not send this message to the dev ML. I forward your answer.

Jacques


Le 09/07/2016 à 19:00, Taher Alkhateeb a écrit :

> Hi Jacques,
>
> I suggest that we keep only two demo VMs instead of three. One for old /
> stable (13) and one for trunk and that's it. Once we branch out 16 and
> stabilize it into a release then we reshuffle things again.
>
> Under the exceptional transformational conditions we are going through, I
> think I would not bother with having too many demos up and running
>
> Regards,
>
> Taher Alkhateeb
>
> On Sat, Jul 9, 2016 at 3:48 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Hi,
>>
>> I have promised to Gavin to put in place the demos on the new VM this
>> weekend.
>>
>> I think I can easily do it with the current setting. But I wonder if we
>> could not benefit from this change to also change the versioned demos.
>>
>> On the other hand it's a bold decision because it would mean that we
>> switch R13 to old and use R14 or even R15 as "stable", which does not make
>> sense. But finally how long will we demos with so old stuff?
>>
>> Opinions?
>>
>> Later I will also put a letsencrypt script to automatically generate the
>> certificates (must be done each 3 months)
>>
>> Jacques
>>
>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: Which versions on new demo VM?

Jacques Le Roux
Administrator
It seems nobody disagreed so I will apply this KISS plan, thanks Taher

Jacques


Le 10/07/2016 à 06:53, Jacques Le Roux a écrit :

> Thanks Taher,
>
> I finally see no reasons to not send this message to the dev ML. I forward your answer.
>
> Jacques
>
>
> Le 09/07/2016 à 19:00, Taher Alkhateeb a écrit :
>> Hi Jacques,
>>
>> I suggest that we keep only two demo VMs instead of three. One for old /
>> stable (13) and one for trunk and that's it. Once we branch out 16 and
>> stabilize it into a release then we reshuffle things again.
>>
>> Under the exceptional transformational conditions we are going through, I
>> think I would not bother with having too many demos up and running
>>
>> Regards,
>>
>> Taher Alkhateeb
>>
>> On Sat, Jul 9, 2016 at 3:48 PM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>> Hi,
>>>
>>> I have promised to Gavin to put in place the demos on the new VM this
>>> weekend.
>>>
>>> I think I can easily do it with the current setting. But I wonder if we
>>> could not benefit from this change to also change the versioned demos.
>>>
>>> On the other hand it's a bold decision because it would mean that we
>>> switch R13 to old and use R14 or even R15 as "stable", which does not make
>>> sense. But finally how long will we demos with so old stuff?
>>>
>>> Opinions?
>>>
>>> Later I will also put a letsencrypt script to automatically generate the
>>> certificates (must be done each 3 months)
>>>
>>> Jacques
>>>
>>>
>>>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Which versions on new demo VM?

Pierre Smits
-1 to the proposal to remove dev branche(s) from the demo environment, as
they offer a easy (and welcome) comparison between a local dev environment
and the running release branch.

It also helps to provide generic links, as pasted urls from localhost can
result in something totally different from contributor to contributor.

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Fri, Jul 15, 2016 at 7:16 AM, Jacques Le Roux <
[hidden email]> wrote:

> It seems nobody disagreed so I will apply this KISS plan, thanks Taher
>
> Jacques
>
>
>
> Le 10/07/2016 à 06:53, Jacques Le Roux a écrit :
>
>> Thanks Taher,
>>
>> I finally see no reasons to not send this message to the dev ML. I
>> forward your answer.
>>
>> Jacques
>>
>>
>> Le 09/07/2016 à 19:00, Taher Alkhateeb a écrit :
>>
>>> Hi Jacques,
>>>
>>> I suggest that we keep only two demo VMs instead of three. One for old /
>>> stable (13) and one for trunk and that's it. Once we branch out 16 and
>>> stabilize it into a release then we reshuffle things again.
>>>
>>> Under the exceptional transformational conditions we are going through, I
>>> think I would not bother with having too many demos up and running
>>>
>>> Regards,
>>>
>>> Taher Alkhateeb
>>>
>>> On Sat, Jul 9, 2016 at 3:48 PM, Jacques Le Roux <
>>> [hidden email]> wrote:
>>>
>>> Hi,
>>>>
>>>> I have promised to Gavin to put in place the demos on the new VM this
>>>> weekend.
>>>>
>>>> I think I can easily do it with the current setting. But I wonder if we
>>>> could not benefit from this change to also change the versioned demos.
>>>>
>>>> On the other hand it's a bold decision because it would mean that we
>>>> switch R13 to old and use R14 or even R15 as "stable", which does not
>>>> make
>>>> sense. But finally how long will we demos with so old stuff?
>>>>
>>>> Opinions?
>>>>
>>>> Later I will also put a letsencrypt script to automatically generate the
>>>> certificates (must be done each 3 months)
>>>>
>>>> Jacques
>>>>
>>>>
>>>>
>>>>
>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: Which versions on new demo VM?

Deepak Dixit-3
>> suggest that we keep only two demo VMs instead of three. One for old /
>>stable (13) and one for trunk and that's it. Once we branch out 16 and
>>stabilize it into a release then we reshuffle things again.

+1

I think its good idea to keep stable release (13) and trunk on demo
instance. I see no reason to keep 14 or 15 on demo instance as we are not
going to release them in future.




Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Fri, Jul 15, 2016 at 11:53 AM, Pierre Smits <[hidden email]>
wrote:

> -1 to the proposal to remove dev branche(s) from the demo environment, as
> they offer a easy (and welcome) comparison between a local dev environment
> and the running release branch.
>
> It also helps to provide generic links, as pasted urls from localhost can
> result in something totally different from contributor to contributor.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Fri, Jul 15, 2016 at 7:16 AM, Jacques Le Roux <
> [hidden email]> wrote:
>
> > It seems nobody disagreed so I will apply this KISS plan, thanks Taher
> >
> > Jacques
> >
> >
> >
> > Le 10/07/2016 à 06:53, Jacques Le Roux a écrit :
> >
> >> Thanks Taher,
> >>
> >> I finally see no reasons to not send this message to the dev ML. I
> >> forward your answer.
> >>
> >> Jacques
> >>
> >>
> >> Le 09/07/2016 à 19:00, Taher Alkhateeb a écrit :
> >>
> >>> Hi Jacques,
> >>>
> >>> I suggest that we keep only two demo VMs instead of three. One for old
> /
> >>> stable (13) and one for trunk and that's it. Once we branch out 16 and
> >>> stabilize it into a release then we reshuffle things again.
> >>>
> >>> Under the exceptional transformational conditions we are going
> through, I
> >>> think I would not bother with having too many demos up and running
> >>>
> >>> Regards,
> >>>
> >>> Taher Alkhateeb
> >>>
> >>> On Sat, Jul 9, 2016 at 3:48 PM, Jacques Le Roux <
> >>> [hidden email]> wrote:
> >>>
> >>> Hi,
> >>>>
> >>>> I have promised to Gavin to put in place the demos on the new VM this
> >>>> weekend.
> >>>>
> >>>> I think I can easily do it with the current setting. But I wonder if
> we
> >>>> could not benefit from this change to also change the versioned demos.
> >>>>
> >>>> On the other hand it's a bold decision because it would mean that we
> >>>> switch R13 to old and use R14 or even R15 as "stable", which does not
> >>>> make
> >>>> sense. But finally how long will we demos with so old stuff?
> >>>>
> >>>> Opinions?
> >>>>
> >>>> Later I will also put a letsencrypt script to automatically generate
> the
> >>>> certificates (must be done each 3 months)
> >>>>
> >>>> Jacques
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Which versions on new demo VM?

Sharan-F
+1 for keeping only the 13.07 and the trunk.

As far as I know we never had 14.12 and 15.12 as demo environments (please correct me if I'm wrong Jacques :-) - so we are not taking anything away. Either way the branch releases are for developers and they already know how to manage, build, synch and patch the codebase themselves.

Also I'm very aware of the amount of time Jacques spends looking after the demos and fixing them  when they fail  â€“ so I'd be much happier if his workload was reduced rather than increased.

Thanks
Sharan

On 2016-07-15 09:03 (+0200), Deepak Dixit <[hidden email]> wrote:

> >> suggest that we keep only two demo VMs instead of three. One for old /
> >>stable (13) and one for trunk and that's it. Once we branch out 16 and
> >>stabilize it into a release then we reshuffle things again.
>
> +1
>
> I think its good idea to keep stable release (13) and trunk on demo
> instance. I see no reason to keep 14 or 15 on demo instance as we are not
> going to release them in future.
>
>
>
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Fri, Jul 15, 2016 at 11:53 AM, Pierre Smits <[hidden email]>
> wrote:
>
> > -1 to the proposal to remove dev branche(s) from the demo environment, as
> > they offer a easy (and welcome) comparison between a local dev environment
> > and the running release branch.
> >
> > It also helps to provide generic links, as pasted urls from localhost can
> > result in something totally different from contributor to contributor.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM <http://www.orrtiz.com>
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Fri, Jul 15, 2016 at 7:16 AM, Jacques Le Roux <
> > [hidden email]> wrote:
> >
> > > It seems nobody disagreed so I will apply this KISS plan, thanks Taher
> > >
> > > Jacques
> > >
> > >
> > >
> > > Le 10/07/2016 à 06:53, Jacques Le Roux a écrit :
> > >
> > >> Thanks Taher,
> > >>
> > >> I finally see no reasons to not send this message to the dev ML. I
> > >> forward your answer.
> > >>
> > >> Jacques
> > >>
> > >>
> > >> Le 09/07/2016 à 19:00, Taher Alkhateeb a écrit :
> > >>
> > >>> Hi Jacques,
> > >>>
> > >>> I suggest that we keep only two demo VMs instead of three. One for old
> > /
> > >>> stable (13) and one for trunk and that's it. Once we branch out 16 and
> > >>> stabilize it into a release then we reshuffle things again.
> > >>>
> > >>> Under the exceptional transformational conditions we are going
> > through, I
> > >>> think I would not bother with having too many demos up and running
> > >>>
> > >>> Regards,
> > >>>
> > >>> Taher Alkhateeb
> > >>>
> > >>> On Sat, Jul 9, 2016 at 3:48 PM, Jacques Le Roux <
> > >>> [hidden email]> wrote:
> > >>>
> > >>> Hi,
> > >>>>
> > >>>> I have promised to Gavin to put in place the demos on the new VM this
> > >>>> weekend.
> > >>>>
> > >>>> I think I can easily do it with the current setting. But I wonder if
> > we
> > >>>> could not benefit from this change to also change the versioned demos.
> > >>>>
> > >>>> On the other hand it's a bold decision because it would mean that we
> > >>>> switch R13 to old and use R14 or even R15 as "stable", which does not
> > >>>> make
> > >>>> sense. But finally how long will we demos with so old stuff?
> > >>>>
> > >>>> Opinions?
> > >>>>
> > >>>> Later I will also put a letsencrypt script to automatically generate
> > the
> > >>>> certificates (must be done each 3 months)
> > >>>>
> > >>>> Jacques
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>
> > >>
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Which versions on new demo VM?

Jacques Le Roux
Administrator
Le 15/07/2016 à 09:18, Sharan Foga a écrit :
> As far as I know we never had 14.12 and 15.12 as demo environments (please correct me if I'm wrong Jacques:-)  
Right Sharan, last are R13 as stable and R12 as old, trunk is always there but a bit hidden because it's not released

Jacques

Reply | Threaded
Open this post in threaded view
|

Re: Which versions on new demo VM?

Pierre Smits
In reply to this post by Sharan-F
Thanks for the correction, Sharan and Jacques.

I agree with not to adding to the burden of Jacques. He already does so
much for the community.

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Fri, Jul 15, 2016 at 9:18 AM, Sharan Foga <[hidden email]> wrote:

> +1 for keeping only the 13.07 and the trunk.
>
> As far as I know we never had 14.12 and 15.12 as demo environments (please
> correct me if I'm wrong Jacques :-) - so we are not taking anything away.
> Either way the branch releases are for developers and they already know how
> to manage, build, synch and patch the codebase themselves.
>
> Also I'm very aware of the amount of time Jacques spends looking after the
> demos and fixing them  when they fail  – so I'd be much happier if his
> workload was reduced rather than increased.
>
> Thanks
> Sharan
>
> On 2016-07-15 09:03 (+0200), Deepak Dixit <[hidden email]>
> wrote:
> > >> suggest that we keep only two demo VMs instead of three. One for old /
> > >>stable (13) and one for trunk and that's it. Once we branch out 16 and
> > >>stabilize it into a release then we reshuffle things again.
> >
> > +1
> >
> > I think its good idea to keep stable release (13) and trunk on demo
> > instance. I see no reason to keep 14 or 15 on demo instance as we are not
> > going to release them in future.
> >
> >
> >
> >
> > Thanks & Regards
> > --
> > Deepak Dixit
> > www.hotwaxsystems.com
> >
> > On Fri, Jul 15, 2016 at 11:53 AM, Pierre Smits <[hidden email]>
> > wrote:
> >
> > > -1 to the proposal to remove dev branche(s) from the demo environment,
> as
> > > they offer a easy (and welcome) comparison between a local dev
> environment
> > > and the running release branch.
> > >
> > > It also helps to provide generic links, as pasted urls from localhost
> can
> > > result in something totally different from contributor to contributor.
> > >
> > > Best regards,
> > >
> > > Pierre Smits
> > >
> > > ORRTIZ.COM <http://www.orrtiz.com>
> > > OFBiz based solutions & services
> > >
> > > OFBiz Extensions Marketplace
> > > http://oem.ofbizci.net/oci-2/
> > >
> > > On Fri, Jul 15, 2016 at 7:16 AM, Jacques Le Roux <
> > > [hidden email]> wrote:
> > >
> > > > It seems nobody disagreed so I will apply this KISS plan, thanks
> Taher
> > > >
> > > > Jacques
> > > >
> > > >
> > > >
> > > > Le 10/07/2016 à 06:53, Jacques Le Roux a écrit :
> > > >
> > > >> Thanks Taher,
> > > >>
> > > >> I finally see no reasons to not send this message to the dev ML. I
> > > >> forward your answer.
> > > >>
> > > >> Jacques
> > > >>
> > > >>
> > > >> Le 09/07/2016 à 19:00, Taher Alkhateeb a écrit :
> > > >>
> > > >>> Hi Jacques,
> > > >>>
> > > >>> I suggest that we keep only two demo VMs instead of three. One for
> old
> > > /
> > > >>> stable (13) and one for trunk and that's it. Once we branch out 16
> and
> > > >>> stabilize it into a release then we reshuffle things again.
> > > >>>
> > > >>> Under the exceptional transformational conditions we are going
> > > through, I
> > > >>> think I would not bother with having too many demos up and running
> > > >>>
> > > >>> Regards,
> > > >>>
> > > >>> Taher Alkhateeb
> > > >>>
> > > >>> On Sat, Jul 9, 2016 at 3:48 PM, Jacques Le Roux <
> > > >>> [hidden email]> wrote:
> > > >>>
> > > >>> Hi,
> > > >>>>
> > > >>>> I have promised to Gavin to put in place the demos on the new VM
> this
> > > >>>> weekend.
> > > >>>>
> > > >>>> I think I can easily do it with the current setting. But I wonder
> if
> > > we
> > > >>>> could not benefit from this change to also change the versioned
> demos.
> > > >>>>
> > > >>>> On the other hand it's a bold decision because it would mean that
> we
> > > >>>> switch R13 to old and use R14 or even R15 as "stable", which does
> not
> > > >>>> make
> > > >>>> sense. But finally how long will we demos with so old stuff?
> > > >>>>
> > > >>>> Opinions?
> > > >>>>
> > > >>>> Later I will also put a letsencrypt script to automatically
> generate
> > > the
> > > >>>> certificates (must be done each 3 months)
> > > >>>>
> > > >>>> Jacques
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>
> > > >>
> > > >
> > >
> >
>