On Fri, Feb 7, 2014 at 3:02 AM, Stephen Connolly
wrote:
> So the second issue is what a PMC member is required to do before voting...
>
> As a PMC member you are required to
>
> 1. Download the source code package
> 2. Compile it as provided
> 3. Test the resulting executable on your own platform
On Fri, Feb 7, 2014 at 11:33 AM, Stephen Connolly
wrote:
> I checked and I think my very original post is reply to dev... Somebody on
> the board list pulled it back in I suspect.
I didn't get my diagnosis quite right.
The copy delivered to dev@community.apache has the following headers:
To
Keeping this in public.
We VOTE and review precisely to minimize and catch the IP mistakes that
inevitably happen when people are examining the IP from time to time. The
community will care about quality, but minding the IP protects us all.
RAT check, detailed review and 3 +1 where those involv
Hi Guys,
I'm sorry if I missed this, but how can I help review the ApacheCon
talks related to Science and OODT/etc.? I would be very happy to do
help.
Thanks and let me know.
Cheers,
Chris
I checked and I think my very original post is reply to dev... Somebody on
the board list pulled it back in I suspect.
On Friday, 7 February 2014, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hmm not sure how that happened, board and the "friend" project's private
> list were supp
Hmm not sure how that happened, board and the "friend" project's private
list were supposed to be BCC only... Arse!
On Friday, 7 February 2014, Marvin Humphrey wrote:
> Hi folks,
>
> This is an important topic, and when I have more time later I hope to
> join in the fun. But for now I'd like to
Hi folks,
This is an important topic, and when I have more time later I hope to
join in the fun. But for now I'd like to point out that the replies
in the kickoff post on dev@community.apache are set to go to
board@apache, which is going to make this thread into a real mess of
public and private
On Fri, Feb 7, 2014 at 12:35 PM, Alex Harui wrote:
> IMO, a more important question is: Does it fit within the "Apache Way" of
> "Community over Code" to have a project release on a particular schedule?
> Because it feels to me that if you have a release cadence then you are saying
> "Clock ove
IMO, a more important question is: Does it fit within the "Apache Way" of
"Community over Code" to have a project release on a particular schedule?
Because it feels to me that if you have a release cadence then you are saying
"Clock over Community".
I get that having a schedule helps many in
To be clear, I am not sure if Maven wants such a rapid release cycle...
after all we have been supposed to release 3.2.0 since Oct 1st 2013... and
it's still not ready... The other way of looking at it is that if we did
have a 1 release every 7 days we'd probably have 3.2.0 out already!
There are
Hi Stephen, @all
I'm not involved in the Maven development, but I enjoy writing plug-ins for
Jenkins.
From a plug-in developer point of view, whenever a developer needs a change
in the Jenkins core, s/he knows that once there is a fix/pull request
for his issue, it will get released probably
On 7 February 2014 11:02, Stephen Connolly
wrote:
> One of the projects I am involved with is the Jenkins project. At Jenkins
> we cut a release of Jenkins every wednesday... assuming the test all pass...
> Not every release is as stable as people might desire (the tests don't
> catch everything),
One of the projects I am involved with is the Jenkins project. At Jenkins
we cut a release of Jenkins every wednesday... assuming the test all pass...
Not every release is as stable as people might desire (the tests don't
catch everything), hence there is the LTS release line, but none the less,
th
13 matches
Mail list logo
