You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by Nate McCall <na...@thelastpickle.com> on 2013/11/26 17:47:23 UTC

Moving over to ASF Jira

So I just closed out the first issue on ASF's Jira instance (basically
tracking INFRA-7018).

There are three others up their currently for misc. process stuff we've
known was coming:
https://issues.apache.org/jira/browse/USERGRID

Basically, I feel like I'm in limbo here, because I know there is a pile of
stuff on the internal Apigee Jira and I don't want to butt heads with what
other folks are about to do in sprints and such, particularly if some
issues are about to be imported from such.

Therefore, I'd like to ask the apigee folks about the plan for
transitioning over to ASF repo work and process wise (I know we have that
other thread going, but this is more a general question on the timeline and
resource allocation).

Re: Moving over to ASF Jira

Posted by Alex Karasulu <ak...@apache.org>.
On Fri, Nov 29, 2013 at 5:56 PM, Dave <sn...@gmail.com> wrote:

> +1 to Tim's statements from me too.
>
>
I was under the impression that there might be a need for separate releases
schedules and versions etc. I'm happy to be wrong about that. With one JIRA
the administration goes down. If this criteria does not exist +1 from me as
well.


> Just because some downstream users (e.g. Apigee)  of Apache Usergrid and
> the SDKs might want to make frequent bug fix releases to get timely bug
> fixes and improvements out to their customers does not mean that the Apache
> Usergrid project has to do the same thing, at the same pace and same
> granularity of releases.
>
>
This is not a downstream user concern. I was presuming this would be
naturally desired by the community.


> On Fri, Nov 29, 2013 at 1:14 AM, Jake Farrell <jf...@apache.org> wrote:
>
> > +1, completely agree with Tim's statements
> >
> > -Jake
> >
> >
> > On Thu, Nov 28, 2013 at 11:17 PM, Tim Anglade <ti...@apache.org>
> > wrote:
> >
> > > I'm not sure why releasing the SDKs + stack + portal together is a
> > concern?
> > > After all, the code bases are now merged, and there's some (or a lot
> > > of) co-dependencies on bugs and new features. Plus, in the grand scheme
> > of
> > > things, I'm not sure it'd be convenient for users and committers to
> deal
> > > with separate versions and release notes for stack/portal/sdk. Finally,
> > why
> > > would we want to de-correlate stack from portal but tie ruby sdk
> releases
> > > to php sdk releases? Having too many projects releases confuses
> > everything
> > > in my opinion.
> > >
> > > Can someone expand on the thinking behind wanting separate releases?
> > >
> > > On Thursday, November 28, 2013, Alex Karasulu wrote:
> > >
> > > > On Thu, Nov 28, 2013 at 7:50 PM, Todd Nine <tnine@apigee.com
> > > <javascript:;>>
> > > > wrote:
> > > >
> > > > > Could we do multiple releases in JIRA?  I.E. One format for stack,
> > > > another
> > > > > for SDKs an UI?  Then we simply need to be good Jira users and make
> > > sure
> > > > we
> > > > > put the issue on the correct release when we resolve it?
> > > > >
> > > > >
> > > > I don't know was hoping Nate, you or someone would know.
> > > >
> > > > Alex
> > > >
> > > >
> > > > > On Thursday, November 28, 2013, Alex Karasulu wrote:
> > > > >
> > > > > > Hi Nate,
> > > > > >
> > > > > > On Wed, Nov 27, 2013 at 5:21 PM, Nate McCall <
> > nate@thelastpickle.com
> > > <javascript:;>
> > > > > <javascript:;>>
> > > > > > wrote:
> > > > > >
> > > > > > > We should keep everything under the USERGRID project or else it
> > > will
> > > > > > > confuse the heck out of our community - can't think of any
> other
> > > ASF
> > > > > > > project that does that besides hadoop. And we know how that
> > worked
> > > > out
> > > > > > for
> > > > > > > them :)
> > > > > > >
> > > > > > >
> > > > > > This would certainly be best (simplest = best) but we ran into a
> > > little
> > > > > > problem while discussing this. Let me explain here maybe you'll
> > have
> > > a
> > > > > work
> > > > > > around for us. If we use JIRA to manage releases, then the
> release
> > > > > > management feature which also produces the release notes listing
> > the
> > > > > issues
> > > > > > and  bugs that were fixed since the release is tied 1:1 to a JIRA
> > > > > project.
> > > > > > So if we do all these together in a single project everything
> sdk,
> > > > portal
> > > > > > and stack would have to release together.
> > > > > >
> > > > > >
> > > > > > > But seriously, in lots of ASF projects, I've seen those types
> of
> > > > things
> > > > > > are
> > > > > > > done as components. Eg. Cassandra ('cause I'm most immediately
> > > > familiar
> > > > > > > with the layout) has: core, tools, cli, config, etc to
> > > differentiate
> > > > > > > functionality.
> > > > > > >
> > > > > > > In the context of Usergrid, we'll have to do the same sort of
> > > module
> > > > > > layout
> > > > > > > done internally but add stuff like SDK_iOS, SDK_java, etc.
> > > > > > >
> > > > > > >
> > > > > > I'd rather go this way however is there a way we can release
> > > separately
> > > > > > even if all these are components under a single JIRA project?
> > > > > >
> > > > > > --
> > > > > > Best Regards,
> > > > > > -- Alex
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best Regards,
> > > > -- Alex
> > > >
> > >
> >
>



