-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/09 13:52, Samuli Seppänen wrote:
> I can't see any reason why the test scripts should be secret. So better
> have them in the open.
I completely agree! That's the very best approach!
> Do you think it'd be possible to have a
> distributed
David Sommerseth ha scritto:
> On 12/12/09 11:52, Samuli Seppänen wrote:
> >> FWIW using a good (rather than merely adequate) revision control
> >> system makes it much easier to keep the very latest code
> >> on-line and still perform regression tests, keep separate
> >> code branches for feature
David Sommerseth ha scritto:
> On 12/12/09 12:37, Samuli Seppänen wrote:
> > Now, if we want to maintain stability, we need some way to test the
> > patches. Automated tests could be used in many cases but building the
> > test cases takes time. In addition I don't think automated tests catch
> > n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/12/09 00:16, James Yonan wrote:
>>
>> However, it _could_ be a requirement that all patches be submitted
>> with documentation. If not, I can't see how you'd want to
>> include any functional changes without also having documentation
>> so some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/12/09 12:37, Samuli Seppänen wrote:
> Now, if we want to maintain stability, we need some way to test the
> patches. Automated tests could be used in many cases but building the
> test cases takes time. In addition I don't think automated tests c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/12/09 11:52, Samuli Seppänen wrote:
>> FWIW using a good (rather than merely adequate) revision control
>> system makes it much easier to keep the very latest code
>> on-line and still perform regression tests, keep separate
>> code branches for
Stefan Monnier ha scritto:
>> One the one hand people expect OpenVPN to be rock-solid in both
>> stability and security. In order to maintain this standard of quality,
>> there needs to be a rigorous process of patch vetting. On the other
>> hand, as an open source project, OpenVPN needs to be
> Via public discussion. Who wants to submit a patch when it
> just disappears without comment. Public discussion has been
> sorely lacking in the past.
>
I can't comment on how patches have been handled in the past, but not
discussing and including them is a sure way to demotivate people.
>>
> One the one hand people expect OpenVPN to be rock-solid in both
> stability and security. In order to maintain this standard of quality,
> there needs to be a rigorous process of patch vetting. On the other
> hand, as an open source project, OpenVPN needs to be transparent and
> open to con
Karl O. Pinc wrote:
On 12/10/2009 04:39:57 AM, Samuli Seppänen wrote:
David Sommerseth ha scritto:
I believe James have received several patches in the past from
people on
the mailing list - or directly.
They will either include patches into their own source
trees, or
kick them back to
On 12/10/2009 04:39:57 AM, Samuli Seppänen wrote:
> David Sommerseth ha scritto:
> > I believe James have received several patches in the past from
> people on
> > the mailing list - or directly.
> > They will either include patches into their own source
> trees, or
> > kick them back to be rewo
David Sommerseth ha scritto:
> On 09/12/09 11:54, Samuli Seppänen wrote:
> >> On Mon, Dec 07, 2009 at 12:25:09PM +0200, Samuli Seppänen wrote:
> >>
> >>> Hello everybody,
> >>>
> >>> I'm the newly appointed community manager for OpenVPN Technologies. I
> >>> will be acting as a liaison between O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/12/09 11:54, Samuli Seppänen wrote:
>
>> On Mon, Dec 07, 2009 at 12:25:09PM +0200, Samuli Seppänen wrote:
>>
>>> Hello everybody,
>>>
>>> I'm the newly appointed community manager for OpenVPN Technologies. I
>>> will be acting as a liaison be
> On Mon, Dec 07, 2009 at 12:25:09PM +0200, Samuli Seppänen wrote:
>
>> Hello everybody,
>>
>> I'm the newly appointed community manager for OpenVPN Technologies. I
>> will be acting as a liaison between OpenVPN community and OpenVPN
>> Technologies. I will help us (the company) make our develo
14 matches
Mail list logo
