Re: Are we ready to publish a new release (16.11.04)?

[Rishi Solanki]

+1.

Thanks!

Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co

On Wed, Dec 20, 2017 at 2:15 AM, Michael Brohl 
wrote:

> +1
>
> Thanks,
>
> Michael
>
>
> Am 19.12.17 um 16:43 schrieb Jacopo Cappellato:
>
> Hi all,
>>
>> we have published our last release mostly 6 months ago and since then we
>> have merged several bug fixes to our 16.11 branch: I think it is time to
>> publish a new one!
>>
>> If there are no objections I am going to prepare the release files in the
>> next few days and then we will start the release vote: if you think we
>> should backport fixes to that branch this is the right time to do it
>> before
>> we start the release process.
>>
>> Kind regards,
>>
>> Jacopo
>>
>>
>
>

Re: Are we ready to publish a new release (16.11.04)?

[Jacques Le Roux]

Le 20/12/2017 à 10:41, Michael Brohl a écrit :

Hi Jacques,

are these bugs fixed in trunk and not just not backported?

I don't know, too much cases to review


Else we should go on with a new release and backport once they are fixed in 
trunk.

Yep



What makes you think that this would be the last 16.11 release?

Was just a guess :) See my answer to Jacopo, it's OK with me.

Jacques


Regards,

Michael


Am 20.12.17 um 09:11 schrieb Jacques Le Roux:

Hi Jacopo,

We have 35 bugs with patches available and priority >= Major

I want to check them before plussing because this will be our last R16 release 
I guess

Thanks

Jacques


Le 19/12/2017 à 16:43, Jacopo Cappellato a écrit :

Hi all,

we have published our last release mostly 6 months ago and since then we
have merged several bug fixes to our 16.11 branch: I think it is time to
publish a new one!

If there are no objections I am going to prepare the release files in the
next few days and then we will start the release vote: if you think we
should backport fixes to that branch this is the right time to do it before
we start the release process.

Kind regards,

Jacopo

Re: Are we ready to publish a new release (16.11.04)?

[Jacques Le Roux]

Then that's OK with me, I'll have more time to review these 35 cases...

+1

Jacques


Le 20/12/2017 à 11:05, Jacopo Cappellato a écrit :

On Wed, Dec 20, 2017 at 9:11 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi Jacopo,

We have 35 bugs with patches available and priority >= Major

I want to check them before plussing because this will be our last R16
release I guess


I think we can keep this branch alive for more time since it is the only
active release branch and the new one will need to be stabilized.

Jacopo



Thanks

Jacques



Le 19/12/2017 à 16:43, Jacopo Cappellato a écrit :


Hi all,

we have published our last release mostly 6 months ago and since then we
have merged several bug fixes to our 16.11 branch: I think it is time to
publish a new one!

If there are no objections I am going to prepare the release files in the
next few days and then we will start the release vote: if you think we
should backport fixes to that branch this is the right time to do it
before
we start the release process.

Kind regards,

Jacopo

Re: Are we ready to publish a new release (16.11.04)?

[Jacopo Cappellato]

On Wed, Dec 20, 2017 at 9:11 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi Jacopo,
>
> We have 35 bugs with patches available and priority >= Major
>
> I want to check them before plussing because this will be our last R16
> release I guess
>

I think we can keep this branch alive for more time since it is the only
active release branch and the new one will need to be stabilized.

Jacopo


>
> Thanks
>
> Jacques
>
>
>
> Le 19/12/2017 à 16:43, Jacopo Cappellato a écrit :
>
>> Hi all,
>>
>> we have published our last release mostly 6 months ago and since then we
>> have merged several bug fixes to our 16.11 branch: I think it is time to
>> publish a new one!
>>
>> If there are no objections I am going to prepare the release files in the
>> next few days and then we will start the release vote: if you think we
>> should backport fixes to that branch this is the right time to do it
>> before
>> we start the release process.
>>
>> Kind regards,
>>
>> Jacopo
>>
>>
>

Re: Are we ready to publish a new release (16.11.04)?

[Michael Brohl]