-- 
Best Regards,
-- Alex

Re: Moving over to ASF Jira

Posted by Dave <sn...@gmail.com>.
+1 to Tim's statements from me too.

Just because some downstream users (e.g. Apigee)  of Apache Usergrid and
the SDKs might want to make frequent bug fix releases to get timely bug
fixes and improvements out to their customers does not mean that the Apache
Usergrid project has to do the same thing, at the same pace and same
granularity of releases.

If such downstream users want to release fixes to a Usergrid based site or
customized SDKs, then they can use their own bug tracking system to manage
the development, plan sprints, assign fixes to releases, etc. Those users
can use as many JIRA (or whatever) projects as they want for their internal
planning, and they can link their internal issues to those in the ASF JIRA
instance if they find that to be helpful.

- Dave


On Fri, Nov 29, 2013 at 1:14 AM, Jake Farrell <jf...@apache.org> wrote:

> +1, completely agree with Tim's statements
>
> -Jake
>
>
> On Thu, Nov 28, 2013 at 11:17 PM, Tim Anglade <ti...@apache.org>
> wrote:
>
> > I'm not sure why releasing the SDKs + stack + portal together is a
> concern?
> > After all, the code bases are now merged, and there's some (or a lot
> > of) co-dependencies on bugs and new features. Plus, in the grand scheme
> of
> > things, I'm not sure it'd be convenient for users and committers to deal
> > with separate versions and release notes for stack/portal/sdk. Finally,
> why
> > would we want to de-correlate stack from portal but tie ruby sdk releases
> > to php sdk releases? Having too many projects releases confuses
> everything
> > in my opinion.
> >
> > Can someone expand on the thinking behind wanting separate releases?
> >
> > On Thursday, November 28, 2013, Alex Karasulu wrote:
> >
> > > On Thu, Nov 28, 2013 at 7:50 PM, Todd Nine <tnine@apigee.com
> > <javascript:;>>
> > > wrote:
> > >
> > > > Could we do multiple releases in JIRA?  I.E. One format for stack,
> > > another
> > > > for SDKs an UI?  Then we simply need to be good Jira users and make
> > sure
> > > we
> > > > put the issue on the correct release when we resolve it?
> > > >
> > > >
> > > I don't know was hoping Nate, you or someone would know.
> > >
> > > Alex
> > >
> > >
> > > > On Thursday, November 28, 2013, Alex Karasulu wrote:
> > > >
> > > > > Hi Nate,
> > > > >
> > > > > On Wed, Nov 27, 2013 at 5:21 PM, Nate McCall <
> nate@thelastpickle.com
> > <javascript:;>
> > > > <javascript:;>>
> > > > > wrote:
> > > > >
> > > > > > We should keep everything under the USERGRID project or else it
> > will
> > > > > > confuse the heck out of our community - can't think of any other
> > ASF
> > > > > > project that does that besides hadoop. And we know how that
> worked
> > > out
> > > > > for
> > > > > > them :)
> > > > > >
> > > > > >
> > > > > This would certainly be best (simplest = best) but we ran into a
> > little
> > > > > problem while discussing this. Let me explain here maybe you'll
> have
> > a
> > > > work
> > > > > around for us. If we use JIRA to manage releases, then the release
> > > > > management feature which also produces the release notes listing
> the
> > > > issues
> > > > > and  bugs that were fixed since the release is tied 1:1 to a JIRA
> > > > project.
> > > > > So if we do all these together in a single project everything sdk,
> > > portal
> > > > > and stack would have to release together.
> > > > >
> > > > >
> > > > > > But seriously, in lots of ASF projects, I've seen those types of
> > > things
> > > > > are
> > > > > > done as components. Eg. Cassandra ('cause I'm most immediately
> > > familiar
> > > > > > with the layout) has: core, tools, cli, config, etc to
> > differentiate
> > > > > > functionality.
> > > > > >
> > > > > > In the context of Usergrid, we'll have to do the same sort of
> > module
> > > > > layout
> > > > > > done internally but add stuff like SDK_iOS, SDK_java, etc.
> > > > > >
> > > > > >
> > > > > I'd rather go this way however is there a way we can release
> > separately
> > > > > even if all these are components under a single JIRA project?
> > > > >
> > > > > --
> > > > > Best Regards,
> > > > > -- Alex
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Best Regards,
> > > -- Alex
> > >
> >
>

