You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pirk.apache.org by Ellison Anne Williams <ea...@gmail.com> on 2016/08/12 16:05:22 UTC
Release Preparations
I'm about to tag all of our completed/closed JIRA issues to-date with Fix
Version = 0.1.0 in preparation for cutting our release branch later today.
If you don't agree - please holler quickly!
Otherwise, I will tag the issues, cut the branch (following a lot of
guidelines that I will send out in a resulting email), and then send a vote
email with lots of commentary (and an ask for the mentors to course correct
as necessary). This will be completed later today.
On a side note - we need to decide on our release versioning so that we can
tag JIRAs appropriately as we go (and so no one has to back-tag).
Re: Release Preparations
Posted by Ellison Anne Williams <ea...@gmail.com>.
Agreed.
On Fri, Aug 12, 2016 at 5:59 PM, Suneel Marthi <sm...@apache.org> wrote:
> I may not be able to get to it today and I think we should go ahead with
> the release.
> This is not core Pirk functionality per se, its safe to close the PR and
> create a Jira to track this for the next release.
>
>
>
> On Fri, Aug 12, 2016 at 5:53 PM, Tim Ellison <t....@gmail.com>
> wrote:
>
> > Keep working it. We could delay the release, but IMO releases should be
> > frequent enough that missing one is not a big deal, and there is no point
> > in delivering function that is not ready yet.
> >
> > Regards,
> > Tim
> >
> > On 12 August 2016 at 22:31, Suneel Marthi <sm...@apache.org> wrote:
> >
> > > I have a PR for the Coveralls code coverage stuff that's open. The PR
> > > doesn't fix the problem and doesn't break anything if it were merged.
> > >
> > > Please go ahead and merge the PR and prepare for the release.
> > >
> > > On Fri, Aug 12, 2016 at 12:08 PM, Ellison Anne Williams <
> > > eawilliamspirk@gmail.com> wrote:
> > >
> > > > No problem - I will most likely cut the branch late afternoon - let's
> > > say,
> > > > after 3 PM EST.
> > > >
> > > > On Fri, Aug 12, 2016 at 12:07 PM, Suneel Marthi <
> > suneel.marthi@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > I am pushing in one last change in next 20 mins, this is to enable
> > the
> > > > code
> > > > > coverage badge on github.
> > > > >
> > > > > On Fri, Aug 12, 2016 at 12:05 PM, Ellison Anne Williams <
> > > > > eawilliamspirk@gmail.com> wrote:
> > > > >
> > > > > > I'm about to tag all of our completed/closed JIRA issues to-date
> > with
> > > > Fix
> > > > > > Version = 0.1.0 in preparation for cutting our release branch
> later
> > > > > today.
> > > > > > If you don't agree - please holler quickly!
> > > > > >
> > > > > > Otherwise, I will tag the issues, cut the branch (following a lot
> > of
> > > > > > guidelines that I will send out in a resulting email), and then
> > send
> > > a
> > > > > vote
> > > > > > email with lots of commentary (and an ask for the mentors to
> course
> > > > > correct
> > > > > > as necessary). This will be completed later today.
> > > > > >
> > > > > > On a side note - we need to decide on our release versioning so
> > that
> > > we
> > > > > can
> > > > > > tag JIRAs appropriately as we go (and so no one has to back-tag).
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Release Preparations
Posted by Suneel Marthi <sm...@apache.org>.
I may not be able to get to it today and I think we should go ahead with
the release.
This is not core Pirk functionality per se, its safe to close the PR and
create a Jira to track this for the next release.
On Fri, Aug 12, 2016 at 5:53 PM, Tim Ellison <t....@gmail.com> wrote:
> Keep working it. We could delay the release, but IMO releases should be
> frequent enough that missing one is not a big deal, and there is no point
> in delivering function that is not ready yet.
>
> Regards,
> Tim
>
> On 12 August 2016 at 22:31, Suneel Marthi <sm...@apache.org> wrote:
>
> > I have a PR for the Coveralls code coverage stuff that's open. The PR
> > doesn't fix the problem and doesn't break anything if it were merged.
> >
> > Please go ahead and merge the PR and prepare for the release.
> >
> > On Fri, Aug 12, 2016 at 12:08 PM, Ellison Anne Williams <
> > eawilliamspirk@gmail.com> wrote:
> >
> > > No problem - I will most likely cut the branch late afternoon - let's
> > say,
> > > after 3 PM EST.
> > >
> > > On Fri, Aug 12, 2016 at 12:07 PM, Suneel Marthi <
> suneel.marthi@gmail.com
> > >
> > > wrote:
> > >
> > > > I am pushing in one last change in next 20 mins, this is to enable
> the
> > > code
> > > > coverage badge on github.
> > > >
> > > > On Fri, Aug 12, 2016 at 12:05 PM, Ellison Anne Williams <
> > > > eawilliamspirk@gmail.com> wrote:
> > > >
> > > > > I'm about to tag all of our completed/closed JIRA issues to-date
> with
> > > Fix
> > > > > Version = 0.1.0 in preparation for cutting our release branch later
> > > > today.
> > > > > If you don't agree - please holler quickly!
> > > > >
> > > > > Otherwise, I will tag the issues, cut the branch (following a lot
> of
> > > > > guidelines that I will send out in a resulting email), and then
> send
> > a
> > > > vote
> > > > > email with lots of commentary (and an ask for the mentors to course
> > > > correct
> > > > > as necessary). This will be completed later today.
> > > > >
> > > > > On a side note - we need to decide on our release versioning so
> that
> > we
> > > > can
> > > > > tag JIRAs appropriately as we go (and so no one has to back-tag).
> > > > >
> > > >
> > >
> >
>
Re: Release Preparations
Posted by Tim Ellison <t....@gmail.com>.
Keep working it. We could delay the release, but IMO releases should be
frequent enough that missing one is not a big deal, and there is no point
in delivering function that is not ready yet.
Regards,
Tim
On 12 August 2016 at 22:31, Suneel Marthi <sm...@apache.org> wrote:
> I have a PR for the Coveralls code coverage stuff that's open. The PR
> doesn't fix the problem and doesn't break anything if it were merged.
>
> Please go ahead and merge the PR and prepare for the release.
>
> On Fri, Aug 12, 2016 at 12:08 PM, Ellison Anne Williams <
> eawilliamspirk@gmail.com> wrote:
>
> > No problem - I will most likely cut the branch late afternoon - let's
> say,
> > after 3 PM EST.
> >
> > On Fri, Aug 12, 2016 at 12:07 PM, Suneel Marthi <suneel.marthi@gmail.com
> >
> > wrote:
> >
> > > I am pushing in one last change in next 20 mins, this is to enable the
> > code
> > > coverage badge on github.
> > >
> > > On Fri, Aug 12, 2016 at 12:05 PM, Ellison Anne Williams <
> > > eawilliamspirk@gmail.com> wrote:
> > >
> > > > I'm about to tag all of our completed/closed JIRA issues to-date with
> > Fix
> > > > Version = 0.1.0 in preparation for cutting our release branch later
> > > today.
> > > > If you don't agree - please holler quickly!
> > > >
> > > > Otherwise, I will tag the issues, cut the branch (following a lot of
> > > > guidelines that I will send out in a resulting email), and then send
> a
> > > vote
> > > > email with lots of commentary (and an ask for the mentors to course
> > > correct
> > > > as necessary). This will be completed later today.
> > > >
> > > > On a side note - we need to decide on our release versioning so that
> we
> > > can
> > > > tag JIRAs appropriately as we go (and so no one has to back-tag).
> > > >
> > >
> >
>
Re: Release Preparations
Posted by Suneel Marthi <sm...@apache.org>.
I have a PR for the Coveralls code coverage stuff that's open. The PR
doesn't fix the problem and doesn't break anything if it were merged.
Please go ahead and merge the PR and prepare for the release.
On Fri, Aug 12, 2016 at 12:08 PM, Ellison Anne Williams <
eawilliamspirk@gmail.com> wrote:
> No problem - I will most likely cut the branch late afternoon - let's say,
> after 3 PM EST.
>
> On Fri, Aug 12, 2016 at 12:07 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> > I am pushing in one last change in next 20 mins, this is to enable the
> code
> > coverage badge on github.
> >
> > On Fri, Aug 12, 2016 at 12:05 PM, Ellison Anne Williams <
> > eawilliamspirk@gmail.com> wrote:
> >
> > > I'm about to tag all of our completed/closed JIRA issues to-date with
> Fix
> > > Version = 0.1.0 in preparation for cutting our release branch later
> > today.
> > > If you don't agree - please holler quickly!
> > >
> > > Otherwise, I will tag the issues, cut the branch (following a lot of
> > > guidelines that I will send out in a resulting email), and then send a
> > vote
> > > email with lots of commentary (and an ask for the mentors to course
> > correct
> > > as necessary). This will be completed later today.
> > >
> > > On a side note - we need to decide on our release versioning so that we
> > can
> > > tag JIRAs appropriately as we go (and so no one has to back-tag).
> > >
> >
>
Re: Release Preparations
Posted by Ellison Anne Williams <ea...@gmail.com>.
No problem - I will most likely cut the branch late afternoon - let's say,
after 3 PM EST.
On Fri, Aug 12, 2016 at 12:07 PM, Suneel Marthi <su...@gmail.com>
wrote:
> I am pushing in one last change in next 20 mins, this is to enable the code
> coverage badge on github.
>
> On Fri, Aug 12, 2016 at 12:05 PM, Ellison Anne Williams <
> eawilliamspirk@gmail.com> wrote:
>
> > I'm about to tag all of our completed/closed JIRA issues to-date with Fix
> > Version = 0.1.0 in preparation for cutting our release branch later
> today.
> > If you don't agree - please holler quickly!
> >
> > Otherwise, I will tag the issues, cut the branch (following a lot of
> > guidelines that I will send out in a resulting email), and then send a
> vote
> > email with lots of commentary (and an ask for the mentors to course
> correct
> > as necessary). This will be completed later today.
> >
> > On a side note - we need to decide on our release versioning so that we
> can
> > tag JIRAs appropriately as we go (and so no one has to back-tag).
> >
>
Re: Release Preparations
Posted by Suneel Marthi <su...@gmail.com>.
I am pushing in one last change in next 20 mins, this is to enable the code
coverage badge on github.
On Fri, Aug 12, 2016 at 12:05 PM, Ellison Anne Williams <
eawilliamspirk@gmail.com> wrote:
> I'm about to tag all of our completed/closed JIRA issues to-date with Fix
> Version = 0.1.0 in preparation for cutting our release branch later today.
> If you don't agree - please holler quickly!
>
> Otherwise, I will tag the issues, cut the branch (following a lot of
> guidelines that I will send out in a resulting email), and then send a vote
> email with lots of commentary (and an ask for the mentors to course correct
> as necessary). This will be completed later today.
>
> On a side note - we need to decide on our release versioning so that we can
> tag JIRAs appropriately as we go (and so no one has to back-tag).
>