Hi Jacques,

are these bugs fixed in trunk and not just not backported?

Else we should go on with a new release and backport once they are fixed 
in trunk.


What makes you think that this would be the last 16.11 release?

Regards,

Michael


Am 20.12.17 um 09:11 schrieb Jacques Le Roux:

Hi Jacopo,

We have 35 bugs with patches available and priority >= Major

I want to check them before plussing because this will be our last R16 
release I guess


Thanks

Jacques


Le 19/12/2017 à 16:43, Jacopo Cappellato a écrit :

Hi all,

we have published our last release mostly 6 months ago and since then we
have merged several bug fixes to our 16.11 branch: I think it is time to
publish a new one!

If there are no objections I am going to prepare the release files in 
the

next few days and then we will start the release vote: if you think we
should backport fixes to that branch this is the right time to do it 
before

we start the release process.

Kind regards,

Jacopo








smime.p7s
Description: S/MIME Cryptographic Signature

Re: Are we ready to publish a new release (16.11.04)?

[Jacques Le Roux]

Hi Jacopo,

We have 35 bugs with patches available and priority >= Major

I want to check them before plussing because this will be our last R16 release 
I guess

Thanks

Jacques


Le 19/12/2017 à 16:43, Jacopo Cappellato a écrit :

Hi all,

we have published our last release mostly 6 months ago and since then we
have merged several bug fixes to our 16.11 branch: I think it is time to
publish a new one!

If there are no objections I am going to prepare the release files in the
next few days and then we will start the release vote: if you think we
should backport fixes to that branch this is the right time to do it before
we start the release process.

Kind regards,

Jacopo

Re: Are we ready to publish a new release (16.11.04)?

[Vaibhav Jain]

+1

Thanks & Regards,

Vaibhav Jain
Hotwax Systems,
vaibhav.j...@hotwaxsystems.com

On Wed, Dec 20, 2017 at 11:17 AM, Aditya Sharma <
aditya.sha...@hotwaxsystems.com> wrote:

> +1
>
> Thanks and Regards,
>
> *Aditya Sharma* | Enterprise Software Engineer
> HotWax Commerce  by HotWax Systems
> 
>
> 
>
> On Wed, Dec 20, 2017 at 10:38 AM, Swapnil Mane <
> swapnil.m...@hotwaxsystems.com> wrote:
>
> > +1
> >
> >
> > - Best Regards,
> > Swapnil M Mane
> >
> > On Tue, Dec 19, 2017 at 9:13 PM, Jacopo Cappellato <
> > jacopo.cappell...@hotwaxsystems.com> wrote:
> >
> > > Hi all,
> > >
> > > we have published our last release mostly 6 months ago and since then
> we
> > > have merged several bug fixes to our 16.11 branch: I think it is time
> to
> > > publish a new one!
> > >
> > > If there are no objections I am going to prepare the release files in
> the
> > > next few days and then we will start the release vote: if you think we
> > > should backport fixes to that branch this is the right time to do it
> > before
> > > we start the release process.
> > >
> > > Kind regards,
> > >
> > > Jacopo
> > >
> >
>

Re: Are we ready to publish a new release (16.11.04)?

[Aditya Sharma]

+1

Thanks and Regards,

*Aditya Sharma* | Enterprise Software Engineer
HotWax Commerce  by HotWax Systems




On Wed, Dec 20, 2017 at 10:38 AM, Swapnil Mane <
swapnil.m...@hotwaxsystems.com> wrote:

> +1
>
>
> - Best Regards,
> Swapnil M Mane
>
> On Tue, Dec 19, 2017 at 9:13 PM, Jacopo Cappellato <
> jacopo.cappell...@hotwaxsystems.com> wrote:
>
> > Hi all,
> >
> > we have published our last release mostly 6 months ago and since then we
> > have merged several bug fixes to our 16.11 branch: I think it is time to
> > publish a new one!
> >
> > If there are no objections I am going to prepare the release files in the
> > next few days and then we will start the release vote: if you think we
> > should backport fixes to that branch this is the right time to do it
> before
> > we start the release process.
> >
> > Kind regards,
> >
> > Jacopo
> >
>