Re: Moving over to ASF Jira

Posted by Jake Farrell <jf...@apache.org>.
+1, completely agree with Tim's statements

-Jake


On Thu, Nov 28, 2013 at 11:17 PM, Tim Anglade <ti...@apache.org> wrote:

> I'm not sure why releasing the SDKs + stack + portal together is a concern?
> After all, the code bases are now merged, and there's some (or a lot
> of) co-dependencies on bugs and new features. Plus, in the grand scheme of
> things, I'm not sure it'd be convenient for users and committers to deal
> with separate versions and release notes for stack/portal/sdk. Finally, why
> would we want to de-correlate stack from portal but tie ruby sdk releases
> to php sdk releases? Having too many projects releases confuses everything
> in my opinion.
>
> Can someone expand on the thinking behind wanting separate releases?
>
> On Thursday, November 28, 2013, Alex Karasulu wrote:
>
> > On Thu, Nov 28, 2013 at 7:50 PM, Todd Nine <tnine@apigee.com
> <javascript:;>>
> > wrote:
> >
> > > Could we do multiple releases in JIRA?  I.E. One format for stack,
> > another
> > > for SDKs an UI?  Then we simply need to be good Jira users and make
> sure
> > we
> > > put the issue on the correct release when we resolve it?
> > >
> > >
> > I don't know was hoping Nate, you or someone would know.
> >
> > Alex
> >
> >
> > > On Thursday, November 28, 2013, Alex Karasulu wrote:
> > >
> > > > Hi Nate,
> > > >
> > > > On Wed, Nov 27, 2013 at 5:21 PM, Nate McCall <nate@thelastpickle.com
> <javascript:;>
> > > <javascript:;>>
> > > > wrote:
> > > >
> > > > > We should keep everything under the USERGRID project or else it
> will
> > > > > confuse the heck out of our community - can't think of any other
> ASF
> > > > > project that does that besides hadoop. And we know how that worked
> > out
> > > > for
> > > > > them :)
> > > > >
> > > > >
> > > > This would certainly be best (simplest = best) but we ran into a
> little
> > > > problem while discussing this. Let me explain here maybe you'll have
> a
> > > work
> > > > around for us. If we use JIRA to manage releases, then the release
> > > > management feature which also produces the release notes listing the
> > > issues
> > > > and  bugs that were fixed since the release is tied 1:1 to a JIRA
> > > project.
> > > > So if we do all these together in a single project everything sdk,
> > portal
> > > > and stack would have to release together.
> > > >
> > > >
> > > > > But seriously, in lots of ASF projects, I've seen those types of
> > things
> > > > are
> > > > > done as components. Eg. Cassandra ('cause I'm most immediately
> > familiar
> > > > > with the layout) has: core, tools, cli, config, etc to
> differentiate
> > > > > functionality.
> > > > >
> > > > > In the context of Usergrid, we'll have to do the same sort of
> module
> > > > layout
> > > > > done internally but add stuff like SDK_iOS, SDK_java, etc.
> > > > >
> > > > >
> > > > I'd rather go this way however is there a way we can release
> separately
> > > > even if all these are components under a single JIRA project?
> > > >
> > > > --
> > > > Best Regards,
> > > > -- Alex
> > > >
> > >
> >
> >
> >
> > --
> > Best Regards,
> > -- Alex
> >
>

