My introduction and JIRA karma

Hi folks, I have been recently promoted as HC committer by Oleg. Being an Apache committer for serveral years now, contributing to Apache Maven, I finally decided to join this project too. Oleg asked me to join to make improvements on the GSS-API-based and SSPI-based (Windows)

Re: My introduction and JIRA karma

. On Fri, Nov 14, 2014 at 12:47 PM, Michael Osipov micha...@apache.org wrote: Hi Karl and thanks for the welcome, Am 2014-11-14 um 17:44 schrieb Karl Wright: Welcome onboard! I'm the lead with the ManifoldCF project, which is a heavy user of httpclient, and the implementer of the NTLM code

Re: My introduction and JIRA karma

, it is the only one that has anyone on it, but I am not sure if that is only for PMC members or both PMCs and Committers... Gary On Fri, Nov 14, 2014 at 11:36 AM, Michael Osipov micha...@apache.org wrote: Hi folks, I have been recently promoted as HC committer by Oleg. Being an Apache committer for serveral

Re: My introduction and JIRA karma

of GSSCredential and always assumes implicit credential. Fortunately, there are several ways to solve that problem too. Michael On Fri, Nov 14, 2014 at 1:06 PM, Michael Osipov micha...@apache.org wrote: Am 2014-11-14 um 18:53 schrieb Karl Wright: Hi Michael, [...] Native code is not something

Re: My introduction and JIRA karma

://dirctxsrc.sourceforge.net/xref/net/sf/michaelo/dirctxsrc/DirContextSource.html#L510 [2] http://tomcatspnegoad.sourceforge.net/xref/net/sf/michaelo/tomcat/authenticator/CurrentWindowsIdentityAuthenticator.html#L93 Michael On Fri, Nov 14, 2014 at 1:38 PM, Michael Osipov micha...@apache.org wrote: Am 2014

Re: My introduction and JIRA karma

Am 2014-11-16 um 13:08 schrieb Oleg Kalnichevski: On Sat, 2014-11-15 at 21:58 +0100, Michael Osipov wrote: Am 2014-11-15 um 14:27 schrieb Karl Wright: Hi Michael, I understand how the workaround would work if I should implement it that way, but I'm less certain about your proposed changes

Re: HC core and client 4.4 GA release planning

Am 2014-12-01 um 11:46 schrieb Oleg Kalnichevski: Folks There has been no bug reports / change requests for the 4.4 branch of HttpCore for some while. I see no good reasons to delay 4.4 GA release any longer given that new development efforts have moved to trunk (5.0). Are there any objections

Re: HttpClient 4.4 release notes; Re: HttpClient 4.4 tutorial preview

Am 2015-01-19 um 17:38 schrieb Oleg Kalnichevski: Folks Please review 4.4 release notes and make changes / amendments you deem necessary: http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/RELEASE_NOTES.txt @Michael, I hope the statement about experimental status of the Native

Re: HttpCore 4.4 release notes and JIRA

Am 2015-02-11 um 09:33 schrieb Oleg Kalnichevski: On Tue, 2015-02-10 at 22:25 +0100, Michael Osipov wrote: Hi folks, stupid questions: why do the release notes [1] not mention a word about 4.4 Because the trunk is 5.0. The 4.4.x branch can be found here http://svn.apache.org/repos/asf

Re: HttpClient 4.5 feature release?

Am 2015-02-17 um 11:04 schrieb Oleg Kalnichevski: Folks It looks like the only proper way of resolving HTTPCLIENT-1613 [1] is to extend existing APIs, which (at least ideally) should require a new feature release and a full ALPHA / BETA development cycle. We, of course, could just cut 4.5 GA

Re: svn commit: r1658967 - /httpcomponents/httpcore/trunk/httpcore/src/main/java/org/apache/http/util/VersionInfo.java

Am 2015-02-11 um 21:24 schrieb sebb: On 11 February 2015 at 14:23, micha...@apache.org wrote: Author: michaelo Date: Wed Feb 11 14:23:29 2015 New Revision: 1658967 URL: http://svn.apache.org/r1658967 Log: HTTPCORE-395: VersionInfo#getUserAgent reports incorrect Java version Modified:

HttpCore 4.4 release notes and JIRA

