> In fact, former releases of
> log4cxx already contained project files generated by cpptaasks.
Even if we drop cpptasks for build purposes, will we still need Maven
to use the current site generation?
- Rhys
> Or clone/fork it into Trafodion, if you need updates or continued
maintenance.
Any chance apr-util could pick up the torch? That would at least centralize
it as anyone needing log4cxx needs apr-util.
- Rhys
> It doesn't look like there's other members still around
I'm still lurking but have not touched the code for awhile.
It is, and has been, unclear what needs to happen for a 0.11.0 release
candidate [1]. Much of the problem is that there's no concensus on what
build system should work. Autoto
[
https://issues.apache.org/jira/browse/LOGCXX-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich closed LOGCXX-441.
---
Resolution: Fixed
Reporter says not reproducible on trunk.
> Log4cxx SocketAppender leads
Resurrecting an old thread...
Currently there are only a couple of items left for 0.11.0 per
https://issues.apache.org/jira/browse/LOGCXX/fixforversion/12313090/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel.
The blocking installation errors LOGCXX-426 and LOGCXX-448 a
[
https://issues.apache.org/jira/browse/LOGCXX-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243661#comment-14243661
]
Rhys Ulerich commented on LOGCXX-441:
-
Would you please provide the appe
[
https://issues.apache.org/jira/browse/LOGCXX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243656#comment-14243656
]
Rhys Ulerich commented on LOGCXX-396:
-
Are you able to checkout SVN head, confi
[
https://issues.apache.org/jira/browse/LOGCXX-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich resolved LOGCXX-446.
-
Resolution: Fixed
Addressed by r1644820.
> make install fails, trying to overwrite header fi
[
https://issues.apache.org/jira/browse/LOGCXX-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich resolved LOGCXX-428.
-
Resolution: Fixed
Fix Version/s: 0.11.0
Addressed in r1644820.
> Wildcards in Makefile
[
https://issues.apache.org/jira/browse/LOGCXX-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240702#comment-14240702
]
Rhys Ulerich commented on LOGCXX-446:
-
This is a dupe of LOG4CXX-428.
> make
[
https://issues.apache.org/jira/browse/LOGCXX-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich reassigned LOGCXX-446:
---
Assignee: Rhys Ulerich (was: Alex Zbarcea)
> make install fails, trying to overwrite hea
Hi Christian,
> I have added a small report to the wiki:
> https://wiki.apache.org/incubator/December2014
I might have said
1. Create a release
2. Create a release
3. Create a release
but I think your version communicates the point well.
Towards that goal, I've (finally) started looking
[
https://issues.apache.org/jira/browse/LOGCXX-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240699#comment-14240699
]
Rhys Ulerich commented on LOGCXX-428:
-
Have been staring at this a bit tonight--
[
https://issues.apache.org/jira/browse/LOGCXX-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178330#comment-14178330
]
Rhys Ulerich commented on LOGCXX-442:
-
As I'm not familiar with that porti
Hi all,
I've crawled out from under my rock (dissertation completed,
postgraduate job started, settled in new city). It would be good to
get 0.11.0 out the door by end of November.
Beyond LOG4CXX-428 (which I'll do this week), what
development/bugfixes/JIRAs must be addressed in 0.11.0?
If ther
[
https://issues.apache.org/jira/browse/LOGCXX-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich resolved LOGCXX-443.
-
Resolution: Fixed
Fix Version/s: 0.11.0
Fixed in r1633356, including changelog update
Rhys Ulerich created LOGCXX-443:
---
Summary: Return by const reference in Logger::getName()
Key: LOGCXX-443
URL: https://issues.apache.org/jira/browse/LOGCXX-443
Project: Log4cxx
Issue Type: Bug
> it's a bit quite the last weeks, so the only thing coming into my mind
> is to simply mention that. Everything else is like the last report.
Agreed on all accounts. Thank you Thorsten.
- Rhys
Do we have a chat room? Would it be worth lurking in #log4cxx on Freenode?
- Rhys
[
https://issues.apache.org/jira/browse/LOGCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940818#comment-13940818
]
Rhys Ulerich commented on LOGCXX-361:
-
> And I don't think we should i
(Thread subject changed as we've now definitely veered away from
report concerns...)
> If CMAKE and Windows is the more problematic candidate than we should
> start with this first, we won't gain anything if you succeed with a
> replacement for autotools only. :-)
Quite true. On the Un*x side, a
Any one know why
const LogString Logger::getName() const { return name; }
within src/main/include/log4cxx/logger.h doesn't return a const reference a la
const LogString& Logger::getName() const { return name; }
In src/main/include/log4cxx/logstring.h the typedef is just
typedef std
On Sun, Mar 9, 2014 at 4:21 PM, Florian Seydoux wrote:
> At APR, cmake seems experimental, but I feel/hope it's the way to go for
> log4cxx - unfortunately, I don't have real experience with it, but I'll
> try it (current situation is a bit frustrating).
Would CMake as the only build system satis
Sorry to have been vague in my intent...
I feel the log4cxx-supported Windows build system(s) should be at
least the APR-supported Windows build system(s). Hence looking at APR
for inspiration and maybe a public list of supported stuff that we
could use.
> I don't think I get the idea behind thi
> don't you want to start a separate thread for this discussion?
Maybe. If we'd like to ask for guidance from the APR folks, the
report might be a good vehicle for it.
- Rhys
Hi Thorsten,
Thank you for writing the draft.
> 1. We probably need to decide what's an acceptable platform/compiler list,
> sort out any
> remaining hiccups, and then move towards a release.
Most true. The un*x side is easy-- we use the autotools and nearly
any compiler one wants to th
[
https://issues.apache.org/jira/browse/LOGCXX-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich updated LOGCXX-428:
Priority: Blocker (was: Major)
> Wildcards in Makefile.am break either VPATH or non-VP
Rhys Ulerich created LOGCXX-428:
---
Summary: Wildcards in Makefile.am break either VPATH or non-VPATH
installs
Key: LOGCXX-428
URL: https://issues.apache.org/jira/browse/LOGCXX-428
Project: Log4cxx
On Tue, Feb 25, 2014 at 2:44 AM, Thorsten Schöning
wrote:
>> - org.apache.xml.serialize ->
>> com.sun.org.apache.xml.internal.serialize
> - /Zi ->> /Z7
>
> Interesting, I never did those changes but mvn simply works. There's
> only some warnings.
Same here. If you're using Ant, I'd do it through
> Actually this gives me an idea for a future feature. What if we made it so
> changing settings while a configureAndWatch is active updated the settings
> file itself? We could make it an option to configureAndWatch. Anybody else
> like that idea? Should I open a feature request in Jira?
If I
> Or do we only want one file for one tool as reference?
That is my inclination. Artistic Style is available as a binary
download for Windows, OS X, and Linux and the configuration file is
quite short (e.g. [1]) and matches the manual [2] well
- Rhys
[1] https://github.com/RhysU/tuna/blob/maste
> it's time to flame! ;-)
Flame on! 1TBS, 4 space indent, nary a tab, and 80 column firm limit.
I say this with 2 24" monitors in front of me. I often debug by
printing and reading, and line wrapping is awful as is printing 125
characters per line to avoid it. We could go Fortran and say 132
c
> It worked without "template<>" in VS, but I added such a statement now and
> hopefulyl this works in GCC as well.
Thank you. I ran into
log4cxx/src/main/include/log4cxx/level.h:279:67: error: specialization
of 'template bool
log4cxx::helpers::ObjectPtrT::operator==(const
log4cxx::helpers::Obj
>> (a) makes visual studio 6 projects, which cannot be used by Visual
>> studio versions above 2008; so you have to convert them with a VS2008
>> before being able to build with 2010, 2012 or later.
>
> Isn't that an argument to remove the creation of projects by cpptasks?
> I have the feeling this
[
https://issues.apache.org/jira/browse/LOGCXX-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903605#comment-13903605
]
Rhys Ulerich commented on LOGCXX-394:
-
You make a good point re: the equality ch
[
https://issues.apache.org/jira/browse/LOGCXX-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902862#comment-13902862
]
Rhys Ulerich commented on LOGCXX-394:
-
Is there some way to fix the orig
>> The better approach should be to use Level::equals for comparison.
> They are, so far as I can tell, the same thing under the covers per
> Level::equals within level.cpp.
Eh, maybe not, but it'd be awkward if one works differently from the other.
- Rhys
> The better approach should be to use Level::equals for comparison.
They are, so far as I can tell, the same thing under the covers per
Level::equals within level.cpp.
- Rhys
> I have some comments regarding commits that are only whitespaces. Is
> difficult to watch, follow or filter (if you are on Windows, probably, you
> do not see them).
I've had good luck using command line SVN's '-x "-b"' option to ignore
whitespace changes when looking at diffs and blames. Does
> ... my only intention was to take what
> I had the feeling was the boring part of reading through the bugs and
> let us fix the problems later together.
I very much appreciate the effort you spent in doing bug triage. It
has been quite impressive.
Please don't stop if you're inclined to contin
FYI, r1567530 tweaks the unit test harness to get e.what() when e
inherits from std::exception.
$ ./src/test/cpp/testsuite -v cacheddateformattestcase
...
Line -1: Unexpected std::exception: basic_string::compare
Line -1: Unexpected std::exception: basic_string::compare
Line -1: Unexpected std::ex
> I'm guessing the problem is in the test cases themselves-- I'll try to
> hook up a debugger to verify soon.
Finally got that debugger attached. The unexpected exceptions are
std::out_of_range, I think, from bad invocations of
std::string::compare. The backtraces all resemble
__cxa_throw () fr
[
https://issues.apache.org/jira/browse/LOGCXX-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898802#comment-13898802
]
Rhys Ulerich commented on LOGCXX-319:
-
r1567525 updates the examples and test
[
https://issues.apache.org/jira/browse/LOGCXX-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich reopened LOGCXX-337:
-
The application of the patch broke compilation. I've tried repairing things in
r1567521
Hi all,
Please, please don't apply and commit patches from issues unless you
can confirm build correctly afterwards. The fixes for 320 and 305
have been invoked APR methods without the correct arguments and have
dropped down mismatched processor directives.
- Rhys
[
https://issues.apache.org/jira/browse/LOGCXX-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich resolved LOGCXX-320.
-
Resolution: Fixed
r1567511 fixes that compilation issue, though several others remain atop that
[
https://issues.apache.org/jira/browse/LOGCXX-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich reopened LOGCXX-320:
-
Assignee: Rhys Ulerich (was: Curt Arnold)
The patch applied in r154 included a bad call
[
https://issues.apache.org/jira/browse/LOGCXX-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896059#comment-13896059
]
Rhys Ulerich commented on LOGCXX-381:
-
Thank you.
> Pkgconfig can
[
https://issues.apache.org/jira/browse/LOGCXX-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich reopened LOGCXX-381:
-
I disagree with the patch as 'apr-1' and 'apr-1-util' should not be presen
> Ok, I can try to make something, but it will really be a draft...
It's not too bad, just edit the wiki at
https://wiki.apache.org/incubator/February2014 to plug our details in.
Re: issues. We probably need to decide what's an acceptable
platform/compiler list, sort out any remaining hiccups, a
> May others have a look at LOG4CXX-420 and -422 and the code before I
> changed it? If you come to the conclusion I wrote nonsense, I will
> simply revert the patch and have a later look at this again. Else we
> may comment the failing tests after creating an issue.
I'm guessing the problem is in
> Which test fails with which error?
I must admit to being a bit of a dunce with respect to the unit tests.
I see
$ ./src/test/cpp/testsuite cacheddateformattestcase
LC_CTYPE: en_US.UTF-8
cacheddateformattestcase: FAILED 4 of 19
Failed Tests Total Fail Failed %
Hi all,
On trunk I've just recently started seeing make check fail repeat-ably
on cacheddateformattestcase.
Running the bisection (using
http://search.cpan.org/~infinoid/App-SVN-Bisect-1.1/bin/svn-bisect)
svn-bisect --min 1556710 --max 1562827 start
identifies r1559522 as the culprit. Thorste
[
https://issues.apache.org/jira/browse/LOGCXX-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich resolved LOGCXX-424.
-
Resolution: Fixed
Done using Requires in r1562823 then Requires.private in 1562826.
I believe
Rhys Ulerich created LOGCXX-424:
---
Summary: liblog4cxx.pc.in should reflect dependency on apr-1,
apr-1-util
Key: LOGCXX-424
URL: https://issues.apache.org/jira/browse/LOGCXX-424
Project: Log4cxx
[
https://issues.apache.org/jira/browse/LOGCXX-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich resolved LOGCXX-423.
-
Resolution: Fixed
Fix Version/s: 0.10.1
Fixed in r1562810.
> Repair autogen scr
Rhys Ulerich created LOGCXX-423:
---
Summary: Repair autogen script warnings
Key: LOGCXX-423
URL: https://issues.apache.org/jira/browse/LOGCXX-423
Project: Log4cxx
Issue Type: Bug
> I have a problem with the build process and started a question on
> stackoverflow
>
> http://stackoverflow.com/questions/21269335/how-to-deactivate-or-hook-linking-in-ant-contrib-cpptasks
I don't know those systems well, but I have done the cowardly thing
and upvoted the question on SO.
- R
> I changed the ant build to automatically retrieve the contents of the
> project page index and added links back to the project site.
Excellent.
> But this
> does only work with ant, do we need to get the same with autotools?
> Ant already replaces some strings in the Doxygen.in file, but I
> co
>> a short question: do wee all agree to ~restrict the codebase to ansi C++
>> (ie. -std=c++98) without 03/11 extension?
I'm fine with 98.
- Rhys
On Thu, Jan 9, 2014 at 10:47 AM, chand priyankara wrote:
> Index: src/main/include/log4cxx/spi/loggingevent.h
> ===
> --- src/main/include/log4cxx/spi/loggingevent.h (revision 1556590)
> +++ src/main/include/log4cxx/spi/loggingevent.h
> I didn't like that 'fpermissive' thing.
Agreed. It was only a workaround.
> I fixed it by putting spi:: in KeySet.
Goofy question, how exactly? I'd love to see a diff.
- Rhys
Hi Thorsten,
>> Documents produced by doxygen are derivative works derived from the
>> input used in their production; they are not affected by this
>> license.
>
> To me this reads like we can simply remove the changes to the
> stylesheets and use the original ones, am I correct?
I read this the
> If we cannot reproduce a bug and we get no reply from the submitter what is
> our course of action in the issue tracking system?
Mark Resolved as Cannot Reproduce?
- Rhys
[
https://issues.apache.org/jira/browse/LOGCXX-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich resolved LOGCXX-385.
-
Resolution: Fixed
Done already in r1511175.
> bin/install: will not overwrite just-crea
[
https://issues.apache.org/jira/browse/LOGCXX-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866300#comment-13866300
]
Rhys Ulerich commented on LOGCXX-385:
-
'make install' just ran cle
[
https://issues.apache.org/jira/browse/LOGCXX-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich reassigned LOGCXX-385:
---
Assignee: Rhys Ulerich (was: Curt Arnold)
> bin/install: will not overwrite just-crea
Hi Thorsten,
I noticed that you clobbered mainpage.dox...
r1556263 | tschoening | 2014-01-07 10:18:46 -0600 (Tue, 07 Jan 2014) | 1 line
Changed paths:
M /incubator/log4cxx/trunk/pom.xml
M /incubator/log4cxx/trunk/src/s
Hi Chand,
I've filed https://issues.apache.org/jira/browse/LOGCXX-419 and will
>> take a look at it.
>>
>
I believe I have that fixed now. Please let me know if it continues to
give you trouble.
- Rhys
[
https://issues.apache.org/jira/browse/LOGCXX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich resolved LOGCXX-419.
-
Resolution: Fixed
> 'typedef spi::KeySet KeySet' changes meani
[
https://issues.apache.org/jira/browse/LOGCXX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866268#comment-13866268
]
Rhys Ulerich commented on LOGCXX-419:
-
Fix in r1556709.
> 'typedef
As we close JIRA issues, should we modify src/changes/changes.xml
along the way? Or is that something which is generally a separate
release preparation step?
If we should, do you want me to add and
nodes to changes.xml and place updates
under 0.12.0? Or should I tack them onto the existing 0.1
[
https://issues.apache.org/jira/browse/LOGCXX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866259#comment-13866259
]
Rhys Ulerich commented on LOGCXX-419:
-
Problem appears to be that "KeySet
> Personally, I have currently access to:
Several compilers
GCC 4.5, 4.6, 4.7, 4.8
Intel 11.1, 12.1, 13.1
on Ubuntu and Scientific Linux boxen. Not much else.
- Rhys
[
https://issues.apache.org/jira/browse/LOGCXX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865026#comment-13865026
]
Rhys Ulerich commented on LOGCXX-419:
-
This has bitten me in the past on GCC
Rhys Ulerich created LOGCXX-419:
---
Summary: 'typedef spi::KeySet KeySet' changes meaning of typedef
Key: LOGCXX-419
URL: https://issues.apache.org/jira/browse/LOGCXX-419
Project: Log4cxx
Hi Thorsten,
> Could some of you please test the build? Something like "mvn clean
> site" should be enough.
It builds for me on Maven 3.0.4. I tweaked the incubation statement
in r1556432. Thanks for all the effort you put into getting the site
generation going.
- Rhys
> Generated code or generated documentation shouldn't be on the VCS
> (subversion), right?
Agreed.
Unless I'm mistaken, Thorsten is dealing with non-generated
documentation needing to link to generated documentation.
- Rhys
> Does anyone has any experience with Doxygen regarding this kind of
> "issue" or any clever idea how to deal with this? I may tent to don't
> use ids in the links at all and hope that file names won't change that
> often.
I think the filenames are fairly stable and would use them without hesitati
> log4cxx-417: atoi undefined on MacOS
IIRC, the older SVN commits use all caps on the issue identifier a la
LOG4CXX.
Looks good to me.
- Rhys
> Based on Christian suggestion I propose on setting a CI on the
> http://ci.apache.org/#jenkins
>
> What is your opinion?
It would be great to have both the Ant and Autotools builds running there.
- Rhys
> I propose to request for a "native" git repository.
I'd prefer to keep the SVN repo:
1) The project is inherently centralized and so I'm not sure what
we'd gain by picking up a distributed RCS.
2) The SVN infrastructure is all in place and seemingly working fine.
There's no indication that we
> As we now know that the website is not build from trunk automatically...
(Thank you for checking).
> I would be fine with leaving trunk as it is and using it for upcoming
> development, but creating "new" release branches from the history of
> the trunk for 0.11.0 and 0.11.1 as described before
> 2) in log4j we use the log4j-dev@ list for commits. You might want to
> reconsider using log4cxx-dev as well
>
> Personally I would suggest we use log4cxx-dev for commit notifications until
> the commit traffic
> becomes so overwhelming that we can't manage it anymore
>
> Wdyt?
Let's go with you
> Is there a ticket for this? I'd like to help.
>
> autotools
> ant
> maven
Offhand, not that I'm aware of.
At least by 0.12.0, I'd planned to take a pass through JIRA for
tickets like LOG4CXX-385 (which Roland mentioned) to make Autotools
happy again out-of-the-box.
That particular issue is sim
> Can we push/commit to this git repository directly?
Doesn't look like it...
"This is a collection of read-only Git mirrors of Apache codebases."
> Can we set up a travis/jenkins for CI?
Dunno. Is there some CI infrastructure already available through the ASF?
- Rhys
Hi Roland,
> Just wanted to mention that... GNU autotools based build should remain
> workable.
Thanks for speaking up. I definitely plan to keep the Autotools alive
and well. I've been worrying about Ant/Maven since they're what
permits cross-platform. I personally plan to develop against
Aut
>> Is there a commit notification mailing list for our repo?
>
> Yes there should be one - actually it should be the dev list.
Just on a hunch, I tried log4cxx-cvs-subscr...@apache.org but it
bounced. I'd prefer having a separate commit notification list as it
keeps the traffic lower on log4cxx-d
Hi Michael,
A group of folks are re-incubating log4cxx. We're trying to get some
pre-incubation releases prepped reflecting the state of work from
before we arrived.
I noticed there's a
http://svn.apache.org/repos/asf/incubator/log4cxx/branches/mcatan/
present in SVN. Is there anything that
>>> I would like to create the branches 0.11.0, 0.11.1 and 0.12.0 base on
>>> the current history and would like to revert trunk back to the last
>>> official release 0.10.0. The only changes I would keep in trunk would
>>> be those from Christian regarding the website etc., but no changes to
>>> t
> I tend to believe that we should start to build log4cxx with Ant. My
feeling is that
> Maven was using Ant to build it. If the Ant stuff works, we could
renenable the Maven build for it,
> or leave it out.
Ah, sorry for crying wolf. I had hit a classpath issue with the cpptasks
JAR. I didn't rec
Hi Christian,
I'm taking a stab at getting an Ant- and/or Maven-based development
build going following either
https://logging.apache.org/log4cxx/building/maven.html or
https://logging.apache.org/log4cxx/building/ant.html. I'm rusty with
Ant, a noob at Maven, and I'm hitting some trouble.
I noti
> History is still keeping an eye on the list :-)
In that case, we should keep The Old Guard (TM) happy in case we have
to ask them questions. :P
I added that crew to pom.xml as emeritus roles. Be unfair to inherit
a decade of code without some credit.
Is there a commit notification mailing lis
Hi Christian,
> Maybe make a little test commit with adding your name to the list of
> committers in
> https://svn.apache.org/repos/asf/incubator/log4cxx/trunk/pom.xml
Success. I added a section to the XML and added an entry
following the examples from
https://svn.apache.org/repos/asf/maven/pom
>> Anyone else willing to serve as a moderator for those?
>
> Me.
Thanks Thorsten. Anyone else?
Ticket filed at https://issues.apache.org/jira/browse/INFRA-7147.
> Is there anything I need to read, understand or know?
I'm guessing we'll get some inline instructions in any email that gets
bounc
Hi all,
Alright, there's something up at
https://wiki.apache.org/incubator/January2014. Please adjust or
complain at will.
Happy New Year if we don't speak again before,
Rhys
>> In particular, can someone confirm that last release date?
> AFAICS 0.11.0 is a renamed 0.10.1 and each fix and commit afterwards
> got contributed under that version number from 2008-07-01 until today
>
> I currently don't understand when commits on trunk count as official
> releases...
I
> I tried SVN and JIRA access with my created username and password
> today, but failed. Am I correct that both access depend on this ticket
> or am I doing something wrong?
I think SVN access for the incubation space depends upon this ticket.
I've been able to access the committers space describe
Hi all,
We've got a podling report due on Wednesday the 1st. I've started on
being able to edit the form at
http://wiki.apache.org/incubator/January2014.
In the meantime, would you take a look at some draft content (below)
and tell me if it looks okay or if there's something you'd like to see
ch
Hi Christian,
Are we on the hook for a report due on the 1st?
> From: Roman Shaposhnik
> http://wiki.apache.org/incubator/January2014
> Wed January 01 -- Podling reports due by end of day
I see some placeholder content but I either lack permissions to login
to the Wiki (or else I'm being stupid
1 - 100 of 110 matches
Mail list logo
