You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by Jordan Zimmerman <jo...@jordanzimmerman.com> on 2014/10/16 22:55:49 UTC
2.7.0 release?
Folks,
I think we should release 2.7.0 at this point (unless there are objections). Scott, would you like to handle the release?
-Jordan
Re: 2.7.0 release?
Posted by Scott Blum <dr...@gmail.com>.
Oh wait.. it looks like they went and fixed it for me. I missed that in
the comments. Ok, I have access now. They just want us to be self-service
in the future.
On Fri, Oct 31, 2014 at 5:42 PM, Scott Blum <dr...@gmail.com> wrote:
> Just comment on https://issues.apache.org/jira/browse/INFRA-8428
>
> On Fri, Oct 31, 2014 at 4:39 PM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
>> Can you forward the email? They don’t seem to understand the problem (not
>> unusual).
>>
>> -JZ
>>
>>
>> On October 31, 2014 at 3:27:57 PM, Scott Blum (dragonsinth@gmail.com)
>> wrote:
>>
>> Pinged them, they said they won't micro manage invididual wikis. They
>> gave me this link which is a "how to" on granting access:
>>
>> https://confluence.atlassian.com/display/DOC/Assigning+Space+Permissions
>>
>> On Fri, Oct 31, 2014 at 12:46 PM, Jordan Zimmerman <
>> jordan@jordanzimmerman.com> wrote:
>>
>>> Grrr - please ping INFRA again. For now, just give me the edits.
>>>
>>>
>>> On October 31, 2014 at 11:42:54 AM, Scott Blum (dragonsinth@gmail.com)
>>> wrote:
>>>
>>> Ah good call. BTW: I still can't edit the wiki. :( I was going to
>>> add a little text to explain the binary vs. source releases.
>>>
>>> On Fri, Oct 31, 2014 at 12:40 PM, Jordan Zimmerman <
>>> jordan@jordanzimmerman.com> wrote:
>>>
>>>> You can activate multiple profiles. That’s what I do.
>>>>
>>>> -JZ
>>>>
>>>>
>>>> On October 31, 2014 at 11:38:41 AM, Scott Blum (dragonsinth@gmail.com)
>>>> wrote:
>>>>
>>>> Right, but when I activate that profile, that's when I want my apache
>>>> GPG key and curator-website-checkout-path to get set, right? I don't just
>>>> want that stuff active all the time when I'm doing non-Curator relative mvn
>>>> stuff.
>>>>
>>>> On Fri, Oct 31, 2014 at 12:37 PM, Jordan Zimmerman <
>>>> jordan@jordanzimmerman.com> wrote:
>>>>
>>>>> BTW: I think the .m2 settings need another tiny update. The
>>>>> <profile> section needs: <id>apache-release</id> right?
>>>>>
>>>>>
>>>>> No - that profile is in the Apache parent pom.
>>>>>
>>>>>
>>>>> -JZ
>>>>>
>>>>
>>>>
>>>
>>
>
Re: 2.7.0 release?
Posted by Scott Blum <dr...@gmail.com>.
Just comment on https://issues.apache.org/jira/browse/INFRA-8428
On Fri, Oct 31, 2014 at 4:39 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> Can you forward the email? They don’t seem to understand the problem (not
> unusual).
>
> -JZ
>
>
> On October 31, 2014 at 3:27:57 PM, Scott Blum (dragonsinth@gmail.com)
> wrote:
>
> Pinged them, they said they won't micro manage invididual wikis. They
> gave me this link which is a "how to" on granting access:
>
> https://confluence.atlassian.com/display/DOC/Assigning+Space+Permissions
>
> On Fri, Oct 31, 2014 at 12:46 PM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
>> Grrr - please ping INFRA again. For now, just give me the edits.
>>
>>
>> On October 31, 2014 at 11:42:54 AM, Scott Blum (dragonsinth@gmail.com)
>> wrote:
>>
>> Ah good call. BTW: I still can't edit the wiki. :( I was going to add
>> a little text to explain the binary vs. source releases.
>>
>> On Fri, Oct 31, 2014 at 12:40 PM, Jordan Zimmerman <
>> jordan@jordanzimmerman.com> wrote:
>>
>>> You can activate multiple profiles. That’s what I do.
>>>
>>> -JZ
>>>
>>>
>>> On October 31, 2014 at 11:38:41 AM, Scott Blum (dragonsinth@gmail.com)
>>> wrote:
>>>
>>> Right, but when I activate that profile, that's when I want my apache
>>> GPG key and curator-website-checkout-path to get set, right? I don't just
>>> want that stuff active all the time when I'm doing non-Curator relative mvn
>>> stuff.
>>>
>>> On Fri, Oct 31, 2014 at 12:37 PM, Jordan Zimmerman <
>>> jordan@jordanzimmerman.com> wrote:
>>>
>>>> BTW: I think the .m2 settings need another tiny update. The
>>>> <profile> section needs: <id>apache-release</id> right?
>>>>
>>>>
>>>> No - that profile is in the Apache parent pom.
>>>>
>>>>
>>>> -JZ
>>>>
>>>
>>>
>>
>
Re: 2.7.0 release?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
Can you forward the email? They don’t seem to understand the problem (not unusual).
-JZ
On October 31, 2014 at 3:27:57 PM, Scott Blum (dragonsinth@gmail.com) wrote:
Pinged them, they said they won't micro manage invididual wikis. They gave me this link which is a "how to" on granting access:
https://confluence.atlassian.com/display/DOC/Assigning+Space+Permissions
On Fri, Oct 31, 2014 at 12:46 PM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
Grrr - please ping INFRA again. For now, just give me the edits.
On October 31, 2014 at 11:42:54 AM, Scott Blum (dragonsinth@gmail.com) wrote:
Ah good call. BTW: I still can't edit the wiki. :( I was going to add a little text to explain the binary vs. source releases.
On Fri, Oct 31, 2014 at 12:40 PM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
You can activate multiple profiles. That’s what I do.
-JZ
On October 31, 2014 at 11:38:41 AM, Scott Blum (dragonsinth@gmail.com) wrote:
Right, but when I activate that profile, that's when I want my apache GPG key and curator-website-checkout-path to get set, right? I don't just want that stuff active all the time when I'm doing non-Curator relative mvn stuff.
On Fri, Oct 31, 2014 at 12:37 PM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
BTW: I think the .m2 settings need another tiny update. The <profile> section needs: <id>apache-release</id> right?
No - that profile is in the Apache parent pom.
-JZ
Re: 2.7.0 release?
Posted by Scott Blum <dr...@gmail.com>.
Pinged them, they said they won't micro manage invididual wikis. They gave
me this link which is a "how to" on granting access:
https://confluence.atlassian.com/display/DOC/Assigning+Space+Permissions
On Fri, Oct 31, 2014 at 12:46 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> Grrr - please ping INFRA again. For now, just give me the edits.
>
>
> On October 31, 2014 at 11:42:54 AM, Scott Blum (dragonsinth@gmail.com)
> wrote:
>
> Ah good call. BTW: I still can't edit the wiki. :( I was going to add a
> little text to explain the binary vs. source releases.
>
> On Fri, Oct 31, 2014 at 12:40 PM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
>> You can activate multiple profiles. That’s what I do.
>>
>> -JZ
>>
>>
>> On October 31, 2014 at 11:38:41 AM, Scott Blum (dragonsinth@gmail.com)
>> wrote:
>>
>> Right, but when I activate that profile, that's when I want my apache
>> GPG key and curator-website-checkout-path to get set, right? I don't just
>> want that stuff active all the time when I'm doing non-Curator relative mvn
>> stuff.
>>
>> On Fri, Oct 31, 2014 at 12:37 PM, Jordan Zimmerman <
>> jordan@jordanzimmerman.com> wrote:
>>
>>> BTW: I think the .m2 settings need another tiny update. The
>>> <profile> section needs: <id>apache-release</id> right?
>>>
>>>
>>> No - that profile is in the Apache parent pom.
>>>
>>>
>>> -JZ
>>>
>>
>>
>
Re: 2.7.0 release?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
Grrr - please ping INFRA again. For now, just give me the edits.
On October 31, 2014 at 11:42:54 AM, Scott Blum (dragonsinth@gmail.com) wrote:
Ah good call. BTW: I still can't edit the wiki. :( I was going to add a little text to explain the binary vs. source releases.
On Fri, Oct 31, 2014 at 12:40 PM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
You can activate multiple profiles. That’s what I do.
-JZ
On October 31, 2014 at 11:38:41 AM, Scott Blum (dragonsinth@gmail.com) wrote:
Right, but when I activate that profile, that's when I want my apache GPG key and curator-website-checkout-path to get set, right? I don't just want that stuff active all the time when I'm doing non-Curator relative mvn stuff.
On Fri, Oct 31, 2014 at 12:37 PM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
BTW: I think the .m2 settings need another tiny update. The <profile> section needs: <id>apache-release</id> right?
No - that profile is in the Apache parent pom.
-JZ
Re: 2.7.0 release?
Posted by Scott Blum <dr...@gmail.com>.
Ah good call. BTW: I still can't edit the wiki. :( I was going to add a
little text to explain the binary vs. source releases.
On Fri, Oct 31, 2014 at 12:40 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> You can activate multiple profiles. That’s what I do.
>
> -JZ
>
>
> On October 31, 2014 at 11:38:41 AM, Scott Blum (dragonsinth@gmail.com)
> wrote:
>
> Right, but when I activate that profile, that's when I want my apache GPG
> key and curator-website-checkout-path to get set, right? I don't just want
> that stuff active all the time when I'm doing non-Curator relative mvn
> stuff.
>
> On Fri, Oct 31, 2014 at 12:37 PM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
>> BTW: I think the .m2 settings need another tiny update. The
>> <profile> section needs: <id>apache-release</id> right?
>>
>>
>> No - that profile is in the Apache parent pom.
>>
>>
>> -JZ
>>
>
>
Re: 2.7.0 release?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
You can activate multiple profiles. That’s what I do.
-JZ
On October 31, 2014 at 11:38:41 AM, Scott Blum (dragonsinth@gmail.com) wrote:
Right, but when I activate that profile, that's when I want my apache GPG key and curator-website-checkout-path to get set, right? I don't just want that stuff active all the time when I'm doing non-Curator relative mvn stuff.
On Fri, Oct 31, 2014 at 12:37 PM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
BTW: I think the .m2 settings need another tiny update. The <profile> section needs: <id>apache-release</id> right?
No - that profile is in the Apache parent pom.
-JZ
Re: 2.7.0 release?
Posted by Scott Blum <dr...@gmail.com>.
Right, but when I activate that profile, that's when I want my apache GPG
key and curator-website-checkout-path to get set, right? I don't just want
that stuff active all the time when I'm doing non-Curator relative mvn
stuff.
On Fri, Oct 31, 2014 at 12:37 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> BTW: I think the .m2 settings need another tiny update. The <profile>
> section needs: <id>apache-release</id> right?
>
>
> No - that profile is in the Apache parent pom.
>
>
> -JZ
>
Re: 2.7.0 release?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
BTW: I think the .m2 settings need another tiny update. The <profile> section needs: <id>apache-release</id> right?
No - that profile is in the Apache parent pom.
-JZ
Re: 2.7.0 release?
Posted by Scott Blum <dr...@gmail.com>.
On Fri, Oct 31, 2014 at 7:46 AM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> >although I had to type in my gpg passphrase like a billion times (can't
> get gpg-agent working properly on mac).
> I just updated the Wiki. You can set your PGP password in the Maven
> settings file.
>
Awesome, I did finally get it to work, I had to install pinentry-mac so
that gpg-agent could pop up the UI for me.
BTW: I think the .m2 settings need another tiny update. The <profile>
section needs: <id>apache-release</id> right?
> >I don't really understand the difference between the two different forms
> of staging
> It’s an Apache thing. Apache releases are SOURCE code releases, not
> binaries. So, even though no one will ever use it, you must push the source
> artifacts to the Apache servers.
>
Yep, finally figured that out later when I was like "OMG where's the
binaries?" and finally got Nexus working.
Re: 2.7.0 release?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
>although I had to type in my gpg passphrase like a billion times (can't get gpg-agent working properly on mac).
I just updated the Wiki. You can set your PGP password in the Maven settings file.
>I don't really understand the difference between the two different forms of staging
It’s an Apache thing. Apache releases are SOURCE code releases, not binaries. So, even though no one will ever use it, you must push the source artifacts to the Apache servers.
-JZ
On October 30, 2014 at 11:56:07 PM, Scott Blum (dragonsinth@gmail.com) wrote:
The Nexus stuff doesn't seem to be working. I ran through the instructions up to that point, but I'm not sure where I'm supposed to look on Nexus. I poked around but don't see anything 2.7.0 anywhere. As far as I can tell, everything seemed fine up to that point, although I had to type in my gpg passphrase like a billion times (can't get gpg-agent working properly on mac).
I'm going to go ahead with the next section tho and push to the svn dist/dev/curator. I don't really understand the difference between the two different forms of staging, or why I have to rebuild it so many times. Wouldn't the artifacts that got installed during step 3 in the first section be usable in step 2 in the second section?
On Fri, Oct 17, 2014 at 11:26 AM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
When you’re ready, just follow the instructions here:
https://cwiki.apache.org/confluence/display/CURATOR/For+Curator+Committers#ForCuratorCommitters-release-curator
Ask questions if/as you run into problems. Like all things Apache, everything has to be just-so.
-JZ
On October 16, 2014 at 4:09:36 PM, Jordan Zimmerman (jordan@jordanzimmerman.com) wrote:
Sure - OK with me
On October 16, 2014 at 4:09:11 PM, Scott Blum (dragonsinth@gmail.com) wrote:
Sure. Any chance of getting in CURATOR-145 in this release? It's the
max-depth addition to TreeCache, which can truly let it replace both
NodeCache and PathChildrenCache. It would be nice to release it with
max-depth for these cases to get some miles on it.
On Thu, Oct 16, 2014 at 4:55 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> Folks,
>
> I think we should release 2.7.0 at this point (unless there are
> objections). Scott, would you like to handle the release?
>
> -Jordan
>
>
>
Re: 2.7.0 release?
Posted by Scott Blum <dr...@gmail.com>.
Oh wait, looks like it did publish after all, but I had to log in on Nexus
to see it and understand what I was even looking at.
On Fri, Oct 31, 2014 at 12:56 AM, Scott Blum <dr...@gmail.com> wrote:
> The Nexus stuff doesn't seem to be working. I ran through the
> instructions up to that point, but I'm not sure where I'm supposed to look
> on Nexus. I poked around but don't see anything 2.7.0 anywhere. As far as
> I can tell, everything seemed fine up to that point, although I had to type
> in my gpg passphrase like a billion times (can't get gpg-agent working
> properly on mac).
>
> I'm going to go ahead with the next section tho and push to the svn
> dist/dev/curator. I don't really understand the difference between the two
> different forms of staging, or why I have to rebuild it so many times.
> Wouldn't the artifacts that got installed during step 3 in the first
> section be usable in step 2 in the second section?
>
> On Fri, Oct 17, 2014 at 11:26 AM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
>> When you’re ready, just follow the instructions here:
>>
>>
>> https://cwiki.apache.org/confluence/display/CURATOR/For+Curator+Committers#ForCuratorCommitters-release-curator
>>
>> Ask questions if/as you run into problems. Like all things Apache,
>> everything has to be just-so.
>>
>> -JZ
>>
>>
>> On October 16, 2014 at 4:09:36 PM, Jordan Zimmerman (
>> jordan@jordanzimmerman.com) wrote:
>>
>> Sure - OK with me
>>
>>
>>
>> On October 16, 2014 at 4:09:11 PM, Scott Blum (dragonsinth@gmail.com)
>> wrote:
>>
>> Sure. Any chance of getting in CURATOR-145 in this release? It's the
>> max-depth addition to TreeCache, which can truly let it replace both
>> NodeCache and PathChildrenCache. It would be nice to release it with
>> max-depth for these cases to get some miles on it.
>>
>> On Thu, Oct 16, 2014 at 4:55 PM, Jordan Zimmerman <
>> jordan@jordanzimmerman.com> wrote:
>>
>> > Folks,
>> >
>> > I think we should release 2.7.0 at this point (unless there are
>> > objections). Scott, would you like to handle the release?
>> >
>> > -Jordan
>> >
>> >
>> >
>>
>>
>
Re: 2.7.0 release?
Posted by Scott Blum <dr...@gmail.com>.
The Nexus stuff doesn't seem to be working. I ran through the instructions
up to that point, but I'm not sure where I'm supposed to look on Nexus. I
poked around but don't see anything 2.7.0 anywhere. As far as I can tell,
everything seemed fine up to that point, although I had to type in my gpg
passphrase like a billion times (can't get gpg-agent working properly on
mac).
I'm going to go ahead with the next section tho and push to the svn
dist/dev/curator. I don't really understand the difference between the two
different forms of staging, or why I have to rebuild it so many times.
Wouldn't the artifacts that got installed during step 3 in the first
section be usable in step 2 in the second section?
On Fri, Oct 17, 2014 at 11:26 AM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> When you’re ready, just follow the instructions here:
>
>
> https://cwiki.apache.org/confluence/display/CURATOR/For+Curator+Committers#ForCuratorCommitters-release-curator
>
> Ask questions if/as you run into problems. Like all things Apache,
> everything has to be just-so.
>
> -JZ
>
>
> On October 16, 2014 at 4:09:36 PM, Jordan Zimmerman (
> jordan@jordanzimmerman.com) wrote:
>
> Sure - OK with me
>
>
>
> On October 16, 2014 at 4:09:11 PM, Scott Blum (dragonsinth@gmail.com)
> wrote:
>
> Sure. Any chance of getting in CURATOR-145 in this release? It's the
> max-depth addition to TreeCache, which can truly let it replace both
> NodeCache and PathChildrenCache. It would be nice to release it with
> max-depth for these cases to get some miles on it.
>
> On Thu, Oct 16, 2014 at 4:55 PM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
> > Folks,
> >
> > I think we should release 2.7.0 at this point (unless there are
> > objections). Scott, would you like to handle the release?
> >
> > -Jordan
> >
> >
> >
>
>
Re: 2.7.0 release?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
When you’re ready, just follow the instructions here:
https://cwiki.apache.org/confluence/display/CURATOR/For+Curator+Committers#ForCuratorCommitters-release-curator
Ask questions if/as you run into problems. Like all things Apache, everything has to be just-so.
-JZ
On October 16, 2014 at 4:09:36 PM, Jordan Zimmerman (jordan@jordanzimmerman.com) wrote:
Sure - OK with me
On October 16, 2014 at 4:09:11 PM, Scott Blum (dragonsinth@gmail.com) wrote:
Sure. Any chance of getting in CURATOR-145 in this release? It's the
max-depth addition to TreeCache, which can truly let it replace both
NodeCache and PathChildrenCache. It would be nice to release it with
max-depth for these cases to get some miles on it.
On Thu, Oct 16, 2014 at 4:55 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> Folks,
>
> I think we should release 2.7.0 at this point (unless there are
> objections). Scott, would you like to handle the release?
>
> -Jordan
>
>
>
Re: 2.7.0 release?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
Sure - OK with me
On October 16, 2014 at 4:09:11 PM, Scott Blum (dragonsinth@gmail.com) wrote:
Sure. Any chance of getting in CURATOR-145 in this release? It's the
max-depth addition to TreeCache, which can truly let it replace both
NodeCache and PathChildrenCache. It would be nice to release it with
max-depth for these cases to get some miles on it.
On Thu, Oct 16, 2014 at 4:55 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> Folks,
>
> I think we should release 2.7.0 at this point (unless there are
> objections). Scott, would you like to handle the release?
>
> -Jordan
>
>
>
Re: 2.7.0 release?
Posted by Scott Blum <dr...@gmail.com>.
Sure. Any chance of getting in CURATOR-145 in this release? It's the
max-depth addition to TreeCache, which can truly let it replace both
NodeCache and PathChildrenCache. It would be nice to release it with
max-depth for these cases to get some miles on it.
On Thu, Oct 16, 2014 at 4:55 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> Folks,
>
> I think we should release 2.7.0 at this point (unless there are
> objections). Scott, would you like to handle the release?
>
> -Jordan
>
>
>