Re: Moving over to ASF Jira

Posted by Tim Anglade <ti...@apache.org>.
I'm not sure why releasing the SDKs + stack + portal together is a concern?
After all, the code bases are now merged, and there's some (or a lot
of) co-dependencies on bugs and new features. Plus, in the grand scheme of
things, I'm not sure it'd be convenient for users and committers to deal
with separate versions and release notes for stack/portal/sdk. Finally, why
would we want to de-correlate stack from portal but tie ruby sdk releases
to php sdk releases? Having too many projects releases confuses everything
in my opinion.

Can someone expand on the thinking behind wanting separate releases?

On Thursday, November 28, 2013, Alex Karasulu wrote:

> On Thu, Nov 28, 2013 at 7:50 PM, Todd Nine <tnine@apigee.com<javascript:;>>
> wrote:
>
> > Could we do multiple releases in JIRA?  I.E. One format for stack,
> another
> > for SDKs an UI?  Then we simply need to be good Jira users and make sure
> we
> > put the issue on the correct release when we resolve it?
> >
> >
> I don't know was hoping Nate, you or someone would know.
>
> Alex
>
>
> > On Thursday, November 28, 2013, Alex Karasulu wrote:
> >
> > > Hi Nate,
> > >
> > > On Wed, Nov 27, 2013 at 5:21 PM, Nate McCall <nate@thelastpickle.com<javascript:;>
> > <javascript:;>>
> > > wrote:
> > >
> > > > We should keep everything under the USERGRID project or else it will
> > > > confuse the heck out of our community - can't think of any other ASF
> > > > project that does that besides hadoop. And we know how that worked
> out
> > > for
> > > > them :)
> > > >
> > > >
> > > This would certainly be best (simplest = best) but we ran into a little
> > > problem while discussing this. Let me explain here maybe you'll have a
> > work
> > > around for us. If we use JIRA to manage releases, then the release
> > > management feature which also produces the release notes listing the
> > issues
> > > and  bugs that were fixed since the release is tied 1:1 to a JIRA
> > project.
> > > So if we do all these together in a single project everything sdk,
> portal
> > > and stack would have to release together.
> > >
> > >
> > > > But seriously, in lots of ASF projects, I've seen those types of
> things
> > > are
> > > > done as components. Eg. Cassandra ('cause I'm most immediately
> familiar
> > > > with the layout) has: core, tools, cli, config, etc to differentiate
> > > > functionality.
> > > >
> > > > In the context of Usergrid, we'll have to do the same sort of module
> > > layout
> > > > done internally but add stuff like SDK_iOS, SDK_java, etc.
> > > >
> > > >
> > > I'd rather go this way however is there a way we can release separately
> > > even if all these are components under a single JIRA project?
> > >
> > > --
> > > Best Regards,
> > > -- Alex
> > >
> >
>
>
>
> --
> Best Regards,
> -- Alex
>

Re: Moving over to ASF Jira

Posted by Alex Karasulu <ak...@apache.org>.
On Thu, Nov 28, 2013 at 7:50 PM, Todd Nine <tn...@apigee.com> wrote:

> Could we do multiple releases in JIRA?  I.E. One format for stack, another
> for SDKs an UI?  Then we simply need to be good Jira users and make sure we
> put the issue on the correct release when we resolve it?
>
>
I don't know was hoping Nate, you or someone would know.