Hi folks, stupid questions: why do the release notes [1] not mention a word about 4.4 and why is the version in JIRA not released with an unresolved issue [2]? [1] http://www.apache.org/dist/httpcomponents/httpcore/RELEASE_NOTES.txt [2]

Re: Need clarification on the auth backend design for HTTPCLIENT-1625

Am 2015-03-13 um 18:05 schrieb Oleg Kalnichevski: On Fri, 2015-03-13 at 15:49 +0100, Michael Osipov wrote: Hi Oleg, finally I am able to respond. Way too late. A cold has knocked me off for 10 days. Same happened to me a month back. It was not fun. Take it easy. ... What about

Re: Need clarification on the auth backend design for HTTPCLIENT-1625

Am 2015-03-15 um 15:15 schrieb Oleg Kalnichevski: On Sat, 2015-03-14 at 23:01 +0100, Michael Osipov wrote: Am 2015-03-13 um 18:05 schrieb Oleg Kalnichevski: On Fri, 2015-03-13 at 15:49 +0100, Michael Osipov wrote: ... That looks quite complex. Anyway, if you can think of a bit

Re: Need clarification on the auth backend design for HTTPCLIENT-1625

Am 2015-03-15 um 23:00 schrieb Oleg Kalnichevski: On Sun, 2015-03-15 at 22:09 +0100, Michael Osipov wrote: Am 2015-03-15 um 15:15 schrieb Oleg Kalnichevski: On Sat, 2015-03-14 at 23:01 +0100, Michael Osipov wrote: Am 2015-03-13 um 18:05 schrieb Oleg Kalnichevski: On Fri, 2015-03-13 at 15:49

Re: Need clarification on the auth backend design for HTTPCLIENT-1625

Hi Oleg, finally I am able to respond. Way too late. A cold has knocked me off for 10 days. Am 2015-03-03 um 18:54 schrieb Oleg Kalnichevski: On Tue, 2015-03-03 at 08:15 +0100, Michael Osipov wrote: Am 2015-03-02 um 12:31 schrieb Oleg Kalnichevski: On Sun, 2015-03-01 at 22:45 +0100

Re: Need clarification on the auth backend design for HTTPCLIENT-1625

Am 2015-03-02 um 12:31 schrieb Oleg Kalnichevski: On Sun, 2015-03-01 at 22:45 +0100, Michael Osipov wrote: Hi folks, I need some design clarification on the HttpClient auth backend. Currently, I trying to figure out how I can plug in connection-based auth best into the code. From reading

Re: Assigning issues

Am 2015-02-27 um 11:28 schrieb Oleg Kalnichevski: On Thu, 2015-02-26 at 21:16 +0100, Michael Osipov wrote: Oleg, is there any reason why you don't assign issues to yourself if you planning to fix/already fixed them? What would be the benefit of that other than extra noise on the mailing

Need clarification on the auth backend design for HTTPCLIENT-1625

Hi folks, I need some design clarification on the HttpClient auth backend. Currently, I trying to figure out how I can plug in connection-based auth best into the code. From reading the docs and the code, this is what I understood now: Client receives a 401/407, looks up the best available

Update Jenkins jobs

Hi folks, can someone update job httpcomponents-client-4.4.x from trunk to branches/4.4.x and create a 4.5.x job from trunk? I am solely a dev on Jenkins. Michael - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For

Re: Update Jenkins jobs

Am 2015-03-01 um 21:16 schrieb Oleg Kalnichevski: On Sun, 2015-03-01 at 20:26 +0100, Michael Osipov wrote: Hi folks, can someone update job httpcomponents-client-4.4.x from trunk to branches/4.4.x and create a 4.5.x job from trunk? Done. https://builds.apache.org/view/H-L/view

Re: HttpClient 4.5 feature release?

Am 2015-02-17 um 11:04 schrieb Oleg Kalnichevski: Folks It looks like the only proper way of resolving HTTPCLIENT-1613 [1] is to extend existing APIs, which (at least ideally) should require a new feature release and a full ALPHA / BETA development cycle. We, of course, could just cut 4.5 GA

Assigning issues

Oleg, is there any reason why you don't assign issues to yourself if you planning to fix/already fixed them? Michael - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail:

Progress of HTTPCLIENT-1625 (2)

Hi folks, I'd like to you to update on the status of my rewrite challenge: It did not turn out to be as easy as I have assumed. I debugged a lot of stuff, read the code, etc. HttpClient is well implementing RFC 2617 auth schemes which are all request-based (stateless), challenge-response

