+1 (non-binding)
So far I've checked:
* signatures and digests
* source releases file layouts,
* matched git tag and commit ids
* NOTICE and LICENSE files
* license headers
* build sources in a clean environment (Maven 3.5.0, OpenJDK 1.8.0_144
64-Bit, Debian amd64)
On Sun, Nov 5, 2017 at 7:4
Hi,
coming closed to the Commons PMC procedure, I'd like to update the vote
with the following information:
* Source release can be found in the office dist area:
https://dist.apache.org/repos/dist/dev/commons/rdf/apache-commons-rdf-0.5.0-RC1/
* 0.5.0-RC1 tagged at git:
https://git-wip-us.apache
created
http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC2/
(rev 1814438)
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-06 20:46 GMT+01:00 Gary Gregory :
> On Mon, Nov 6, 2017 at 11:11 AM, Thomas Vandahl wrote:
>
>> On 06.11.17 04:48,
FWIW, I don't use the release plugin.
Gary
On Mon, Nov 6, 2017 at 12:22 PM, Romain Manni-Bucau
wrote:
> Hmm,
>
> there are probably a lot of manual workarounds - like not using the
> release plugin at all to start easy, but I was more looking for a
> standard normalized procedure like mvn relea
On Mon, Nov 6, 2017 at 11:11 AM, Thomas Vandahl wrote:
> On 06.11.17 04:48, Gary Gregory wrote:
> > The document http://commons.apache.org/releases/prepare.html clearly
> shows
> > an example of an RC tag being labeled with the "RC1" postfix.
>
> Not in the maven-release-plugin chapter. And with
Hmm,
there are probably a lot of manual workarounds - like not using the
release plugin at all to start easy, but I was more looking for a
standard normalized procedure like mvn release:prepare && mvn
release:perform-rc && mvn release:promote-rc or something like that.
Ideally 2 commands matching
Just be sure you have pushChanges=false, so you can manually push the work
to your RC branch, but you don't push the tag.
Anyways, the commit id is binding for a vote, not the tag (because can be
changed).
On Mon, Nov 6, 2017 at 11:14 AM, Romain Manni-Bucau
wrote:
> Will not recopy what i said
Will not recopy what i said in jcs vote thread but git solves it
creating the tag locally so you can immediately copy it *locally* and
only push the rc tag for the vote duration. That said most of
communities push the tag on a fork and avoid any issue with the asf
repo. This is how git can solve th
Think the idea was to avoid to have a tag which can have been checked
out already but fundamentally agree there is no point to have such a
rule and it just makes the project handling hard with no benefit in
practise.
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-
On 06.11.17 09:01, Romain Manni-Bucau wrote:
> 2017-11-06 8:59 GMT+01:00 Jochen Wiedmann :
>> On Mon, Nov 6, 2017 at 7:27 AM, Romain Manni-Bucau
>> wrote:
>>
>>> due to the RCx procedure we cant use the maven release plugin, any
>>> plan to make it working with commons release procedure or do we j
On 06.11.17 04:48, Gary Gregory wrote:
> The document http://commons.apache.org/releases/prepare.html clearly shows
> an example of an RC tag being labeled with the "RC1" postfix.
Not in the maven-release-plugin chapter. And with reason. The problem of
the later copy would be, that the tagged pom.
Hi,
On Sun, Nov 5, 2017 at 11:26 PM, Romain Manni-Bucau
wrote:
> Answers inline.
>
> 2017-11-06 7:08 GMT+01:00 Gary Gregory :
> > The blocker part is that the VOTE email does not follow the process or
> the
> > format outlined on http://commons.apache.org/releases/prepare.html
> >
> > Specifical
Hi All:
Here is a start: http://git-wip-us.apache.org/repos/asf/commons-testing.git
The JIRA project key is TEST.
Gary
Hello experts
I added a gitignore file to Commons Configuration project.
https://github.com/apache/commons-configuration/pull/9/files
Thanks
Minglei
Hello experts
I implemented a tool that can directly read a file name by its current
classloader read an Inputstream and returns a java.util.Properties and created
two JIRA for this issue as I am not sure which components are the best. The
code and the conversions are here:
https://github.com
Github user zhangminglei commented on the issue:
https://github.com/apache/commons-collections/pull/33
Thanks @kinow . I would move this PR to Commons/Configuration. I just not
sure which component is the best to put it.
---
--
Github user kinow commented on the issue:
https://github.com/apache/commons-collections/pull/33
Thanks for the clear response Minglei! And thanks for your contribution.
Let's see what others think :+1:
---
-
To uns
Github user zhangminglei commented on the issue:
https://github.com/apache/commons-collections/pull/33
Hello, @kinow Thanks for your reply!
- Why Commons Collections?. I am not sure which is the best address I
should put it. At the beginning, I created the JIRA under Commons
Github user kinow commented on the issue:
https://github.com/apache/commons-collections/pull/33
Hi @zhangminglei !
Sure. Few questions from reviewing the JIRA ticket and the pull request.
* Why Commons Collections? The SortedProperties uses Java collection
classes to
Github user zhangminglei commented on the issue:
https://github.com/apache/commons-collections/pull/33
The CI error seems does not relevant to this PR.
---
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
Github user zhangminglei commented on the issue:
https://github.com/apache/commons-collections/pull/33
Hello, @kinow, Could you please take a look on this PR? Thanks!
---
-
To unsubscribe, e-mail: dev-unsubscr...@com
Github user coveralls commented on the issue:
https://github.com/apache/commons-collections/pull/33
[](https://coveralls.io/builds/14052842)
Coverage increased (+0.006%) to 86.622% when pulling
**3ee56fdce999b
GitHub user zhangminglei opened a pull request:
https://github.com/apache/commons-collections/pull/33
[COLLECTIONS-664] Add a class that extend a load method which accept â¦
â¦a filename.
You can merge this pull request into a Git repository by running:
$ git pull https://git
2017-11-06 8:59 GMT+01:00 Jochen Wiedmann :
> On Mon, Nov 6, 2017 at 7:27 AM, Romain Manni-Bucau
> wrote:
>
>> due to the RCx procedure we cant use the maven release plugin, any
>> plan to make it working with commons release procedure or do we just
>> wait to move all to git?
>
> What problem is
On Mon, Nov 6, 2017 at 7:27 AM, Romain Manni-Bucau
wrote:
> due to the RCx procedure we cant use the maven release plugin, any
> plan to make it working with commons release procedure or do we just
> wait to move all to git?
What problem is there when using the plugin?
Thanks,
Jochen
--
The
25 matches
Mail list logo
