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/06 14:47:00 UTC
Mentors - Release Process?
Hi Mentors,
Can you please give an overview (or point to a good overview) of what the
process is / what we need to do in order to execute our first release?
There is some information on the Accumulo and NiFi websites - happy to
synthesize those resources into a list for us and email for
comment/correction, but wanted to check first.
Thanks!
Ellison Anne
Re: Mentors - Release Process?
Posted by Ellison Anne Williams <ea...@gmail.com>.
As per the comments, I will plan to create a release branch on Friday --
whichever JIRAs/PRs are completed by that point will be included. That way,
we can start voting on Friday evening/Saturday.
Any concerns, please let me know. Thanks!
On Tue, Aug 9, 2016 at 10:16 AM, Tim Ellison <t....@gmail.com> wrote:
> On 06/08/16 21:06, Ellison Anne Williams wrote:
> > It appears that we reached consensus regarding proceeding with a
> release. I
> > would like to get our first release out over the next couple of weeks.
>
> Yep, it will be a good practice to release early and often. I don't see
> any fundamental release blockers in the code (the original contribution
> was very "clean"), so it will be an opportunity to exercise the release
> process itself.
>
> > Many of our committers are out on vacation/at conferences next week. We
> can
> > go ahead and prepare everything for release and vote accordingly,
> realizing
> > that we may need to wait until folks return to complete the vote.
> According
> > to the documentation below, we need three +1 votes from PPMC members for
> > the release in order to elevate it to the IPMC for voting.
>
> Yep.
>
> > First, we need to decide which open JIRA issues we would like to have
> > resolved (if any) before making the release. I propose that we complete
> > PIRK-29 (user notification of decrypting with wrong Querier) and PIRK-13
> > (integrate jackson); we may want to also take a step towards addressing
> > PIRK-14 (user examples). Thoughts?
>
> Again, I don't see any blockers yet. It may be good to get into the
> habit of assigning the "Fix version" fields of the JIRAs you want to see
> in the release.
>
> The very first release may well have limited adoption, understandably,
> but quite soon it will be good to get some enhanced user documentation
> and examples in place to make it easier for people to pick-up.
>
> > Once we decide on which JIRAs need to be resolved and resolve them, I
> will
> > create a candidate release branch for voting purposes. (Mentors - please
> > let me know if I'm doing the wrong thing or the right thing in the wrong
> > order here)
> >
> > For ease of reference, here is the official release information that I
> was
> > able to find (we can move this to the Pirk website too):
> >
> > - Apache Release Guide: http://www.apache.org/dev/release-publishing
> > - Apache Release Policy: http://www.apache.org/dev/release.html
> > - Apache Incubator Release Guidelines:
> > http://incubator.apache.org/guides/releasemanagement.html
> > - Apache Incubator Release Policy:
> > http://incubator.apache.org/incubation/Incubation_Policy.
> html#Releases
> > - For Maven Release:
> > http://www.apache.org/dev/publishing-maven-artifacts.html
> >
> > I propose that we follow the Incubator Release Guidelines with some help
> > from the Accumulo (https://accumulo.apache.org/releasing) and NiFi (
> > https://nifi.apache.org/release-guide.html) release guides. Between
> these
> > webpages, there's lots of great information.
>
> I agree, those projects have a good step-by-step guide to creating a
> release. Having a robust and repeatable process ensures we can have a
> variety of release managers as the project progresses, which is a good
> sign of a healthy project.
>
> Regards,
> Tim
>
> > A few questions:
> >
> > - We need to publish our release to
> > http://www.apache.org/dist/incubator/pirk -- however, we do not yet
> have
> > a Pirk folder. Do we need to request the 'pirk' folder from INFRA or
> can we
> > just create it?
> > - We have not received our official sign off from the trademark folks
> > for the Pirk name - is this necessary before making our first release?
> >
> > One general TODO:
> >
> > - In order to publish our release artifact to Maven, we need to have
> > Pirk setup in the Nexus Repository - a ticket to INFRA is required --
> > http://www.apache.org/dev/publishing-maven-artifacts.html#signing-up
> >
> > Thanks!
> >
> > Ellison Anne
> >
> > On Sat, Aug 6, 2016 at 11:02 AM, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> >> I can definitely help here. I looked at the NiFi release guidelines and
> >> they are a good baseline to follow.
> >> When are we planning on a release ?
> >>
> >> On Sat, Aug 6, 2016 at 10:47 AM, Ellison Anne Williams <
> >> eawilliamspirk@gmail.com> wrote:
> >>
> >>> Hi Mentors,
> >>>
> >>> Can you please give an overview (or point to a good overview) of what
> the
> >>> process is / what we need to do in order to execute our first release?
> >>>
> >>> There is some information on the Accumulo and NiFi websites - happy to
> >>> synthesize those resources into a list for us and email for
> >>> comment/correction, but wanted to check first.
> >>>
> >>> Thanks!
> >>>
> >>> Ellison Anne
> >>>
> >>
> >
>
Re: Mentors - Release Process?
Posted by Tim Ellison <t....@gmail.com>.
On 06/08/16 21:06, Ellison Anne Williams wrote:
> It appears that we reached consensus regarding proceeding with a release. I
> would like to get our first release out over the next couple of weeks.
Yep, it will be a good practice to release early and often. I don't see
any fundamental release blockers in the code (the original contribution
was very "clean"), so it will be an opportunity to exercise the release
process itself.
> Many of our committers are out on vacation/at conferences next week. We can
> go ahead and prepare everything for release and vote accordingly, realizing
> that we may need to wait until folks return to complete the vote. According
> to the documentation below, we need three +1 votes from PPMC members for
> the release in order to elevate it to the IPMC for voting.
Yep.
> First, we need to decide which open JIRA issues we would like to have
> resolved (if any) before making the release. I propose that we complete
> PIRK-29 (user notification of decrypting with wrong Querier) and PIRK-13
> (integrate jackson); we may want to also take a step towards addressing
> PIRK-14 (user examples). Thoughts?
Again, I don't see any blockers yet. It may be good to get into the
habit of assigning the "Fix version" fields of the JIRAs you want to see
in the release.
The very first release may well have limited adoption, understandably,
but quite soon it will be good to get some enhanced user documentation
and examples in place to make it easier for people to pick-up.
> Once we decide on which JIRAs need to be resolved and resolve them, I will
> create a candidate release branch for voting purposes. (Mentors - please
> let me know if I'm doing the wrong thing or the right thing in the wrong
> order here)
>
> For ease of reference, here is the official release information that I was
> able to find (we can move this to the Pirk website too):
>
> - Apache Release Guide: http://www.apache.org/dev/release-publishing
> - Apache Release Policy: http://www.apache.org/dev/release.html
> - Apache Incubator Release Guidelines:
> http://incubator.apache.org/guides/releasemanagement.html
> - Apache Incubator Release Policy:
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> - For Maven Release:
> http://www.apache.org/dev/publishing-maven-artifacts.html
>
> I propose that we follow the Incubator Release Guidelines with some help
> from the Accumulo (https://accumulo.apache.org/releasing) and NiFi (
> https://nifi.apache.org/release-guide.html) release guides. Between these
> webpages, there's lots of great information.
I agree, those projects have a good step-by-step guide to creating a
release. Having a robust and repeatable process ensures we can have a
variety of release managers as the project progresses, which is a good
sign of a healthy project.
Regards,
Tim
> A few questions:
>
> - We need to publish our release to
> http://www.apache.org/dist/incubator/pirk -- however, we do not yet have
> a Pirk folder. Do we need to request the 'pirk' folder from INFRA or can we
> just create it?
> - We have not received our official sign off from the trademark folks
> for the Pirk name - is this necessary before making our first release?
>
> One general TODO:
>
> - In order to publish our release artifact to Maven, we need to have
> Pirk setup in the Nexus Repository - a ticket to INFRA is required --
> http://www.apache.org/dev/publishing-maven-artifacts.html#signing-up
>
> Thanks!
>
> Ellison Anne
>
> On Sat, Aug 6, 2016 at 11:02 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
>> I can definitely help here. I looked at the NiFi release guidelines and
>> they are a good baseline to follow.
>> When are we planning on a release ?
>>
>> On Sat, Aug 6, 2016 at 10:47 AM, Ellison Anne Williams <
>> eawilliamspirk@gmail.com> wrote:
>>
>>> Hi Mentors,
>>>
>>> Can you please give an overview (or point to a good overview) of what the
>>> process is / what we need to do in order to execute our first release?
>>>
>>> There is some information on the Accumulo and NiFi websites - happy to
>>> synthesize those resources into a list for us and email for
>>> comment/correction, but wanted to check first.
>>>
>>> Thanks!
>>>
>>> Ellison Anne
>>>
>>
>
Re: Mentors - Release Process?
Posted by Ellison Anne Williams <ea...@gmail.com>.
Excellent - thanks Suneel!
I would like to wait until Walter completed PIRK-13 and we complete/close
PIRK-29 before moving the branch off for a release vote. This should be
ready to go in the next couple of days.
On Mon, Aug 8, 2016 at 4:24 PM, Suneel Marthi <sm...@apache.org> wrote:
> Nexus and Apache artifacts repository have been setup for Pirk.
>
> See https://issues.apache.org/jira/browse/INFRA-12383
>
> We are good to go ahead with a first release.
>
> On Mon, Aug 8, 2016 at 4:23 PM, Josh Elser <jo...@gmail.com> wrote:
>
> > Suneel Marthi wrote:
> >
> >> - We have not received our official sign off from the trademark
> folks
> >>
> >>> > for the Pirk name - is this necessary before making our first
> >>> release?
> >>> >
> >>>
> >> Maybe a good idea to follow up with the concerned folks on this.
> >>
> >>
> > Not a blocking concern. If the name "Pirk" doesn't pass the
> > podlingnamesearch efforts, the worst case is that there would be some
> Pirk
> > releases and some "Whatever the new name is" releases.
> >
>
Re: Mentors - Release Process?
Posted by Suneel Marthi <sm...@apache.org>.
Nexus and Apache artifacts repository have been setup for Pirk.
See https://issues.apache.org/jira/browse/INFRA-12383
We are good to go ahead with a first release.
On Mon, Aug 8, 2016 at 4:23 PM, Josh Elser <jo...@gmail.com> wrote:
> Suneel Marthi wrote:
>
>> - We have not received our official sign off from the trademark folks
>>
>>> > for the Pirk name - is this necessary before making our first
>>> release?
>>> >
>>>
>> Maybe a good idea to follow up with the concerned folks on this.
>>
>>
> Not a blocking concern. If the name "Pirk" doesn't pass the
> podlingnamesearch efforts, the worst case is that there would be some Pirk
> releases and some "Whatever the new name is" releases.
>
Re: Mentors - Release Process?
Posted by Josh Elser <jo...@gmail.com>.
Suneel Marthi wrote:
> - We have not received our official sign off from the trademark folks
>> > for the Pirk name - is this necessary before making our first release?
>> >
> Maybe a good idea to follow up with the concerned folks on this.
>
Not a blocking concern. If the name "Pirk" doesn't pass the
podlingnamesearch efforts, the worst case is that there would be some
Pirk releases and some "Whatever the new name is" releases.
Re: Mentors - Release Process?
Posted by Suneel Marthi <sm...@apache.org>.
On Sat, Aug 6, 2016 at 4:06 PM, Ellison Anne Williams <
eawilliamspirk@gmail.com> wrote:
> It appears that we reached consensus regarding proceeding with a release. I
> would like to get our first release out over the next couple of weeks.
>
> Many of our committers are out on vacation/at conferences next week. We can
> go ahead and prepare everything for release and vote accordingly, realizing
> that we may need to wait until folks return to complete the vote. According
> to the documentation below, we need three +1 votes from PPMC members for
> the release in order to elevate it to the IPMC for voting.
>
> First, we need to decide which open JIRA issues we would like to have
> resolved (if any) before making the release. I propose that we complete
> PIRK-29 (user notification of decrypting with wrong Querier) and PIRK-13
> (integrate jackson); we may want to also take a step towards addressing
> PIRK-14 (user examples). Thoughts?
>
> Once we decide on which JIRAs need to be resolved and resolve them, I will
> create a candidate release branch for voting purposes. (Mentors - please
> let me know if I'm doing the wrong thing or the right thing in the wrong
> order here)
>
> For ease of reference, here is the official release information that I was
> able to find (we can move this to the Pirk website too):
>
> - Apache Release Guide: http://www.apache.org/dev/release-publishing
> - Apache Release Policy: http://www.apache.org/dev/release.html
> - Apache Incubator Release Guidelines:
> http://incubator.apache.org/guides/releasemanagement.html
> - Apache Incubator Release Policy:
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> - For Maven Release:
> http://www.apache.org/dev/publishing-maven-artifacts.html
>
> I propose that we follow the Incubator Release Guidelines with some help
> from the Accumulo (https://accumulo.apache.org/releasing) and NiFi (
> https://nifi.apache.org/release-guide.html) release guides. Between these
> webpages, there's lots of great information.
>
> A few questions:
>
> - We need to publish our release to
> http://www.apache.org/dist/incubator/pirk -- however, we do not yet
> have
> a Pirk folder. Do we need to request the 'pirk' folder from INFRA or
> can we
> just create it?
>
Created https://issues.apache.org/jira/browse/INFRA-12383
- We have not received our official sign off from the trademark folks
> for the Pirk name - is this necessary before making our first release?
>
Maybe a good idea to follow up with the concerned folks on this.
>
> One general TODO:
>
> - In order to publish our release artifact to Maven, we need to have
> Pirk setup in the Nexus Repository - a ticket to INFRA is required --
> http://www.apache.org/dev/publishing-maven-artifacts.html#signing-up
See https://issues.apache.org/jira/browse/INFRA-12383
>
> Thanks!
>
> Ellison Anne
>
> On Sat, Aug 6, 2016 at 11:02 AM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> > I can definitely help here. I looked at the NiFi release guidelines and
> > they are a good baseline to follow.
> > When are we planning on a release ?
> >
> > On Sat, Aug 6, 2016 at 10:47 AM, Ellison Anne Williams <
> > eawilliamspirk@gmail.com> wrote:
> >
> > > Hi Mentors,
> > >
> > > Can you please give an overview (or point to a good overview) of what
> the
> > > process is / what we need to do in order to execute our first release?
> > >
> > > There is some information on the Accumulo and NiFi websites - happy to
> > > synthesize those resources into a list for us and email for
> > > comment/correction, but wanted to check first.
> > >
> > > Thanks!
> > >
> > > Ellison Anne
> > >
> >
>
Re: Mentors - Release Process?
Posted by Ellison Anne Williams <ea...@gmail.com>.
It appears that we reached consensus regarding proceeding with a release. I
would like to get our first release out over the next couple of weeks.
Many of our committers are out on vacation/at conferences next week. We can
go ahead and prepare everything for release and vote accordingly, realizing
that we may need to wait until folks return to complete the vote. According
to the documentation below, we need three +1 votes from PPMC members for
the release in order to elevate it to the IPMC for voting.
First, we need to decide which open JIRA issues we would like to have
resolved (if any) before making the release. I propose that we complete
PIRK-29 (user notification of decrypting with wrong Querier) and PIRK-13
(integrate jackson); we may want to also take a step towards addressing
PIRK-14 (user examples). Thoughts?
Once we decide on which JIRAs need to be resolved and resolve them, I will
create a candidate release branch for voting purposes. (Mentors - please
let me know if I'm doing the wrong thing or the right thing in the wrong
order here)
For ease of reference, here is the official release information that I was
able to find (we can move this to the Pirk website too):
- Apache Release Guide: http://www.apache.org/dev/release-publishing
- Apache Release Policy: http://www.apache.org/dev/release.html
- Apache Incubator Release Guidelines:
http://incubator.apache.org/guides/releasemanagement.html
- Apache Incubator Release Policy:
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
- For Maven Release:
http://www.apache.org/dev/publishing-maven-artifacts.html
I propose that we follow the Incubator Release Guidelines with some help
from the Accumulo (https://accumulo.apache.org/releasing) and NiFi (
https://nifi.apache.org/release-guide.html) release guides. Between these
webpages, there's lots of great information.
A few questions:
- We need to publish our release to
http://www.apache.org/dist/incubator/pirk -- however, we do not yet have
a Pirk folder. Do we need to request the 'pirk' folder from INFRA or can we
just create it?
- We have not received our official sign off from the trademark folks
for the Pirk name - is this necessary before making our first release?
One general TODO:
- In order to publish our release artifact to Maven, we need to have
Pirk setup in the Nexus Repository - a ticket to INFRA is required --
http://www.apache.org/dev/publishing-maven-artifacts.html#signing-up
Thanks!
Ellison Anne
On Sat, Aug 6, 2016 at 11:02 AM, Suneel Marthi <su...@gmail.com>
wrote:
> I can definitely help here. I looked at the NiFi release guidelines and
> they are a good baseline to follow.
> When are we planning on a release ?
>
> On Sat, Aug 6, 2016 at 10:47 AM, Ellison Anne Williams <
> eawilliamspirk@gmail.com> wrote:
>
> > Hi Mentors,
> >
> > Can you please give an overview (or point to a good overview) of what the
> > process is / what we need to do in order to execute our first release?
> >
> > There is some information on the Accumulo and NiFi websites - happy to
> > synthesize those resources into a list for us and email for
> > comment/correction, but wanted to check first.
> >
> > Thanks!
> >
> > Ellison Anne
> >
>
Re: Mentors - Release Process?
Posted by Suneel Marthi <su...@gmail.com>.
I can definitely help here. I looked at the NiFi release guidelines and
they are a good baseline to follow.
When are we planning on a release ?
On Sat, Aug 6, 2016 at 10:47 AM, Ellison Anne Williams <
eawilliamspirk@gmail.com> wrote:
> Hi Mentors,
>
> Can you please give an overview (or point to a good overview) of what the
> process is / what we need to do in order to execute our first release?
>
> There is some information on the Accumulo and NiFi websites - happy to
> synthesize those resources into a list for us and email for
> comment/correction, but wanted to check first.
>
> Thanks!
>
> Ellison Anne
>