On Wed, Aug 8, 2012 at 5:18 AM, Bertrand Delacretaz
wrote:
> On Thu, Jul 26, 2012 at 4:10 PM, Jukka Zitting
> wrote:
>
>> ...I'd like to start fixing this by forming a "release task force" of a
>> handful of volunteers who are ready to invest an hour or two per week
>> to work onb) migrating
On Thu, Jul 26, 2012 at 4:10 PM, Jukka Zitting wrote:
> ...I'd like to start fixing this by forming a "release task force" of a
> handful of volunteers who are ready to invest an hour or two per week
> to work onb) migrating
> /dist/incubator to svnpubsub by the end of this year...
I'm inter
Hi,
For people interested in working on this, the ongoing Bloodhound
release vote has triggered some good discussion that would be great to
capture somehow.
BR,
Jukka Zitting
-
To unsubscribe, e-mail: general-unsubscr...@incuba
Jukka Zitting wrote on Fri, Jul 27, 2012 at 10:38:56 +0300:
> The existing Incubator release guide [1] is a noble effort, but I
> think it went wrong in trying to explain everything (even the table of
> contents is TL;DR, and parts of the page are already outdated) instead
> of just pointing to mor
Hi,
On Fri, Jul 27, 2012 at 1:07 AM, Joe Schaefer wrote:
> It sucks for the same old tired rationale behind excluding competent
> peer reviewers from the halls of power here. Some of us think this
> is a core failing of the IPMC, others disagree. If Jukka can satisfy
> the anti-progressives and
>From a mobile device - forgive errors and terseness
On Jul 26, 2012 11:07 PM, "Joe Schaefer" wrote:
>
> >
> > From: Upayavira
> >To: general@incubator.apache.org
> >Sent: Thursday, July 26, 2012 5:37 PM
> >Subject:
Hi,
On Fri, Jul 27, 2012 at 1:44 AM, Joe Schaefer wrote:
> I'm sure I speak for Marvin when I say I would love to participate on a task
> force dedicated to producing such documentation, but I am also weary about
> writing about a whole bunch of hypotheticals that nobody (other than Roy)
> has a
On Thu, Jul 26, 2012 at 9:49 AM, Ross Gardler
wrote:
> For those interested in helping the documentation side of this you
> might find the task oriented documenation that the Rave project
> developed during incubation useful. This has already been successfully
> adopted by at least two other podli
- Original Message -
> From: Dave Fisher
> To: general@incubator.apache.org
> Cc:
> Sent: Thursday, July 26, 2012 6:33 PM
> Subject: Re: Incubator release task force
>
>
> On Jul 26, 2012, at 3:07 PM, Joe Schaefer wrote:
>
>>> _
On Jul 26, 2012, at 3:07 PM, Joe Schaefer wrote:
>>
>> From: Upayavira
>> To: general@incubator.apache.org
>> Sent: Thursday, July 26, 2012 5:37 PM
>> Subject: Re: Incubator release task force
>>
>> Marvin,
>>
>
> From: Upayavira
>To: general@incubator.apache.org
>Sent: Thursday, July 26, 2012 5:37 PM
>Subject: Re: Incubator release task force
>
>Marvin,
>
>While I (think I) can understand your concern (that it should be the
>mentors who a
On Thu, Jul 26, 2012 at 5:37 PM, Upayavira wrote:
> Marvin,
>
> While I (think I) can understand your concern (that it should be the
> mentors who are reviewing releases, not yet another group), I'd suggest
> that Jukka's approach might be a way to get there.
>
> The incubator release process is,
Marvin,
While I (think I) can understand your concern (that it should be the
mentors who are reviewing releases, not yet another group), I'd suggest
that Jukka's approach might be a way to get there.
The incubator release process is, at the moment, pretty fraught, and I
suspect there are only a h
Hi Gary...
On Thu, Jul 26, 2012 at 6:20 PM, Gary Martin wrote:
> As someone who is currently attempting to go through their first release,
> I am not really in the category of someone who could be in such a
> taskforce. However, I am very interested in seeing an improvement in the
> release docum
Great idea.
For those interested in helping the documentation side of this you
might find the task oriented documenation that the Rave project
developed during incubation useful. This has already been successfully
adopted by at least two other podlings.
Of course it is project and build tool spec
As someone who is currently attempting to go through their first
release, I am not really in the category of someone who could be in such
a taskforce. However, I am very interested in seeing an improvement in
the release documentation. I would certainly consider looking back over
my recent expe
Ditto.
>
> From: Marvin Humphrey
>To: general@incubator.apache.org
>Sent: Thursday, July 26, 2012 11:48 AM
>Subject: Re: Incubator release task force
>
>On Thu, Jul 26, 2012 at 7:10 AM, Jukka Zitting wrote:
>
>> For example, ou
On Thu, Jul 26, 2012 at 7:10 AM, Jukka Zitting wrote:
> For example, our current release guide [1] is the result
> of quite a bit of work, but without a clear vision accompanied with a
> process of incremental improvements it's become a mess that few people
> read, let alone understand.
I am int
I like the idea, but I suggest to do it in a different way:
Why not to have volunteers who are already mentoring different podlings
with different sizes of both number of people and the size of code base,
these mentors then volunteer:
1- Update the release process docs
2- Report their their exper
Hi,
The Incubator ships about half a dozen releases each month on average,
but our release process is notoriously lengthy, fraught with problems,
and badly documented. If this was any other project, we'd have had a
well-oiled release process in place already years ago.
Much of our extra release o
20 matches
Mail list logo
