Rahul Akolkar wrote:
On 6/24/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Rahul Akolkar wrote:
> On 6/23/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
>> On 6/23/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
>> > <snip/>
>> >
>> > I haven't yet understood why we need to release anything from the
>> > sandbox at all. Sure, reproducibility is a good thing, but I
doubt the
>> > builds are radically irreproducible without this release; and more
>> > importantly, I believe if people are interested in the sandbox
>> > components and their reproducibility, they should help get a release
>> > out instead.
>> >
>>
>> I think you have a good point there, Rahul, but I would see this as a
>> commons release, not a commons-sandbox release and I personally see
>> the benefit (consistent builds, easier to get a sandbox component to
>> build when jumping in) as outweighing the negatives (increasing
>> likelihood people depend on sandbox components, making the sandbox
>> more "comfortable"), especially given that we are *not* releasing any
>> sandbox jars.
>>
> <snip/>
>
> I appreciate you taking the time to elaborate. I am not impressed by
> any of these benefits (I'm not trying to be curt, I don't know how
> else to put it). Moreover, I agree about the negatives.
So what are the negatives here? I have not seen anyone put forward any
arguments yet as to why releasing the sandbox parent pom would be bad.
We are *not* talking about releasing sandbox components! Please,
enlighten me.
<snip/>
See line below, and less importantly, some comments above.
> I see this as being distilled, and worse -- recurring, busy work.
Well, Carlos asked for a release of the pom. I imagine that he has a
good reason for this.
<snap/>
imagine? I can only go by reasons stated in this thread (Carlos' and
Phil's subsequent posts do not have a new reason IMO).
Here is the message that made me start this thread.
http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/200706.mbox/[EMAIL
PROTECTED]
Apparently he is working on commons CSV, so if releasing this pom can
help him do that then it's a Good Thing TM. It might even help CSV to
get promoted out of the sandbox.
So I stepped up to do the release. If I don't mind
doing the job - why should you care?
<snap/>
Because this is a Commons release.
Because (as a more general statement beyond the ASF workings) I
believe that merely having someone available to do something, does not
by itself, make doing that thing worthwhile.
Because (in terms of the ASF workings) do-ocracies do not imply that
others should not care about what you are doing when its about
releasing artifacts.
You misread my previous comment. I was not talking about *what* is being
done, but *who* is doing it. You said that releasing the sandbox pom
will require work, meaning someone has to do it. I then said that I'll
do it. Can we just leave it at that.
If we focus on *what* is being done instead. Can you tell me what is
wrong with releasing the sandbox parent? Besides the fact that it
requires someone has to do the actual work.
Because we will have to:
* Release periodically
Not necessarily. The consensus when we started with Maven 2 poms was
that we try to keep the parent(s) stable. Try something out in a
component first and it's deemed good for all, then we'll move it to the
parent. In my opinion the parent defines the common build process that
all components should use. And that should not change that often.
- Needs process cycles: RMs, votes (thanks for your cycles on this one)
Like I said I'm volunteering to be RM for this release. If you don't
have the cycles to check the release, you are perfectly entitled to
refrain from voting.
- Who knows how often this will have to happen (lesser the better)
Agreed.
* Update all sandbox component POMs to keep parent versions in sync etc.
Again this doesn't have to be a lot of work. Once we get the first
release of the sandbox pom out, it is necessary to update the poms of
all sandbox components at least once. Again I'm volunteering here.
I vote:
-0 (non-binding)
-Rahul
--
Dennis Lundberg
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