Alex


> On Thursday, November 28, 2013, Alex Karasulu wrote:
>
> > Hi Nate,
> >
> > On Wed, Nov 27, 2013 at 5:21 PM, Nate McCall <nate@thelastpickle.com
> <javascript:;>>
> > wrote:
> >
> > > We should keep everything under the USERGRID project or else it will
> > > confuse the heck out of our community - can't think of any other ASF
> > > project that does that besides hadoop. And we know how that worked out
> > for
> > > them :)
> > >
> > >
> > This would certainly be best (simplest = best) but we ran into a little
> > problem while discussing this. Let me explain here maybe you'll have a
> work
> > around for us. If we use JIRA to manage releases, then the release
> > management feature which also produces the release notes listing the
> issues
> > and  bugs that were fixed since the release is tied 1:1 to a JIRA
> project.
> > So if we do all these together in a single project everything sdk, portal
> > and stack would have to release together.
> >
> >
> > > But seriously, in lots of ASF projects, I've seen those types of things
> > are
> > > done as components. Eg. Cassandra ('cause I'm most immediately familiar
> > > with the layout) has: core, tools, cli, config, etc to differentiate
> > > functionality.
> > >
> > > In the context of Usergrid, we'll have to do the same sort of module
> > layout
> > > done internally but add stuff like SDK_iOS, SDK_java, etc.
> > >
> > >
> > I'd rather go this way however is there a way we can release separately
> > even if all these are components under a single JIRA project?
> >
> > --
> > Best Regards,
> > -- Alex
> >
>



-- 
Best Regards,
-- Alex

Re: Moving over to ASF Jira

Posted by Todd Nine <tn...@apigee.com>.
Could we do multiple releases in JIRA?  I.E. One format for stack, another
for SDKs an UI?  Then we simply need to be good Jira users and make sure we
put the issue on the correct release when we resolve it?

On Thursday, November 28, 2013, Alex Karasulu wrote:

> Hi Nate,
>
> On Wed, Nov 27, 2013 at 5:21 PM, Nate McCall <nate@thelastpickle.com<javascript:;>>
> wrote:
>
> > We should keep everything under the USERGRID project or else it will
> > confuse the heck out of our community - can't think of any other ASF
> > project that does that besides hadoop. And we know how that worked out
> for
> > them :)
> >
> >
> This would certainly be best (simplest = best) but we ran into a little
> problem while discussing this. Let me explain here maybe you'll have a work
> around for us. If we use JIRA to manage releases, then the release
> management feature which also produces the release notes listing the issues
> and  bugs that were fixed since the release is tied 1:1 to a JIRA project.
> So if we do all these together in a single project everything sdk, portal
> and stack would have to release together.
>
>
> > But seriously, in lots of ASF projects, I've seen those types of things
> are
> > done as components. Eg. Cassandra ('cause I'm most immediately familiar
> > with the layout) has: core, tools, cli, config, etc to differentiate
> > functionality.
> >
> > In the context of Usergrid, we'll have to do the same sort of module
> layout
> > done internally but add stuff like SDK_iOS, SDK_java, etc.
> >
> >
> I'd rather go this way however is there a way we can release separately
> even if all these are components under a single JIRA project?
>
> --
> Best Regards,
> -- Alex
>

Re: Moving over to ASF Jira

Posted by Alex Karasulu <ak...@apache.org>.
Hi Nate,

On Wed, Nov 27, 2013 at 5:21 PM, Nate McCall <na...@thelastpickle.com> wrote:

> We should keep everything under the USERGRID project or else it will
> confuse the heck out of our community - can't think of any other ASF
> project that does that besides hadoop. And we know how that worked out for
> them :)
>
>
This would certainly be best (simplest = best) but we ran into a little
problem while discussing this. Let me explain here maybe you'll have a work
around for us. If we use JIRA to manage releases, then the release
management feature which also produces the release notes listing the issues
and  bugs that were fixed since the release is tied 1:1 to a JIRA project.
So if we do all these together in a single project everything sdk, portal
and stack would have to release together.


