We are bumping the version because there is some change in the source to
fix one of the gradle task.
Regards,
Adi
On 09-May-2016 9:16 am, "Roman Shaposhnik" wrote:
> One question: are you bumping the version # to 0.1.2-incubating just
> because of that?
>
> It is fine to
One question: are you bumping the version # to 0.1.2-incubating just
because of that?
It is fine to do so, but I wonder whether RC# will help achieve the same without
version # proliferation.
Thanks,
Roman.
On Fri, May 6, 2016 at 5:09 AM, Nazeer Shaik
Hi Jim,
We have used tar for 0.1.2-incubating release.
On Fri, May 6, 2016 at 5:31 PM, Jim Jagielski wrote:
> Would it make sense to consider using tar instead of zip ??
>
>
> > On May 6, 2016, at 1:49 AM, Nazeer Shaik <
> nazeer.sh...@confluxtechnologies.com> wrote:
> >
>
Would it make sense to consider using tar instead of zip ??
> On May 6, 2016, at 1:49 AM, Nazeer Shaik
> wrote:
>
> Hi all,
>
> You are seeing the mentioned issues because we have prepared the release on
> windows machine. But we don't see any issues if
Hi all,
You are seeing the mentioned issues because we have prepared the release on
windows machine. But we don't see any issues if we prepare same release on
Linux machine. Even the mentioned test case passes without any code change.
*So we are withdrawing the current release from voting.*
We
+1
On Wed, May 4, 2016, 12:43 AM Ed Cable wrote:
> +1
> On May 3, 2016 4:09 AM, "Nazeer Shaik" <
> nazeer.sh...@confluxtechnologies.com>
> wrote:
>
> > Hello All
> >
> > We have addressed issues with Notice & License files and prepared
> > 0.1.1-incubating release for
+1
On May 3, 2016 4:09 AM, "Nazeer Shaik"
wrote:
> Hello All
>
> We have addressed issues with Notice & License files and prepared
> 0.1.1-incubating release for FINERACT.
> The files are hosted at
>
>