Re: Progress of HTTPCLIENT-1625 (2)

Am 2015-04-17 um 16:47 schrieb Oleg Kalnichevski: On Fri, 2015-04-17 at 13:02 +0200, Michael Osipov wrote: Am 2015-04-14 um 20:35 schrieb Oleg Kalnichevski: On Mon, 2015-04-13 at 22:46 +0200, Michael Osipov wrote: Hi folks, ... Michael, Probably we have to move resolution of this issue

Re: Progress of HTTPCLIENT-1625 (2)

Am 2015-04-14 um 20:35 schrieb Oleg Kalnichevski: On Mon, 2015-04-13 at 22:46 +0200, Michael Osipov wrote: Hi folks, I'd like to you to update on the status of my rewrite challenge: It did not turn out to be as easy as I have assumed. I debugged a lot of stuff, read the code, etc. HttpClient

Re: Progress of HTTPCLIENT-1625/open questions

Am 2015-04-06 um 18:12 schrieb Oleg Kalnichevski: On Mon, 2015-04-06 at 16:26 +0200, Michael Osipov wrote: Hi folks, I have finally started coding of that issue. While I was able to write a working prototype within an hour authenticating against Apache Tomcat and Apache Web Server, an issue

Re: Progress of HTTPCLIENT-1625/open questions

Am 2015-04-07 um 12:04 schrieb Oleg Kalnichevski: On Mon, 2015-04-06 at 22:15 +0200, Michael Osipov wrote: Am 2015-04-06 um 18:12 schrieb Oleg Kalnichevski: On Mon, 2015-04-06 at 16:26 +0200, Michael Osipov wrote: Hi folks, I have finally started coding of that issue. While I was able

Re: Progress of HTTPCLIENT-1625/open questions

Am 2015-04-07 um 14:05 schrieb Oleg Kalnichevski: On Tue, 2015-04-07 at 13:23 +0200, Michael Osipov wrote: ... Oh, Holy Mother. WWW-Authenticate in a 200 response? Really? Absolutely, it can happen on any response code, at least 2xx and 3xx because HTTP is crappy for that. ... I fear

Progress of HTTPCLIENT-1625/open questions

Hi folks, I have finally started coding of that issue. While I was able to write a working prototype within an hour authenticating against Apache Tomcat and Apache Web Server, an issue arose I am not really clear about: Is a credentials provider always necessary for a target host? In other

Re: Progress of HTTPCLIENT-1625/open questions

Am 2015-04-07 um 14:42 schrieb Oleg Kalnichevski: On Tue, 2015-04-07 at 14:25 +0200, Michael Osipov wrote: Am 2015-04-07 um 14:05 schrieb Oleg Kalnichevski: On Tue, 2015-04-07 at 13:23 +0200, Michael Osipov wrote: ... Oh, Holy Mother. WWW-Authenticate in a 200 response? Really? Absolutely

Re: My part in auth APIs refactoring concluded; was Re: Some comments on recent auth API changes

Am 2015-08-12 um 16:25 schrieb Oleg Kalnichevski: On Sun, 2015-08-09 at 20:19 +0200, Oleg Kalnichevski wrote: On Sun, 2015-08-09 at 19:41 +0200, Michael Osipov wrote: Oleg, ... I was going to write everything up in a few days, post it to the list and basically pass everything over to you

Some comments on recent auth API changes

Oleg, just have noticed that you started to rewrite the auth API, here are a few issues which need some improvement: 1. httpclient/src/main/java/org/apache/http/auth/AuthScheme.java: #getPrinciple That is supposed to be #getPricipal and not #getPrinciple. 2. Rename AuthState in

Re: Better header API

Am 2015-11-30 um 19:53 schrieb Gary Gregory: I mean: Index: src/main/java/org/apache/hc/core5/http/HttpMessage.java === --- src/main/java/org/apache/hc/core5/http/HttpMessage.java (revision 1717301) +++

Re: HC 5.0: HttpCore 5.0 alpha1 release

Am 2015-12-01 um 14:35 schrieb Oleg Kalnichevski: Folks I would like to start cutting RC1 for HttpCore 5.0 alpha1 sometime soon. Could you please take a look at the latest snapshot and let me know if you find anything that might block the release or cause another RC build? While this is an

