[Had a private chat with Ralph and the outcome of it is] I will see if I
can spare time for it this week. If not, I will let you know at the end of
the week. In the worst case, next month I will start working for a new team
in the company where I will be officially allowed to claim plenty of time
t
On Mon, Aug 03, 2020 at 07:34:15PM -0500, Matt Sicker wrote:
> Very well said! It helps get user feedback quicker, too.
+1!
Also, the current "stable" has some many bugs (I carry 13 non Debian-specific
patches in the current Debian package…) and a new release would also fix some
open
Bugs on the
On Mon, Aug 03, 2020 at 07:49:14PM -0400, Robert Middleton wrote:
> Thorsten,
>
> > > A number of these are rather large changes, so it probably
> > > doesn't make sense to work on them until there's a known-good release, as
> > > they would likely break both API and ABI compatibility.
> >
> > D
Very well said! It helps get user feedback quicker, too.
On Mon, Aug 3, 2020 at 19:03 Ralph Goers wrote:
> Here are my thoughts after working on several ASF projects for over 15
> years.
>
> Theoretically logging projects should follow the “release early, release
> often” philosophy. There are a
Here are my thoughts after working on several ASF projects for over 15 years.
Theoretically logging projects should follow the “release early, release often”
philosophy. There are a few good reasons why it should be that way. However,
when you have a project with very few committers with limited
Thorsten,
> > A number of these are rather large changes, so it probably
> > doesn't make sense to work on them until there's a known-good release, as
> > they would likely break both API and ABI compatibility.
>
> Does it really matter much if things are broken now vs. with 0.12.0 or
> alike? B
Thanks Remko. That makes 3 +1 votes from PMC members.
Ralph
> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
>
> +1 Remko.
>
> On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker wrote:
>
>> +1 from me. We can handle the release signing afterwards as Ralph suggests.
>>
>> On Mon, 3 Aug 2020 at 10:30
+1 Remko.
On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker wrote:
> +1 from me. We can handle the release signing afterwards as Ralph suggests.
>
> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
> wrote:
> >
> > Can other PMC members please review this? It has been more than 72
> hours.
> >
> > Ralph
> >
+1 from me. We can handle the release signing afterwards as Ralph suggests.
On Mon, 3 Aug 2020 at 10:30, Ralph Goers wrote:
>
> Can other PMC members please review this? It has been more than 72 hours.
>
> Ralph
>
> > On Jul 30, 2020, at 11:17 PM, Davyd McColl wrote:
> >
> > Hi all, I've never
Can other PMC members please review this? It has been more than 72 hours.
Ralph
> On Jul 30, 2020, at 11:17 PM, Davyd McColl wrote:
>
> Hi all, I've never done this before, so bear with me if I fluff it:
>
> This is a proposed vote to release log4net 2.0.9 from PR
> https://github.com/apache
Guten Tag Robert Middleton,
am Montag, 3. August 2020 um 02:17 schrieben Sie:
> I'd like to propose some new features/updates for log4cxx, if there's
> interest.
Things mostly read good and interesting to me. Even though I would
suffer myself a lot most likely, as my currently used compiler/IDE i
11 matches
Mail list logo