Re: Are we ready to publish a new release (16.11.04)?

[Swapnil Mane]

+1


- Best Regards,
Swapnil M Mane

On Tue, Dec 19, 2017 at 9:13 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> Hi all,
>
> we have published our last release mostly 6 months ago and since then we
> have merged several bug fixes to our 16.11 branch: I think it is time to
> publish a new one!
>
> If there are no objections I am going to prepare the release files in the
> next few days and then we will start the release vote: if you think we
> should backport fixes to that branch this is the right time to do it before
> we start the release process.
>
> Kind regards,
>
> Jacopo
>

Re: Are we ready to publish a new release (16.11.04)?

[Deepak Dixit]

+1

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

On Wed, Dec 20, 2017 at 10:05 AM, Taher Alkhateeb <
slidingfilame...@gmail.com> wrote:

> +1
>
> On Dec 20, 2017 7:17 AM, "Ashish Vijaywargiya" <
> ashish.vijaywarg...@hotwaxsystems.com> wrote:
>
> > +1
> >
> > --
> > Kind Regards
> > Ashish Vijaywargiya
> > HotWax Systems - est. 1997 
> >
> >
> > On Tue, Dec 19, 2017 at 9:13 PM, Jacopo Cappellato <
> > jacopo.cappell...@hotwaxsystems.com> wrote:
> >
> > > Hi all,
> > >
> > > we have published our last release mostly 6 months ago and since then
> we
> > > have merged several bug fixes to our 16.11 branch: I think it is time
> to
> > > publish a new one!
> > >
> > > If there are no objections I am going to prepare the release files in
> the
> > > next few days and then we will start the release vote: if you think we
> > > should backport fixes to that branch this is the right time to do it
> > before
> > > we start the release process.
> > >
> > > Kind regards,
> > >
> > > Jacopo
> > >
> >
>

Re: Are we ready to publish a new release (16.11.04)?

[Taher Alkhateeb]

+1

On Dec 20, 2017 7:17 AM, "Ashish Vijaywargiya" <
ashish.vijaywarg...@hotwaxsystems.com> wrote:

> +1
>
> --
> Kind Regards
> Ashish Vijaywargiya
> HotWax Systems - est. 1997 
>
>
> On Tue, Dec 19, 2017 at 9:13 PM, Jacopo Cappellato <
> jacopo.cappell...@hotwaxsystems.com> wrote:
>
> > Hi all,
> >
> > we have published our last release mostly 6 months ago and since then we
> > have merged several bug fixes to our 16.11 branch: I think it is time to
> > publish a new one!
> >
> > If there are no objections I am going to prepare the release files in the
> > next few days and then we will start the release vote: if you think we
> > should backport fixes to that branch this is the right time to do it
> before
> > we start the release process.
> >
> > Kind regards,
> >
> > Jacopo
> >
>

Re: Are we ready to publish a new release (16.11.04)?

[Ashish Vijaywargiya]

+1

--
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997 


On Tue, Dec 19, 2017 at 9:13 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> Hi all,
>
> we have published our last release mostly 6 months ago and since then we
> have merged several bug fixes to our 16.11 branch: I think it is time to
> publish a new one!
>
> If there are no objections I am going to prepare the release files in the
> next few days and then we will start the release vote: if you think we
> should backport fixes to that branch this is the right time to do it before
> we start the release process.
>
> Kind regards,
>
> Jacopo
>

Re: Are we ready to publish a new release (16.11.04)?

[Michael Brohl]

+1

Thanks,

Michael


Am 19.12.17 um 16:43 schrieb Jacopo Cappellato:

Hi all,

we have published our last release mostly 6 months ago and since then we
have merged several bug fixes to our 16.11 branch: I think it is time to
publish a new one!

If there are no objections I am going to prepare the release files in the
next few days and then we will start the release vote: if you think we
should backport fixes to that branch this is the right time to do it before
we start the release process.

Kind regards,

Jacopo






smime.p7s
Description: S/MIME Cryptographic Signature