Re: HC 5.0: HttpCore 5.0 alpha1 release

Am 2015-12-01 um 21:52 schrieb Oleg Kalnichevski: On Tue, 2015-12-01 at 21:50 +0100, Michael Osipov wrote: Am 2015-12-01 um 21:46 schrieb Oleg Kalnichevski: On Tue, 2015-12-01 at 21:29 +0100, Michael Osipov wrote: Am 2015-12-01 um 14:35 schrieb Oleg Kalnichevski: Folks I would like to start

Re: HC 5.0: artifact id; Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

Am 2015-11-25 um 17:36 schrieb Oleg Kalnichevski: Folks I made the first pass at re-arranging packages in HttpCore trunk and think it is presently good enough for 5.0-alpha1 Please feel free to take a look. Just checked. Looks like a tremendous move action. I will require a day or two to

Re: HC 5.0: artifact id; Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

Am 2015-11-25 um 21:07 schrieb Gary Gregory: [..] |- httpcore |- httpcore-ab |- httpcore-osgi We should always keep in mind that the artifact should be recognizable by its filname or id. Maybe httpcomponents-httpcore, -httpcore-ab, etc. would be better but they are, of course, longer. (imho)

Re: Better header API

Am 2015-12-01 um 02:22 schrieb Gary Gregory: On Mon, Nov 30, 2015 at 1:43 PM, Michael Osipov <micha...@apache.org> wrote: Am 2015-11-30 um 19:53 schrieb Gary Gregory: I mean: Index: src/main/java/org/apache/hc/core5/http/HttpMessag

Re: Re: Re: HC 5.0: co-location with HC 4.x

> On Fri, 2015-11-20 at 12:42 +0100, Michael Osipov wrote: > > > On Thu, 2015-11-19 at 23:27 +, sebb wrote: > > > > On 19 November 2015 at 21:17, Michael Osipov <micha...@apache.org> > > > > wrote: > > > &

Re: Re: HC 5.0: co-location with HC 4.x

> On Thu, 2015-11-19 at 23:27 +, sebb wrote: > > On 19 November 2015 at 21:17, Michael Osipov <micha...@apache.org> wrote: > > > Am 2015-11-19 um 12:32 schrieb Oleg Kalnichevski: > > ... > > > > > > > First of all, I wouldn't use any of thos

Re: HC 5.0: co-location with HC 4.x

Am 2015-11-20 um 16:33 schrieb Oleg Kalnichevski: On Fri, 2015-11-20 at 15:13 +0100, Michael Osipov wrote: On Fri, 2015-11-20 at 12:42 +0100, Michael Osipov wrote: On Thu, 2015-11-19 at 23:27 +, sebb wrote: On 19 November 2015 at 21:17, Michael Osipov <micha...@apache.org> wrote: A

Re: HC 5.0: co-location with HC 4.x

Am 2015-11-20 um 19:38 schrieb Gary Gregory: On Fri, Nov 20, 2015 at 10:04 AM, Michael Osipov <micha...@apache.org> wrote: Am 2015-11-20 um 16:33 schrieb Oleg Kalnichevski: On Fri, 2015-11-20 at 15:13 +0100, Michael Osipov wrote: On Fri, 2015-11-20 at 12:42 +0100, Michael Osipov

Re: HC 5.0: co-location with HC 4.x

Am 2015-11-20 um 20:57 schrieb Oleg Kalnichevski: I also can well imagine SSL related components being in a separate namespace like 'org.apache.hc.core5.ssl' That would be ok. At the end, you propose: HC Core: org.apache.hc.http.core5 HC Client: org.apache.hc.http.client5 HC Async Cilent:

Re: HC 5.0: co-location with HC 4.x

Am 2015-11-19 um 12:32 schrieb Oleg Kalnichevski: Folks I would like to start working on the first alpha releases of HC 5.0. There is one issue that still needs to be discussed though before I can proceed. We need to decide on how we intent to maintain compatibility with HC 4.x. It is pretty

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

Am 2015-11-21 um 19:52 schrieb Gary Gregory: +1. I would not mind using Java 8 too. Believe that is too early. We are using a company-wide, Eclipse RCP-based product which is on Eclipse 3.4/3.6 and still HttpClient 3.x. I highly doubt that the dev team will jump on e4 and Java 8 features.

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

