> This is a limitation of Jira, everybody should be added to the contributors
> manually.
Marton, This is because of the permission scheme selected by the project and
can be changed by jira-administrator or to be precise by Infra folks. Nothing
specific to jira I think...
IIRC Hive doesn’t requ
+1
-Ayush
> On 11-Jan-2021, at 11:56 AM, Sammi Chen wrote:
>
> +1 for the new release.
>
>
> Sammi
>
>> On Fri, Jan 8, 2021 at 2:02 AM Arpit Agarwal
>> wrote:
>>
>> Hi all, it has been some time since the Ozone 1.0.0 release. Would this be
>> a good time to kick off the 1.1.0 release?
>>
Login to github, goto settings, then email.
Check you have a mail id added as primary and that is verified.
Check “Keep my email addresses private” checkbox is unchecked.
https://github.com/settings/emails
-Ayush
Sent from my iPhone
> On 17-Jan-2021, at 12:32 AM, Rui Wang wrote:
>
> Hi Commu
+1
> On 26-Jan-2021, at 2:31 PM, István Fajth wrote:
>
> I have been bought, +1 on the idea, especially as this is something that is
> a long standing thing in the jls, which is not at all hard to conform, and
> most if not all of the devs are used to the correct order.
>
> Pifta
>
> Rui Wang
+1, Sounds Good!!!
-Ayush
> On 03-Mar-2021, at 12:36 PM, Shashikant Banerjee
> wrote:
>
> +1
>
> Thanks
> Shashi
>
>> On Wed, Mar 3, 2021, 12:21 PM Dinesh Chitlangia wrote:
>>
>> +1, Go is surely being adopted very well so this can attract some new devs
>> too to contribute to Ozone.
>>
Thanx Rakesh for driving this.
Quickly tried some basic stuff with this. Looks good.
+1, Good Luck!!!
-Ayush
> On 09-Apr-2021, at 2:15 PM, Shashikant Banerjee
> wrote:
> +1
>
> Thanks
> Shashi
>
>> On Fri, Apr 9, 2021 at 1:39 PM Sadanand Shenoy <
>> sadanand.shenoy4...@gmail.com> wrote:
>>
+1(non-binding)
*Built from source.
*Verified Checksums
*Verified ozone version
*Ran basic shell commands
*Browsed through the UI.
Thanx Prashant for driving the release.
-Ayush
> On 12-Apr-2021, at 1:21 PM, Sammi Chen wrote:
>
> +1,
>
> Thanks Prashant for updating to RC2.
> One suggestion
+1, Thanx Rakesh for driving this.
-Ayush
> On 31-May-2021, at 1:50 PM, Sadanand Shenoy
> wrote:
>
> +1
>
> Thanks,
> Sadanand
>
>> On Mon, May 31, 2021, 1:28 PM Mukul Kumar Singh
>> wrote:
>>
>> +1 for the merge.
>>
>> Thanks for starting the discussion Rakesh.
>>
>> Thanks,
>>
>> Muk
Unless the effort is very high
+1 for rebase
-Ayush
> On 16-Aug-2021, at 8:30 PM, Shashikant Banerjee
> wrote:
>
> +1 for rebase
>
> Thanks
> Shashi
>
>> On Thu, Aug 12, 2021 at 2:10 PM Hui Fei wrote:
>>
>> Thanks for bringing this up.
>>
>> Share an article for introducing Rebase:
>> ht
+1
> On 27-Aug-2021, at 1:49 AM, Xiaoyu Yao wrote:
>
> +1
>
>> On Thu, Aug 26, 2021 at 12:23 PM Ethan Rose
>> wrote:
>>
>> +1
>>
>> On Thu, Aug 26, 2021 at 11:36 AM Vivek Ratnavel
>> wrote:
>>
>>> +1, thanks for volunteering Ethan!
>>>
>>>
>>> On Thu, Aug 26, 2021 at 11:35 AM Prashant P
+1(non-binding)
* Built from source
* Verified Checksums
* Ran basic shell commands
* Verified ‘ozone version’ output
Thanx Ethan for driving the release!!!
-Ayush
>
> On 16-Nov-2021, at 10:28 AM, Bharat Viswanadham wrote:
>
> +1.
>
> 1. Verified Signatures.
> 2. Built from source tarball.
+1 for merge.
Thanx Uma for driving this. Good Luck!!!
-Ayush
> On 18-Feb-2022, at 9:38 PM, Rakesh Radhakrishnan wrote:
>
> +1 for merging EC into master branch.
>
> Thanks @Uma for putting this together. Kudos to everyone who contributed to
> this feature!
>
> Best,
> Rakesh
>
>> On Tue, F
+1 for merge
-Ayush
> On 07-Apr-2022, at 11:19 AM, Bharat Viswanadham
> wrote:
>
> +1 for merge.
>
> Thanks,
> Bharat
>
>
>> On Wed, Apr 6, 2022 at 10:36 PM Tsz Wo Sze wrote:
>>
>> +1
>> We should merge it so that more people can try it. We can work on the
>> remaining tasks in the mast
Thanx Stephen for initiating this.
+1 to have specific documented compat guidelines, all 4 points makes sense to
me..
-Ayush
> On 23-Apr-2022, at 1:41 AM, Uma Maheswara Rao Gangumalla
> wrote:
>
> Hi Stephen,
>
> Thanks for starting this thread.
>
> I am +1. I agree that adding new lines
+1,
Thanks Mingchao for the initiative
-Ayush
> On 28-Jul-2022, at 12:52 PM, Sammi Chen wrote:
>
> 1
>
> Thanks Mingchao
-
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@oz
Hi Siyao,
I don’t understand the line ‘along with its artifacts in Apache archive’
Why would we want to remove it from the archives?
https://archive.apache.org/dist/hadoop/ozone/
The archive above has versions as old as 0.2.1-alpha as well.
Checked the Hadoop archives as well:
https://archive.
+1, skimmed over the code and tried some basic stuff.
Thanx Tsz-Wo for the driving this!!
-Ayush
> On 06-Dec-2022, at 7:06 AM, Arpit Agarwal wrote:
>
> +1 for merging this feature. This is an important performance improvement
> for Ozone.
>
> Nicholas, what's the plan to have streaming wri
+1
-Ayush
> On 09-Dec-2022, at 4:46 PM, mingchao zhao wrote:
>
> +1 (non-binding)
> Thanks Nicholas working on this.
>
>> On Fri, Dec 9, 2022 at 6:31 PM Sadanand Shenoy wrote:
>>
>> +1 (non-binding)
>>
>> Thanks,
>> Sadanand
>>
>>> On Fri, Dec 9, 2022 at 12:47 PM Kaijie Chen wrote:
>>>
+1(non-binding)
* Built from source
* Verified Checksums & Signatures
* Ran some basic shell commands
* Verified output of `ozone version`
* Checked licence & Notice
Thanx MingChao for driving the release. Good Luck!!!
-Ayush
On Thu, 15 Dec 2022 at 19:38, Attila Doroszlai
wrote:
> +1
>
> * Ve
Cool Stuff, Just looking at the PR Wei-chiu you plan to add a page in the
website, maybe maintaining a wiki and adding a link to that in the website
would have worked as well, just wiki's are more easy to update and maintain
so. Choice is all yours, juzz my thoughts :-)
-Ayush
On Sat, 17 Dec 202
+1
-Ayush
> On 23-Jan-2023, at 3:27 PM, Sadanand Shenoy wrote:
>
> +1 for the merge.
>
> Thanks,
> Sadanand
>
>> On Mon, Jan 23, 2023 at 3:06 PM NILOTPAL NANDI
>> wrote:
>>
>> +1 for the merge.
>>
>> Thanks,
>> Nilotpal Nandi
>>
>>> On Sat, Jan 21, 2023 at 6:08 AM Tsz Wo Sze wrote:
>>>
+1,
Makes sense,
Thanx Uma for bringing this up. Maybe the number of days to wait can vary
depending on the time of the year (vacations/weekends or so) and the
criticality of the Jira (release blocker or so), just give enough
opportunity to the reviewer to come back and that should be fine.
-Ayush
+1
-Ayush
> On 09-Feb-2023, at 7:41 AM, Neil Joshi wrote:
>
> +1
> Thanks!
> Regards,
> Neil
>
>> On Tue, Feb 7, 2023 at 8:52 PM mingchao zhao wrote:
>>
>> +1 for merge.
>>
>> On Tue, Feb 7, 2023 at 5:03 PM Uma Maheswara Rao Gangumalla <
>> umaganguma...@gmail.com> wrote:
>>
>>> +1
>>>
>
+1
-Ayush
> On 01-Mar-2023, at 1:09 AM, Siyao Meng wrote:
>
> +1
>
> -Siyao
>
>> On Feb 28, 2023 at 8:57:00 AM, Tsz Wo Sze wrote:
>>
>> +1
>> Tsz-Wo
>>
>> On Mon, Feb 27, 2023 at 11:12 PM Sadanand Shenoy
>> wrote:
>>
>> +1 for merge.
>>
>>
>> -Sadanand
>>
>>
>> On Tue, Feb 28, 2023
+1,
Sounds good to me.
-Ayush
On Wed, 15 Mar 2023 at 03:01, Ritesh Shukla
wrote:
> I recommend adding the 1.3.1 version to the target version field (sample:
> https://issues.apache.org/jira/browse/HDDS-8142) for the Jiras that should
> be part of 1.3.1
> We can review the list in the next commu
+1
Sounds cool. Amongst the ones I know Airflow does that:
https://github.com/apache/airflow/discussions
-Ayush
On Mon, 24 Apr 2023 at 11:42, Ritesh Shukla wrote:
>
> Hello folks,
>
> Sending this across for a couple of reasons
> 1. Slack and Jiras are invitations only for now
> 2. Slack message
+1 (Binding)
-Ayush
> On 02-Jun-2023, at 11:14 PM, Wei-Chiu Chuang wrote:
>
> +1 (binding)
>
> I was involved when Duong discovered the issue and proposed the solution,
> and was involved in reviewing some of the patches.
>
>> On Fri, Jun 2, 2023 at 10:35 AM Ritesh Shukla
>> wrote:
>>
>> +
>
> artifact descriptor for
> org.apache.hadoop:hadoop-build-tools:jar:3.3.9-SNAPSHOT: Could not transfer
> artifact org.apache.hadoop:hadoop-build-tools:pom:3.3.9-SNAPSHOT from/to
> maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for
> repositories: [apache.snapshots (http://repositor
Hi Attila,
Thanx for flagging this, makes sense to me. Following the Github Doc that
you shared, reached here [1]
The 4th point here:
--->
Optionally, under Allow squash merging, select the dropdown menu, then
click the format of the default squash commit message presented to
contributors when mer
Is it a Java-8 thing? or a higher Java version, I saw similar stuff
while attempting to upgrade another project from Java-8 to Java-11,
some stuff over here [1] and [2]
I don't remember exactly but I think I added jakarta.xml.bind-api &
jaxb-runtime as docletArtifact and things worked for me.
btw.
Well makes sense in a way but everytime the PR size isn't the right
metric, if you have 100 lines of code & if it bothers some core and
complex part & if there is a possibility to split, it is good to do
so, because it lets the reviewer to focus on that core & complex part
one at a time.
Sometimes
Thanx Wei-Chiu for the initiative. Definitely makes sense to move to
2.10.x line instead of 2.7, if anyone in the Hadoop ecosystem wants to
stay over in 2.x line, it shouldn't be that tough for them to move to
2.10.x from 2.7
+1 to drop Hadoop-3.2, I have heard very few people moving to this
relea
Makes sense to have policies around Jiras & PR, Having proper
descriptions & linking the related tickets and stuff like that.
Though I am not very much in favour of closing tickets right away
based on discussions in Community sync. The contributor might be a
newbie, he might be genuinely not aware
Hi Slava,
I have sent you the invite.
-Ayush
On Tue, 3 Oct 2023 at 14:41, Slava Tutrinov wrote:
>
> Hi Devs, I’d like to join jour slack channel as the mailing list is not
> very active. As far as I understand apache slack workspace is not opened
> for everyone (just for apache commiters) but I’
t; Haiyang Hu.*
> >
> > In your example "Contributed by" indicates the single author of the
> > change, there are no co-authors.
> >
> > Author: huhaiyang <...>
> > AuthorDate: Sat Jul 15 14:30:07 2023 +0800
> > Commit: GitHub
&g
+1 (Binding)
* Built from source
* Verified Checksums
* Verified Signatures
* Ran some basic shell commands.
* Ran some FS related unit tests.
* Browsed through the UI (OM/SCM/Recon)
* Skimmed over the contents of staging repo.
* Verified no code diff b/w the git tag & source tar
* Validated the o
+1
-Ayush
> On 14-Feb-2024, at 10:12 AM, Sumit Agrawal
> wrote:
>
> Hi,
>
> The contents of asf-site are automatically *generated from master and
>> committed*
>> by a GitHub Action
>> <
>> https://github.com/apache/ozone-site/blob/master/.github/workflows/regenerate.yml
>>> .
>> From there
+1
-Ayush
On Tue, 9 Jul 2024 at 08:18, Attila Doroszlai wrote:
>
> > I would like to propose merging into master the feature branch
> > HDDS-10656-atomic-key-overwrite, which was used to develop Atomic Key
> > Overwrite.
>
> Thanks for the votes so far. Would anyone else like to vote?
>
> -Atti
+1 (Binding), some minor stuff which we should fix in next release
* Built from source
* Verified Checksums
* Verified Signatures
* All source files have apache header
* No code diff b/w the git tag & the contents of src tar
(dependency-reduced-pom only in src tar, maybe that ain't required
there)
+1 (Binding)
* Built from source
* Validated Checksums
* Validated Signatures
* Validated LICENSE & NOTICE files
* Validated code diff b/w git tag & src tar [1]
* Ran some basic shell commands.
Thanx Xi Chen for driving the release. Good Luck!!!
-Ayush
[1]
It seems the Fault Injection Service
(
+1 (Binding)
* Built from source
* Verified Checksums
* Verified Signature
* Validated no code diff b/w git tag & src tar
* Verified the output of ozone version
* Ran some basic shell commands.
* Verified the NOTICE & LICENSE files
* Skimmed over the contents of ReleaseNotes, ChangeLog & maven art
+1
-Ayush
On Tue, 17 Jun 2025 at 00:21, soumitra sulav wrote:
>
> +1 for the merge of this feature.
>
> - Soumitra
>
> On Mon, Jun 16, 2025 at 11:43 PM Siyao Meng wrote:
>
> > +1
> > Thanks for all the work that has been put into this.
> >
> > -Siyao
> >
> > On Mon, Jun 16, 2025 at 10:39 AM Si
42 matches
Mail list logo
