spot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Austin Leahy <Aus...@digitalminion.com>
Subject Re: [DISCUSS] Publishing Open Data Model Scripts to Github - EPIC Creation in Jira
Date Fri, 28 Apr 2017 22:16:52 GMT
Yep nothing stopping that... just clearing up that the epic field in
tickets is misleading and not useable
On Fri, Apr 28, 2017 at 3:06 PM Michael Ridley <mridley@cloudera.com> wrote:

> Could we just make a regular task as the umbrella jira and then have the
> specific tasks as subtasks?  That's what I do with some non-ASF JIRA stuff
> and it works for the purposes I use it for.
>
> Michael
>
> On Fri, Apr 28, 2017 at 6:04 PM, Austin Leahy <Austin@digitalminion.com>
> wrote:
>
> > I actually just sent in a question about Epic creation and was told epics
> > are not the canonical asf way to approach enhancements because Jira makes
> > epics available across projects. e.g. HDFS would be able to assign
> tickets
> > in their project to Spot epics. The recommendation is to tie tasks to
> > generalized enhancement statements or feature tickets.
> >
> > On Fri, Apr 28, 2017 at 3:00 PM Mark Grover <grover.markgrover@gmail.com
> >
> > wrote:
> >
> > > Removing private@
> > >
> > > On Fri, Apr 28, 2017 at 2:27 PM, Michael Ridley <mridley@cloudera.com>
> > > wrote:
> > >
> > > > Seems like an Epic would be a reasonable way to track a workstream of
> > > this
> > > > magnitude.
> > > >
> > > > What is the best way in ASF land to track work in progress design
> > > > documents/concepts?  Attach docs to a JIRA and comment in the JIRA?
> > Not
> > > > really sure.
> > > >
> > > Yeah, attaching docs (with versions _v1, etc.) is what's usually done.
> > >
> > >
> > > >
> > > > Michael
> > > >
> > > > On Thu, Apr 27, 2017 at 11:11 AM, Raymundo Panduro <
> > raypanduro@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > I don't see any Epic in Jira about ODM as itself, just a lot of
> tasks
> > > > > regarding ODM. I think will be good to review and create an EPIC
as
> > > "New
> > > > > Feature" or "Improvement" to link all the tasks to that epic in
> Jira
> > > with
> > > > > the help of @Morris and the rest of the team to be able to start
> this
> > > > > integration following the process.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > *Raymundo Panduro*
> > > > >
> > > > >
> > > > > On Wed, Apr 26, 2017 at 10:59 AM, Nathanael Smith <
> > > nathanael@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Should we create a branch for ODM development?
> > > > > > I feel that there are several steps that need to happen before
> it’s
> > > in
> > > > > the
> > > > > > master.
> > > > > >
> > > > > > 1. contribution of database creation scripts
> > > > > > 2. possible component (ingest, ml and oa) changes/additions
for
> > said
> > > > > > databases
> > > > > > 3. documentation changes
> > > > > >
> > > > > > any thoughts?
> > > > > >
> > > > > > - Nathanael
> > > > > >
> > > > > >
> > > > > >
> > > > > > > On Apr 26, 2017, at 8:50 AM, Cesar B <cesar@apache.org>
wrote:
> > > > > > >
> > > > > > > Hello @Morris and @Jon
> > > > > > >
> > > > > > > Please refer to the process below:
> > > > > > >
> > > > > > > http://spot.apache.org/community/contribute/
> > > > > > >
> > > > > > > Getting this into the project repo will be awesome, Community
> in
> > > > > general
> > > > > > has been looking to play with ODM for a while.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Cesar
> > > > > > >
> > > > > > >
> > > > > > > On April 26, 2017 at 8:07:10 AM, Zeolla@GMail.com (
> > > zeolla@gmail.com)
> > > > > > wrote:
> > > > > > >
> > > > > > > I totally agree - I would love something to align my data
> > against,
> > > > and
> > > > > > have
> > > > > > > been waiting on a (documented) standard to emerge.
> > > > > > >
> > > > > > > Jon
> > > > > > >
> > > > > > > On Wed, Apr 26, 2017 at 8:16 AM Morris Hicks <
> > mhicks@cloudera.com>
> > > > > > wrote:
> > > > > > >
> > > > > > >> Scripts have been created for automating the creation
of the
> > open
> > > > data
> > > > > > >> model and enabling fast data ingest & query as
outlined in
> this
> > > > > cloudera
> > > > > > >> blog.
> > > > > > >> <
> > > > > > >> https://blog.cloudera.com/blog/2015/11/how-to-ingest-and-
> > > > > > query-fast-data-with-impala-without-kudu/
> > > > > > >>>
> > > > > > >> It could be beneficial to publish this content to the
project
> > > GitHub
> > > > > to
> > > > > > >> allow org's to start using the open data model. What's
the
> > > > recommended
> > > > > > >> mechanism to serve this content (create a new branch,
create a
> > > > > > >> subdirectory in existing branch, etc.)?
> > > > > > >>
> > > > > > >> Thanks,
> > > > > > >>
> > > > > > >> --
> > > > > > >> Morris Hicks
> > > > > > >> Strategic Enablement Expert, Cloudera
> > > > > > >> mhicks@cloudera.com
> > > > > > >> (703) 447-5883
> > > > > > >>
> > > > > > > --
> > > > > > >
> > > > > > > Jon
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Michael Ridley <mridley@cloudera.com>
> > > > office: (650) 352-1337
> > > > mobile: (571) 438-2420
> > > > Senior Solutions Architect
> > > > Cloudera, Inc.
> > > >
> > >
> >
>
>
>
> --
> Michael Ridley <mridley@cloudera.com>
> office: (650) 352-1337
> mobile: (571) 438-2420
> Senior Solutions Architect
> Cloudera, Inc.
>

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