Am 2015-11-21 um 18:01 schrieb Oleg Kalnichevski: Folks I moved code to org.apache.hc.core5 namespace as the first step. Now I would like to move things around in order to make the package structure more consistent, reduce circular dependencies between packages and prepare for messaging code

Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

> On Sun, Nov 22, 2015 at 3:10 PM, Jon Moore <j...@apache.org> wrote: > > > On Sat, Nov 21, 2015 at 1:56 PM, Michael Osipov <micha...@apache.org> > > wrote: > > > > > Am 2015-11-21 um 19:52 schrieb Gary Gregory: > > > >

Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

> On Sun, 2015-11-22 at 20:42 +0100, Michael Osipov wrote: > > Am 2015-11-22 um 20:11 schrieb Oleg Kalnichevski: > > > On Sat, 2015-11-21 at 19:48 +0100, Michael Osipov wrote: > > >> Am 2015-11-21 um 18:01 schrieb Oleg Kalnichevski: > > >>> Folks > &

Re: Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

> On Mon, 2015-11-23 at 10:51 +0100, Michael Osipov wrote: > > > On Sun, 2015-11-22 at 20:42 +0100, Michael Osipov wrote: > > > > Am 2015-11-22 um 20:11 schrieb Oleg Kalnichevski: > > > > > On Sat, 2015-11-21 at 19:48 +0100, Michael Osipov wrote: > &g

Re: Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

> On Mon, 2015-11-23 at 10:08 +0100, Michael Osipov wrote: > > > On Sun, Nov 22, 2015 at 3:10 PM, Jon Moore <j...@apache.org> wrote: > > > > > > > On Sat, Nov 21, 2015 at 1:56 PM, Michael Osipov <micha...@apache.org> > > > > wrote: >

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

Am 2015-11-22 um 20:11 schrieb Oleg Kalnichevski: On Sat, 2015-11-21 at 19:48 +0100, Michael Osipov wrote: Am 2015-11-21 um 18:01 schrieb Oleg Kalnichevski: Folks I moved code to org.apache.hc.core5 namespace as the first step. Now I would like to move things around in order to make

Re: Do not commit to HttpCore SVN!

icies and practices". I don't want either the master/release branch to be rewritten. On Thu, May 11, 2017 at 9:23 AM, Oleg Kalnichevski <ol...@apache.org> wrote: On Thu, 2017-05-11 at 00:00 +0200, Michael Osipov wrote: Am 2017-05-10 um 23:48 schrieb Oleg Kalnichevski: On Wed, 201

Re: Do not commit to HttpCore SVN!

Am 2017-05-15 um 13:13 schrieb Oleg Kalnichevski: On Mon, 2017-05-15 at 11:54 +0200, Julian Sedding wrote: Force pushing is considered a bad practice in Git for good reasons, thus rewriting history of published branches is IMHO a no-go. It makes everybody's life harder (and developers less

Re: Do not commit to HttpCore SVN!

Am 2017-05-15 um 15:05 schrieb Oleg Kalnichevski: On Mon, 2017-05-15 at 14:58 +0200, Michael Osipov wrote: Am 2017-05-15 um 13:13 schrieb Oleg Kalnichevski: On Mon, 2017-05-15 at 11:54 +0200, Julian Sedding wrote: Force pushing is considered a bad practice in Git for good reasons, thus

Re: Do not commit to HttpCore SVN!

Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski: On Mon, 2017-05-15 at 15:18 +0200, Michael Osipov wrote: ... Am 2017-05-15 um 15:05 schrieb Oleg Kalnichevski: I have _no_ intention of policing other committers. It is emotionally cheaper for me to take time to clean things up and than

Re: Git policies and practices

Am 2017-05-10 um 21:22 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 21:06 +0200, Michael Osipov wrote: Hi folks, given that Oleg finally took up the chance migrating core and client to a Git-based repo, we should agree how we are going to work with in conformance with a good Git practice

Re: Git policies and practices

Am 2017-05-10 um 21:52 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 21:36 +0200, Michael Osipov wrote: ... I would still ask for master being mutable (rewritable) or abandon the concept of a master branch as inapplicable in favor of a release branch such as 5.0.x. One master per

Re: Do not commit to HttpCore SVN!

