hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Re: Updated 2.8.0-SNAPSHOT artifact
Date Wed, 02 Nov 2016 14:04:51 GMT
I do kind of concur, but also think we need to consider whether its time to increase the jackson
2.x version ( HADOOP-12705 ).

Whether we do or don't, there will be classpath conflicts with downstream apps (hello HBase!
Hello Spark!) —but we get them already.

All that staying on an older one is doing is stopping us pick up later versions of other libraries
(HADOOP-13050).

Of course, if people are happy with upgrading Jackson, there's an issue with which one: 2.8.x
appears to have some API compatibilities, which is significant. I'm a lot happier with JAR
updates that are at least compile time compatible, as they don't break linking so much

On 2 Nov 2016, at 00:05, Zhe Zhang <zhe.zhang.research@gmail.com<mailto:zhe.zhang.research@gmail.com>>
wrote:

I think recutting branch-2.8 from branch-2 is a good idea. We are running
2.6.x in production, and as a result we spend quite some effort for each
patch we want to backport (branch-2 => branch-2.8 => branch-2.7).

On Mon, Oct 31, 2016 at 1:20 AM Brahma Reddy Battula <
brahmareddy.battula@huawei.com<mailto:brahmareddy.battula@huawei.com>> wrote:

Thanks Akira and Karthik for replies.


If there is no significant benefit over current branch-2.8 ,re-cutting
will be an good idea, As we can reduce the maintenance effort.



--Brahma Reddy Battula


-----Original Message-----
From: Akira Ajisaka [mailto:ajisakaa@oss.nttdata.co.jp]
Sent: 31 October 2016 14:06
To: Karthik Kambatla
Cc: Brahma Reddy Battula; Vinod Kumar Vavilapalli;
common-dev@hadoop.apache.org<mailto:common-dev@hadoop.apache.org>; hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>;
mapreduce-dev@hadoop.apache.org<mailto:mapreduce-dev@hadoop.apache.org>; yarn-dev@hadoop.apache.org<mailto:yarn-dev@hadoop.apache.org>
Subject: Re: Updated 2.8.0-SNAPSHOT artifact

Thanks Karthik for the comment.

Pros:

* (Probably) we can release 2.8.0 earlier.

  * New feature in 2.8.0 will be available sooner.
  * We can deprecate APIs sooner. After 2.8.0 is released, we can remove
them from trunk.

Cons:

* Maintenance cost becomes higher because # of branches becomes more.
* New feature in 2.9.0 will be available later

I'm okay with either releasing current branch-2.8 or re-cutting it.

Thoughts?

Regards,
Akira

On 10/26/16 07:30, Karthik Kambatla wrote:
Is there value in releasing current branch-2.8? Aren't we better off
re-cutting the branch off of branch-2?

On Tue, Oct 25, 2016 at 12:20 AM, Akira Ajisaka
<ajisakaa@oss.nttdata.co.jp<mailto:ajisakaa@oss.nttdata.co.jp>>
wrote:

It's almost a year since branch-2.8 has cut.
I'm thinking we need to release 2.8.0 ASAP.

According to the following list, there are 5 blocker and 6 critical
issues.
https://issues.apache.org/jira/issues/?filter=12334985

Regards,
Akira


On 10/18/16 10:47, Brahma Reddy Battula wrote:

Hi Vinod,

Any plan on first RC for branch-2.8 ? I think, it has been long time.




--Brahma Reddy Battula

-----Original Message-----
From: Vinod Kumar Vavilapalli [mailto:vinodkv@apache.org]
Sent: 20 August 2016 00:56
To: Jonathan Eagles
Cc: common-dev@hadoop.apache.org
Subject: Re: Updated 2.8.0-SNAPSHOT artifact

Jon,

That is around the time when I branched 2.8, so I guess you were
getting SNAPSHOT artifacts till then from the branch-2 nightly builds.

If you need it, we can set up SNAPSHOT builds. Or just wait for the
first RC, which is around the corner.

+Vinod

On Jul 28, 2016, at 4:27 PM, Jonathan Eagles <jeagles@gmail.com>
wrote:

Latest snapshot is uploaded in Nov 2015, but checkins are still
coming in quite frequently.
https://repository.apache.org/content/repositories/snapshots/org/ap
ach
e/hadoop/hadoop-yarn-api/

Are there any plans to start producing updated SNAPSHOT artifacts
for current hadoop development lines?



--------------------------------------------------------------------
- To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org<mailto:common-dev-unsubscribe@hadoop.apache.org>
For additional commands, e-mail: common-dev-help@hadoop.apache.org<mailto:common-dev-help@hadoop.apache.org>


--------------------------------------------------------------------
- To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org<mailto:common-dev-unsubscribe@hadoop.apache.org>
For additional commands, e-mail: common-dev-help@hadoop.apache.org<mailto:common-dev-help@hadoop.apache.org>



---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org<mailto:mapreduce-dev-unsubscribe@hadoop.apache.org>
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org<mailto:mapreduce-dev-help@hadoop.apache.org>




--
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message