> But seriously, in lots of ASF projects, I've seen those types of things are
> done as components. Eg. Cassandra ('cause I'm most immediately familiar
> with the layout) has: core, tools, cli, config, etc to differentiate
> functionality.
>
> In the context of Usergrid, we'll have to do the same sort of module layout
> done internally but add stuff like SDK_iOS, SDK_java, etc.
>
>
I'd rather go this way however is there a way we can release separately
even if all these are components under a single JIRA project?

-- 
Best Regards,
-- Alex

Re: Moving over to ASF Jira

Posted by Nate McCall <na...@thelastpickle.com>.
We should keep everything under the USERGRID project or else it will
confuse the heck out of our community - can't think of any other ASF
project that does that besides hadoop. And we know how that worked out for
them :)

But seriously, in lots of ASF projects, I've seen those types of things are
done as components. Eg. Cassandra ('cause I'm most immediately familiar
with the layout) has: core, tools, cli, config, etc to differentiate
functionality.

In the context of Usergrid, we'll have to do the same sort of module layout
done internally but add stuff like SDK_iOS, SDK_java, etc.

Thoughts?


On Tue, Nov 26, 2013 at 2:34 PM, Rod Simpson <ro...@rodsimpson.com> wrote:

> Nate,
>
> We are in the process of pruning / cleaning up the tickets to put into the
> ASF’s Jira.  At this point, we are thinking of using 3 different projects -
> UG_Stack, UG_UI, and UG_SDKs, although we could also get by with just two:
> UG_Stack and UG_UI_SDKs.
>
> Thoughts on that would be appreciated ^
>
> Basically we(I) have to go through all the tickets and sanitize (pull out
> customer-specific items) and then push them over.  I created another Jira
> project internally and am pushing all tickets there.  Once done, I will
> export the lot and import to Apache Jira.
>
> Rod
>
>
>
>
> On November 26, 2013 at 9:47:56 AM, Nate McCall (nate@thelastpickle.com)
> wrote:
>
> So I just closed out the first issue on ASF's Jira instance (basically
> tracking INFRA-7018).
>
> There are three others up their currently for misc. process stuff we've
> known was coming:
> https://issues.apache.org/jira/browse/USERGRID
>
> Basically, I feel like I'm in limbo here, because I know there is a pile of
> stuff on the internal Apigee Jira and I don't want to butt heads with what
> other folks are about to do in sprints and such, particularly if some
> issues are about to be imported from such.
>
> Therefore, I'd like to ask the apigee folks about the plan for
> transitioning over to ASF repo work and process wise (I know we have that
> other thread going, but this is more a general question on the timeline and
> resource allocation).
>



-- 
-----------------
Nate McCall
Austin, TX
@zznate

Co-Founder & Sr. Technical Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: Moving over to ASF Jira

Posted by Rod Simpson <ro...@rodsimpson.com>.
Nate,

We are in the process of pruning / cleaning up the tickets to put into the ASF’s Jira.  At this point, we are thinking of using 3 different projects - UG_Stack, UG_UI, and UG_SDKs, although we could also get by with just two: UG_Stack and UG_UI_SDKs.   

Thoughts on that would be appreciated ^

Basically we(I) have to go through all the tickets and sanitize (pull out customer-specific items) and then push them over.  I created another Jira project internally and am pushing all tickets there.  Once done, I will export the lot and import to Apache Jira.

Rod




On November 26, 2013 at 9:47:56 AM, Nate McCall (nate@thelastpickle.com) wrote:

So I just closed out the first issue on ASF's Jira instance (basically  
tracking INFRA-7018).  

There are three others up their currently for misc. process stuff we've  
known was coming:  
https://issues.apache.org/jira/browse/USERGRID  

Basically, I feel like I'm in limbo here, because I know there is a pile of  
stuff on the internal Apigee Jira and I don't want to butt heads with what  
other folks are about to do in sprints and such, particularly if some  
issues are about to be imported from such.  

Therefore, I'd like to ask the apigee folks about the plan for  
transitioning over to ASF repo work and process wise (I know we have that  
other thread going, but this is more a general question on the timeline and  
resource allocation).