Le 4/01/2017 à 15:19, sebb a écrit :
> Likewise if the common site wanted to use a subdirectory with the same
> name as a component.
> Both 'resources' and 'email' are potentially useful as common subdirs.
>
> There are lots of potential clashes if the name spaces are merged, so
> why run the ris
On 4 January 2017 at 13:16, Emmanuel Bourg wrote:
> Le 4/01/2017 à 12:58, sebb a écrit :
>
>> That was done originally, but then the same name space is used for
>> common pages as for component names.
>>
>> e.g. there could not be common pages called resources.html and email.html.
>
> Why not? An
Le 4/01/2017 à 12:58, sebb a écrit :
> That was done originally, but then the same name space is used for
> common pages as for component names.
>
> e.g. there could not be common pages called resources.html and email.html.
Why not? An email.html file could co-exist with an email/ directory
cont
On 4 January 2017 at 08:30, Emmanuel Bourg wrote:
> Le 4/01/2017 à 01:27, sebb a écrit :
>> Where do pre-release components appear on the website?
>
> I'd suggest flattening the layout of the site and putting all components
> at the same level (proper, sandbox, dormant):
>
> http://commons.apach
Le 4/01/2017 à 01:44, Gilles a écrit :
> Alternative would be that any committer is allowed to ask INFRA
> to create a git repository. Is it that which you advocate for?
Assuming there is a consensus to do so, yes. But if a committer just
wants to play alone in a corner he can do it on GitHub, no
Le 4/01/2017 à 01:27, sebb a écrit :
> Where do pre-release components appear on the website?
I'd suggest flattening the layout of the site and putting all components
at the same level (proper, sandbox, dormant):
http://commons.apache.org/foo/
http://commons.apache.org/bar/
instead of:
ht
On Wed, 4 Jan 2017 00:40:43 +0100, Emmanuel Bourg wrote:
IMHO this concept of promoting components from the sandbox to proper
looks a bit obsolete (any Apache committer has access to our
repositories now)
I don't see any relationship.
AFAIK, the "sandbox" was a place where developers could "pl
Where do pre-release components appear on the website?
On 3 January 2017 at 23:40, Emmanuel Bourg wrote:
> IMHO this concept of promoting components from the sandbox to proper
> looks a bit obsolete (any Apache committer has access to our
> repositories now) and it just makes the introduction of
IMHO this concept of promoting components from the sandbox to proper
looks a bit obsolete (any Apache committer has access to our
repositories now) and it just makes the introduction of new components
more complicated.
We could consider that any unreleased component is in a "sandbox" state,
and it
> On Jan 3, 2017, at 9:48 AM, Stefan Bodewig wrote:
>
> On 2017-01-03, Rob Tompkins wrote:
>
>>> On Jan 3, 2017, at 8:57 AM, Stefan Bodewig wrote:
>
On 2017-01-03, Rob Tompkins wrote:
>
As a relative novice to the Apache/Apache Commons sandboxing process,
I figure that it migh
On 2017-01-03, Rob Tompkins wrote:
>> On Jan 3, 2017, at 8:57 AM, Stefan Bodewig wrote:
>>> On 2017-01-03, Rob Tompkins wrote:
>>> As a relative novice to the Apache/Apache Commons sandboxing process,
>>> I figure that it might be prudent to ask what the process is for
>>> moving a component ou
Am 03.01.2017 um 15:11 schrieb Rob Tompkins:
>
>
>> On Jan 3, 2017, at 8:57 AM, Stefan Bodewig wrote:
>>
>>> On 2017-01-03, Rob Tompkins wrote:
>>>
>>> As a relative novice to the Apache/Apache Commons sandboxing process,
>>> I figure that it might be prudent to ask what the process is for
>>>
> On Jan 3, 2017, at 8:57 AM, Stefan Bodewig wrote:
>
>> On 2017-01-03, Rob Tompkins wrote:
>>
>> As a relative novice to the Apache/Apache Commons sandboxing process,
>> I figure that it might be prudent to ask what the process is for
>> moving a component out of the sandbox, before I attempt
On 2017-01-03, Rob Tompkins wrote:
> As a relative novice to the Apache/Apache Commons sandboxing process,
> I figure that it might be prudent to ask what the process is for
> moving a component out of the sandbox, before I attempt a release on
> TEXT. So, I was wondering if someone could point me
Hello all,
As a relative novice to the Apache/Apache Commons sandboxing process, I figure
that it might be prudent to ask what the process is for moving a component out
of the sandbox, before I attempt a release on TEXT. So, I was wondering if
someone could point me in the direction of the docu
15 matches
Mail list logo
