Hi Christian,
Regarding https://issues.apache.org/jira/browse/LOGCXX-418, is it possible
to be granted access to Jenkins?
http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson
Right now I can login, but I cannot create jobs.
Any ASF project can run build and test tasks for their pro
On 06.01.2014 18:25, Joseph Southwell wrote:
> Sounds good to me.
[...]
> On Jan 6, 2014, at 10:25 AM, Thorsten Schöning wrote:
> [...]
>> Said that, "tags/latest_stable" would be much better than
>> "current_stable" and I would use this unless people shout at me.
+1
--
flo
Sounds good to me.
Joseph Southwell
jos...@southwell.org
The past is history,
The future's a mystery,
The present's a gift.
On Jan 6, 2014, at 10:25 AM, Thorsten Schöning wrote:
> Guten Tag Joseph Southwell,
> am Montag, 6. Januar 2014 um 16:56 schrieben Sie:
>
>> How will stable and current
Guten Tag Joseph Southwell,
am Montag, 6. Januar 2014 um 16:56 schrieben Sie:
> How will stable and current_stable be different?
They won't, I just suggested two names for the same thing: Only one
tag where our latest stable release and latest official web site
information will get published from
On Jan 3, 2014, at 1:34 PM, Thorsten Schöning wrote:
> As we now know that the website is not build from trunk automatically 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.
> 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
Guten Tag Rhys Ulerich,
am Freitag, 3. Januar 2014 um 16:59 schrieben Sie:
> I like the 0.11.0, 0.11.1, and 0.12.0 plan that Thorsten set out with
> the implication that "trunk" means the last, public, stable release.
> That makes the public APIs and website reflect stable in a
> straightforward m
On 3 Jan 2014, at 18:04, Alexandru Zbarcea wrote:
Can we consider the .git (git://git.apache.org/log4cxx.git) repo as
the
main repo and not the subversion one?
http://git.apache.org/
Can we push/commit to this git repository directly?
Currently this is a git mirror of the svn repos.
However
> 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,
Can we consider the .git (git://git.apache.org/log4cxx.git) repo as the
main repo and not the subversion one?
http://git.apache.org/
Can we push/commit to this git repository directly?
I would rather manage stable (release/intermediary release) with "tags". In
this way, you know you have a s
>>> 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
Guten Tag Joseph Southwell,
am Freitag, 3. Januar 2014 um 15:49 schrieben Sie:
> Perhaps I am behind the times, but that doesn't match my
> expectation when I go check out a source repository for a project.
> If I want to try the bleeding edge of development code I always go
> checkout trunk. Havi
Perhaps I am behind the times, but that doesn't match my expectation when I go
check out a source repository for a project. If I want to try the bleeding edge
of development code I always go checkout trunk. Having that not be the bleeding
edge seems like another thing we would have to document a
Hello,
as we now have commit access to log4cxx, I would like to create a new
directory structure to get new patches etc. applied and move towards
our first incubation release which will be entirely based on the "old"
codebase with all the patches since 0.10.0 which seemed to never ever
make it int
14 matches
Mail list logo