On 27 November 2012 18:29, sebb wrote:
> On 27 November 2012 17:16, Ralph Goers wrote:
>>
>> On Nov 27, 2012, at 5:12 AM, Gilles Sadowski wrote:
>>
>>> On Tue, Nov 27, 2012 at 10:55:14AM +, sebb wrote:
On 26 November 2012 17:41, Ralph Goers wrote:
> Traceability by who?
>
>
On 27 November 2012 17:16, Ralph Goers wrote:
>
> On Nov 27, 2012, at 5:12 AM, Gilles Sadowski wrote:
>
>> On Tue, Nov 27, 2012 at 10:55:14AM +, sebb wrote:
>>> On 26 November 2012 17:41, Ralph Goers wrote:
Traceability by who?
PMC members can easily verify that what is committ
On Nov 27, 2012, at 5:12 AM, Gilles Sadowski wrote:
> On Tue, Nov 27, 2012 at 10:55:14AM +, sebb wrote:
>> On 26 November 2012 17:41, Ralph Goers wrote:
>>> Traceability by who?
>>>
>>> PMC members can easily verify that what is committed to dist matches what
>>> they verified using what t
On Tue, Nov 27, 2012 at 10:55:14AM +, sebb wrote:
> On 26 November 2012 17:41, Ralph Goers wrote:
> > Traceability by who?
> >
> > PMC members can easily verify that what is committed to dist matches what
> > they verified using what they downloaded and the MD5s that came with them.
> > The
On 26 November 2012 17:41, Ralph Goers wrote:
> Traceability by who?
>
> PMC members can easily verify that what is committed to dist matches what
> they verified using what they downloaded and the MD5s that came with them.
> They are the ones responsible for the vote and the artifacts so I don
Traceability by who?
PMC members can easily verify that what is committed to dist matches what they
verified using what they downloaded and the MD5s that came with them. They are
the ones responsible for the vote and the artifacts so I don't see a problem
with that. Why you would need some so
On 26/11/2012 17:23, sebb wrote:
> On 26 November 2012 17:01, Ralph Goers wrote:
>> Actually, if you use the Release plugin the artifacts will be uploaded to
>> the staging repository. At least that is what VFS does. They can be voted
>> on there and then checked into SVN. You can easily verif
On 26 November 2012 17:01, Ralph Goers wrote:
> Actually, if you use the Release plugin the artifacts will be uploaded to the
> staging repository. At least that is what VFS does. They can be voted on
> there and then checked into SVN. You can easily verify they didn't change
> because the MD
Actually, if you use the Release plugin the artifacts will be uploaded to the
staging repository. At least that is what VFS does. They can be voted on there
and then checked into SVN. You can easily verify they didn't change because
the MD5s go along with them.
Ralph
On Nov 26, 2012, at 8:41
On 26 November 2012 11:24, sebb wrote:
> On 26 November 2012 09:53, Emmanuel Bourg wrote:
>> Le 26/11/2012 01:01, sebb a écrit :
>>
>>> Hope this all makes sense!
>>
>> Well, maybe I misunderstood, but committing the RC sites for review into
>> a SVN repository seems a bit convoluted to me. A goo
On 26 November 2012 09:53, Emmanuel Bourg wrote:
> Le 26/11/2012 01:01, sebb a écrit :
>
>> Hope this all makes sense!
>
> Well, maybe I misunderstood, but committing the RC sites for review into
> a SVN repository seems a bit convoluted to me. A good old upload on
> people.apache.org was perfectl
Le 26/11/2012 01:01, sebb a écrit :
> Hope this all makes sense!
Well, maybe I misunderstood, but committing the RC sites for review into
a SVN repository seems a bit convoluted to me. A good old upload on
people.apache.org was perfectly fine.
Emmanuel Bourg
smime.p7s
Description: Signature
As well as moving to svnpubsub for Commons websites, infra require the
use of svn for dist releases - i.e. the non-Maven releases.
I have set up the required top-level SVN folders [1][2], and asked
infra to direct commit messages to commits@commons.a.o so we can keep
track of them.
The dev tree [
13 matches
Mail list logo