Am 2017-05-10 um 09:59 schrieb Oleg Kalnichevski: I collected all your latest SVN commits and pushed them to the Git repo. Nothing should have been lost. One personal request. Do you think you could try to make your commits less granular and combine logically related changes into larger change

Re: [VOTE][RESULT] Migrate project source repository to Git

Please do not forget to rename trunk to master: https://git-wip-us.apache.org/repos/asf?p=httpcomponents-core.git;a=shortlog;h=refs/heads/trunk - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands,

Re: Git policies and practices

Am 2017-05-15 um 19:35 schrieb Gary Gregory: On Mon, May 15, 2017 at 9:34 AM, Michael Osipov <micha...@apache.org> wrote: Folks, I have updated the link based on the input and put it onto the wiki: https://wiki.apache.org/HttpComponents/GitGuidelines Here is verbatim copy: = Typical

Re: Git policies and practices

Am 2017-05-15 um 20:22 schrieb Oleg Kalnichevski: On Mon, 2017-05-15 at 20:13 +0200, Michael Osipov wrote: Am 2017-05-15 um 19:35 schrieb Gary Gregory: On Mon, May 15, 2017 at 9:34 AM, Michael Osipov <micha...@apache.or ... Which of the paths should we pick: https://makandracards.

Re: [Httpcomponents Wiki] Update of "GitGuidelines" by MichaelOsipov

Am 2017-05-15 um 18:43 schrieb Gary Gregory: Altassian has a plugin to handle (7) IIRC, we use something like that at work but for SVN. The plugin links a JIRA ticket to commits if the commit message includes the string [JIRA-ID]. There is also Altassian FishEye. I aware of that plugin. In

Re: Git policies and practices

er be able to define the duration of temp, one day, week, months? The dev/ seems redundant to because 4.4.x -- note the X implies development on a bugfix branch. Michael On Mon, May 15, 2017 at 9:34 AM, Michael Osipov <micha...@apache.org> wrote: Folks, I have updated the link ba

Re: Git policies and practices

Am 2017-05-15 um 20:43 schrieb Gary Gregory: On Mon, May 15, 2017 at 11:37 AM, Michael Osipov <micha...@apache.org> wrote: Am 2017-05-15 um 20:18 schrieb Oleg Kalnichevski: On Mon, 2017-05-15 at 18:34 +0200, Michael Osipov wrote: Folks, I have updated the link based on the input a

Re: Fwd: [Httpcomponents Wiki] Update of "GitGuidelines" by MichaelOsipov

Am 2017-05-15 um 18:34 schrieb Gary Gregory: Hi, Thank you for kicking off this thread. I do not think "/" is good enough. At least when I tried it, EGit would not let me create a branch in a branch which makes sense. Which is what I used dev/4.4.x/HTTPCORE-466 in the HttpCore Git repo.

Re: Git policies and practices

Folks, I have updated the link based on the input and put it onto the wiki: https://wiki.apache.org/HttpComponents/GitGuidelines Here is verbatim copy: = Typical Issue Workflow = 1. Branch off master ({{{git checkout -b / master}}}) where {{{}}} is the branch you are going to apply the fix,

Re: [Httpcomponents Wiki] Update of "GitGuidelines" by MichaelOsipov

Am 2017-05-15 um 18:59 schrieb Michael Osipov: Am 2017-05-15 um 18:43 schrieb Gary Gregory: Altassian has a plugin to handle (7) IIRC, we use something like that at work but for SVN. The plugin links a JIRA ticket to commits if the commit message includes the string [JIRA-ID]. There is also

Re: Git policies and practices

Am 2017-05-15 um 20:18 schrieb Gary Gregory: On Mon, May 15, 2017 at 11:13 AM, Michael Osipov <micha...@apache.org> wrote: Am 2017-05-15 um 19:35 schrieb Gary Gregory: On Mon, May 15, 2017 at 9:34 AM, Michael Osipov <micha...@apache.org> wrote: Folks, I have updated th

Re: Git policies and practices / of tendency for good intentions to turn into s..t

Hi Julian, Am 2017-05-17 um 09:30 schrieb Julian Sedding: Hi Oleg and Michael I understand your frustration with a messy commit log. Personally I strive to give context so that the commit can more easily be understood. Normally that includes a JIRA ID and the title. There are cases where I

Re: Git policies and practices / of tendency for good intentions to turn into s..t

