Re: Next Release

[Darin Johnson]

I think it's very possible I can have things done by the end of next week.
There may be some minor issues that may move part of it into next week.

I'm +1 (non binding) for 0.2.0.

Darin

On Sep 24, 2016 2:58 PM, "Ellison Anne Williams" 
wrote:

> Hi Guys,
>
> In the spirit of release often (~1x per month), I would like to execute
> another release in about a week (next Friday/Saturday). Any objections?
>
> If not, would you prefer that this release be 0.1.1 or 0.2.0?
>
> Darin - If the initial submodule refactor is completed by then, it would be
> a great addition to the release. If not, we will plan to roll it into the
> October release.
>
> Thanks!
>
> Ellison Anne
>

Re: Next Release

[Suneel Marthi]

I am cool with someone else playing the RM role, lets plan for a release
early next week in time for October incubator report.

On Sat, Sep 24, 2016 at 8:19 PM, Walter Ray-Dulany 
wrote:

> No objections, and I would defer to the community on numbering (which right
> now means I defer to Tim ;) ).
>
> On Sat, Sep 24, 2016 at 8:03 PM, Ellison Anne Williams <
> eawilli...@apache.org> wrote:
>
> > Happy to be the RM again or give another committer the 'privilege' -- if
> I
> > don't hear otherwise, I will take it this month and someone else can
> assume
> > the duties in October.
> >
> > On Sat, Sep 24, 2016 at 5:18 PM, Tim Ellison 
> > wrote:
> >
> > > On 24 September 2016 at 19:58, Ellison Anne Williams <
> > > eawilli...@apache.org>
> > > wrote:
> > >
> > > > Hi Guys,
> > > >
> > > > In the spirit of release often (~1x per month), I would like to
> execute
> > > > another release in about a week (next Friday/Saturday). Any
> objections?
> > > >
> > > > If not, would you prefer that this release be 0.1.1 or 0.2.0?
> > > >
> > > > Darin - If the initial submodule refactor is completed by then, it
> > would
> > > be
> > > > a great addition to the release. If not, we will plan to roll it into
> > the
> > > > October release.
> > > >
> > >
> > > Sounds good to me.
> > >
> > > I don't have a strong feeling about the name, until we get to the 1.0.0
> > > release when we should adopt a major.minor.patch semantic version
> naming
> > > scheme.  FWIW I'd probably pick 0.2.0.
> > >
> > > Are you volunteering to be RM again?  We should rotate the 'privilege',
> > but
> > > there will be opportunities to do that with frequent releases.
> > >
> > > Regards,
> > > Tim
> > >
> >
>

[GitHub] incubator-pirk issue #101: [PIRK-68] - Add the Capability for Generic Fields...

[wraydulany]

Github user wraydulany commented on the issue:

https://github.com/apache/incubator-pirk/pull/101
  
+1 lgtm


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Next Release

[Ellison Anne Williams]

Happy to be the RM again or give another committer the 'privilege' -- if I
don't hear otherwise, I will take it this month and someone else can assume
the duties in October.

On Sat, Sep 24, 2016 at 5:18 PM, Tim Ellison  wrote:

> On 24 September 2016 at 19:58, Ellison Anne Williams <
> eawilli...@apache.org>
> wrote:
>
> > Hi Guys,
> >
> > In the spirit of release often (~1x per month), I would like to execute
> > another release in about a week (next Friday/Saturday). Any objections?
> >
> > If not, would you prefer that this release be 0.1.1 or 0.2.0?
> >
> > Darin - If the initial submodule refactor is completed by then, it would
> be
> > a great addition to the release. If not, we will plan to roll it into the
> > October release.
> >
>
> Sounds good to me.
>
> I don't have a strong feeling about the name, until we get to the 1.0.0
> release when we should adopt a major.minor.patch semantic version naming
> scheme.  FWIW I'd probably pick 0.2.0.
>
> Are you volunteering to be RM again?  We should rotate the 'privilege', but
> there will be opportunities to do that with frequent releases.
>
> Regards,
> Tim
>