Hi
Obviously it is ultimately up to you how you want to support things but
I'd just say that with a limited development team it is probably best to
avoid hard and fast support commitments.
I think a lot of small open source projects get bogged down in writing
and following rules and policies when
On Fri, Dec 10, 2010 at 11:09 PM, Kevin Bowling
wrote:
> On Fri, Dec 10, 2010 at 8:45 PM, Nick Mathewson wrote:
>>
>> Hi, all! Here's a thing I wrote up to try to explain a proposed
>> policy for what to backport to 2.0.x once it's stable, and what to
>> backport to 1.4.x after 2.0.x is released
On Fri, Dec 10, 2010 at 8:45 PM, Nick Mathewson wrote:
> Hi, all! Here's a thing I wrote up to try to explain a proposed
> policy for what to backport to 2.0.x once it's stable, and what to
> backport to 1.4.x after 2.0.x is released. Absent major problems with
> it, the current Libevent core d
Hi, all! Here's a thing I wrote up to try to explain a proposed
policy for what to backport to 2.0.x once it's stable, and what to
backport to 1.4.x after 2.0.x is released. Absent major problems with
it, the current Libevent core developers are probably going to stick
with this for official rele
