phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Flavio Pompermaier <pomperma...@okkam.it>
Subject Re: Cloudera parcel update
Date Mon, 11 Dec 2017 19:22:23 GMT
Can simeone replay correctly to this topic please?
http://community.cloudera.com/t5/Cloudera-Labs/Apache-Phoenix-Support-for-CDH-5-8-x-5-9x-5-10-x-5-11-x/m-p/62687#M416?eid=1&aid=1

On 9 Nov 2017 21:36, "Pedro Boado" <pedro.boado@gmail.com> wrote:

> I'll open a Jira ticket and put together a pull request in the next few
> days for Phoenix 4.11 + cdh 5.11.2 parcel.
>
> Then I'll start working on 4.12
>
> Sorry, I couldn't work on this in the last two weeks.
>
>
>
> On 9 Nov 2017 15:51, "James Taylor" <jamestaylor@apache.org> wrote:
>
>> I agree with JMS and there is interest from the PMC, but no bandwidth to
>> do the work - we’d look toward others like you to do the work of putting
>> together an initial pull request, regular pulls to keep things in sync,
>> RMing releases, etc. These types of contributions would earn merit toward a
>> committership and eventual nomination for PMC (that’s how the ASF works).
>> The files would of course be hosted on Apache infrastructure (just like our
>> current releases and repos).
>>
>> On Thu, Nov 9, 2017 at 6:15 AM Jean-Marc Spaggiari <
>> jean-marc@spaggiari.org> wrote:
>>
>>> We "simply" need to have a place to host the file, right? From a code
>>> perspective, it can be another branch in the same repo?
>>>
>>> 2017-11-09 8:48 GMT-05:00 Flavio Pompermaier <pompermaier@okkam.it>:
>>>
>>>> No interest from Phoenix PMCs to provide support to the creation of
>>>> official Cloudera parcels (at least from Phoenix side)...?
>>>>
>>>> On Tue, Oct 31, 2017 at 8:09 AM, Flavio Pompermaier <
>>>> pompermaier@okkam.it> wrote:
>>>>
>>>>> Anyone from Phoenix...?
>>>>>
>>>>> On 27 Oct 2017 16:47, "Pedro Boado" <pedro.boado@gmail.com> wrote:
>>>>>
>>>>>> For creating a CDH parcel repository the only thing needed is a web
>>>>>> server where the parcels and the manifest.json is published. But
we need
>>>>>> one.
>>>>>>
>>>>>> I'm in of course. Who can help onboarding this changes and publishing
>>>>>> etc and getting users to push changes to the project? How do you
do this in
>>>>>> Phoenix? Via another mail list, right?
>>>>>>
>>>>>> Defining regression strategy is probably the most complex bit. And
>>>>>> automating it is even more complex I think. This is where more work
is
>>>>>> needed.
>>>>>>
>>>>>> On 27 Oct 2017 15:20, "Jean-Marc Spaggiari" <jean-marc@spaggiari.org>
>>>>>> wrote:
>>>>>>
>>>>>>> See below.
>>>>>>>
>>>>>>> 2017-10-27 8:45 GMT-04:00 Flavio Pompermaier <pompermaier@okkam.it>:
>>>>>>>
>>>>>>>> I just need someone who tells which git repository to use,
the
>>>>>>>> branching/tagging policy, what should be done to release
a parcel (i.e.
>>>>>>>> compile, test ok, update docs, etc). For example, I need
someone who says:
>>>>>>>> to release a Phoenix CDH  parcel the process is this:
>>>>>>>>
>>>>>>>> 1. use this repo (e.g.https://github.com/pboado
>>>>>>>> /phoenix-for-cloudera
>>>>>>>> <https://github.com/pboado/phoenix-for-cloudera/tree/4.11-cdh5.11.2>
>>>>>>>>  or https://github.com/apahce/phoenix)
>>>>>>>>
>>>>>>>
>>>>>>> Well, if Apache Phoenix maintains it, I feel this should be moved
>>>>>>> under the Apache Phoenix git repository, right?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 2. create one or more branches for each supported release
(i.e.
>>>>>>>> 4.11-cdh-5.10 and 4.11-cdh-5.11)
>>>>>>>>     - this imply to create an official compatibility
>>>>>>>> matrix...obviously it doesn't make sense to issue a 4.11-cdh-4.1
for
>>>>>>>> example)
>>>>>>>>
>>>>>>>
>>>>>>> Indeed.
>>>>>>>
>>>>>>>
>>>>>>>> 3. The test that should be passed to consider a parcel ok
for a
>>>>>>>> release
>>>>>>>>
>>>>>>>
>>>>>>> Ha! good idea. Don't know if this can be automated, but deploying
>>>>>>> the parcel, doing rolling upgrades, minor versions and major
versions
>>>>>>> upgrades tests, etc. We might be able to come with a list of
things to
>>>>>>> test, and increase/improve the list as we move forward...
>>>>>>>
>>>>>>>
>>>>>>>> 4. Which documentation to write
>>>>>>>>
>>>>>>>
>>>>>>> Most probably documenting what has changed between the Apache
core
>>>>>>> branch and the updated parce branch? And how to build?
>>>>>>>
>>>>>>>
>>>>>>>> 5. Who is responsible to update Phoenix site and announcements
etc?
>>>>>>>>
>>>>>>>
>>>>>>> You? ;)
>>>>>>>
>>>>>>>
>>>>>>>> 6. Call for contributors when a new release is needed and
>>>>>>>> coordinate them
>>>>>>>>
>>>>>>>
>>>>>>> I'm already in! I have one CDH cluster and almost all CDH versions
>>>>>>> VMs... So I can do a lot of tests, as long as it doesn't required
a month
>>>>>>> of my time every month ;)
>>>>>>>
>>>>>>> JMS
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Kind of those things :)
>>>>>>>>
>>>>>>>> On Fri, Oct 27, 2017 at 2:33 PM, Jean-Marc Spaggiari <
>>>>>>>> jean-marc@spaggiari.org> wrote:
>>>>>>>>
>>>>>>>>> FYI, you can also count on me for that. At least to perform
some
>>>>>>>>> testing or gather information, communication, etc.
>>>>>>>>>
>>>>>>>>> Flavio, what can you leading do you need there?
>>>>>>>>>
>>>>>>>>> James, I am also interested ;) So count me in... (My
very personal
>>>>>>>>> contribution)
>>>>>>>>>
>>>>>>>>> To setup a repo we just need to have a folder on the
existing file
>>>>>>>>> storage with the correct parcel structure so people can
point to it. That's
>>>>>>>>> not a big deal...
>>>>>>>>>
>>>>>>>>> JMS
>>>>>>>>>
>>>>>>>>> 2017-10-27 5:08 GMT-04:00 Flavio Pompermaier <pompermaier@okkam.it
>>>>>>>>> >:
>>>>>>>>>
>>>>>>>>>> I can give it a try..is there someone who can lead
this thing?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>
>>>

Mime
View raw message