Am 2017-05-16 um 09:22 schrieb Oleg Kalnichevski: So, I woke up this morning, took a look at my mail box and found two wonderful commit messages on top of the 4.4.x release branch saying 'oh, forgot this' and 'ah, forgot that' immediately after a dev branch merge. Shit like that will happen

Re: Do not commit to HttpCore SVN!

Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski: On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote: ... Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski: What benefit do you have if it is hard to follow the code paths? How much is "good" code worth if you don't h

Re: Do not commit to HttpCore SVN!

Am 2017-05-10 um 23:48 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 23:25 +0200, Michael Osipov wrote: ... But your answer is contrary to your previous statement -- cherry- picking shouldn't be a fuzz with two different repos. Can you explain why? My understanding is that cherry

Re: Do not commit to HttpCore SVN!

Am 2017-05-10 um 23:19 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 22:00 +0200, Michael Osipov wrote: Am 2017-05-10 um 21:54 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 21:45 +0200, Michael Osipov wrote: This will a problem anyway because all paths change (package names, etc

Git policies and practices

Hi folks, given that Oleg finally took up the chance migrating core and client to a Git-based repo, we should agree how we are going to work with in conformance with a good Git practice to avoid chaos on master. I'd like to provide an example first why a common practive is so necessary to

Re: Do not commit to HttpCore SVN!

Am 2017-05-10 um 21:16 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote: Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote: On Wed, May 10, 2017 at 10:13 AM, Oleg Kalnichevski <olegk@apache .org wr

Re: Do not commit to HttpCore SVN!

Am 2017-05-10 um 21:42 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 21:27 +0200, Michael Osipov wrote: Am 2017-05-10 um 21:16 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote: Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 11:15

Re: Do not commit to HttpCore SVN!

Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote: On Wed, May 10, 2017 at 10:13 AM, Oleg Kalnichevski

Re: Git policies and practices

Am 2017-05-10 um 21:31 schrieb Bindul Bhowmik: On Wed, May 10, 2017 at 1:25 PM, sebb <seb...@gmail.com> wrote: It would be helpful to document this on the Wiki and/or website On 10 May 2017 at 20:22, Oleg Kalnichevski <ol...@apache.org> wrote: On Wed, 2017-05-10 at 21:06 +0200, Mi

One Git repo per major version

Folks, since there is still some disagreement on how an issue should be applied to 4.4.x and 5.0.x, I'd like to propose the following two ideas: Have one repo per major version and all pain will end: httpcomponents-core-4 httpcomponents-client-4 httpcomponents-core-5 httpcomponents-client-5

Re: Do not commit to HttpCore SVN!

Am 2017-05-10 um 21:54 schrieb Oleg Kalnichevski: On Wed, 2017-05-10 at 21:45 +0200, Michael Osipov wrote: This will a problem anyway because all paths change (package names, etc.). Hopefully Git's similarity algorithm can detect this. No, it is not. Git is that great. It always amazes me

Re: Git policies and practices

Since I haven't received anymore comments on the guidelines, I'll close the questioning and call a vote for commmitters and PMC members. Michael - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands,

Re: [Httpcomponents Wiki] Update of "GitGuidelines" by MichaelOsipov

Am 2017-05-22 um 09:59 schrieb Oleg Kalnichevski: On Sun, 2017-05-21 at 21:17 +0200, Michael Osipov wrote: Am 2017-05-21 um 19:07 schrieb Oleg Kalnichevski: On Sun, 2017-05-21 at 17:27 +0200, Michael Osipov wrote: ... Am 2017-05-21 um 11:42 schrieb Oleg Kalnichevski: What is a timeframe

Re: [VOTE] Git Guidelines

Am 2017-05-22 um 20:29 schrieb Gary Gregory: On Mon, May 22, 2017 at 11:16 AM, Michael Osipov <micha...@apache.org> wrote: Am 2017-05-22 um 06:46 schrieb Gary Gregory: I will follow whatever the community decides; my only request is that precise git instructions be provided for contri

Re: [VOTE] Git Guidelines

if there a bug fix I just must have ASAP. On what do you exact Git steps? How to squash/rewrite? On a release? Maven Release Plugin does that for you On May 21, 2017 2:00 AM, "Michael Osipov" <micha...@apache.org> wrote: Hi folks, I am casting this vote for the previously discusse

Re: Re: Git merges

> Hi Oleg, > > I'm sure we need no noise at all but I could not figure out how to clean it > up. > > I do know that got one cherry-picked commit right for one of the tickets. > > For the other, I could not get rid of the merge commits. If you can't merge properly, please ask for help before

Re: Git merges

Am 2017-05-24 um 13:49 schrieb Oleg Kalnichevski: On Wed, 2017-05-24 at 11:51 +0200, Michael Osipov wrote: Hi Oleg, I'm sure we need no noise at all but I could not figure out how to clean it up. I do know that got one cherry-picked commit right for one of the tickets. For the other, I could

[VOTE] Git Guidelines (2)

Hi folks, I am re-casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off a release branch (e.g., 4.4.x, 5.0.x)

Re: [VOTE] Git Guidelines (2)

Am 2017-05-24 um 19:11 schrieb Michael Osipov: Hi folks, I am re-casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off

Re: Git merges

Am 2017-05-24 um 18:55 schrieb Oleg Kalnichevski: . Michael, Is there anything holding back the vote? Not from my side. I did cast it (see [VOTE] Git Guidelines), but didn't receive no official votes. I will extend the period. Don't forget to cast your vote! Michael The subject of the

Re: [VOTE] Git Guidelines

Am 2017-05-21 um 11:00 schrieb Michael Osipov: Hi folks, I am casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off

[VOTE] Git Guidelines

Hi folks, I am casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off a release branch (e.g., 4.4.x, 5.0.x) ({{{git

Re: [Httpcomponents Wiki] Update of "GitGuidelines" by MichaelOsipov

Am 2017-05-21 um 11:42 schrieb Oleg Kalnichevski: On Sun, 2017-05-21 at 08:52 +, Apache Wiki wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on "Httpcomponents Wiki" for change notification. The "GitGuidelines" page has been changed by MichaelOsipov:

Re: [VOTE] Git Guidelines (2)

Am 2017-05-24 um 19:11 schrieb Michael Osipov: Hi folks, I am re-casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off

Re: Git policies and practices / of tendency for good intentions to turn into s..t

Am 2017-05-18 um 09:38 schrieb Oleg Kalnichevski: On Wed, 2017-05-17 at 22:56 -0700, Gary Gregory wrote: Now that I am done with the branch dev/4.4.x/HTTPCORE-468 and the code is merged into 4.4.x, is it OK to delete the branch? Of course, once merged a dev branch should be deleted in the

Re: HttpCore / HttpClient fully migrated to Git

Am 2017-05-18 um 09:31 schrieb Oleg Kalnichevski: On Wed, 2017-05-17 at 09:12 -0700, Gary Gregory wrote: On May 17, 2017 6:54 AM, "Oleg Kalnichevski" wrote: Folks HttpCore / HttpClient have been fully migrated to Git, GitHub replication and all. Happy hacking, pushing and

Re: Git repo naming

> On Mon, 2017-05-08 at 11:48 +0200, Michael Osipov wrote: > > Based on Daniel Gruno's answer, we should discuss repo names first. > > > > Michael > > > > OK. How about this? > > HttpCore -> httpcomponents-core > HttpClient -> httpcompo

Disagreement on Log4J2

Hi folks, it recently has come to my attention that Commons Logging has been replaced with Log4J2. Well, I proposed almost two years ago to move to SLF4J for good reasons [1]. People disagreed that Commons Logging is good enough and this discussion has been held several times w/o any

Re: SSLContextBuilder.[use|set]Protocol(String)

Am 2017-05-05 um 02:02 schrieb Gary Gregory: Hi, In Core 4.4.x we have: SSLContextBuilder.useProtocol(String) and in 5.0, we have: SSLContextBuilder.setProtocol(String) How about adding SSLContextBuilder.setProtocol(String) to 4.4.x and deprecating useProtocol(String) to make porting

Re: Git repo naming

Am 2017-05-08 um 15:51 schrieb Oleg Kalnichevski: On Mon, 2017-05-08 at 14:54 +0200, Oleg Kalnichevski wrote: On Mon, 2017-05-08 at 14:12 +0200, Michael Osipov wrote: On Mon, 2017-05-08 at 11:48 +0200, Michael Osipov wrote: Based on Daniel Gruno's answer, we should discuss repo names first

  1   2   3   4   5   6   7   8   9   10   >