Looks good Jason. I too agree that it should be required to stage
locally and scp to a public location for the vote. I too have had
things accidentally pushed to rsync too soon.
Will the release:rollback and stage:copy remain unchanged? Also, has
this been validated with multiple subproject
I am going to update server/trunk to use Genesis 2.0 shortly. Yes I
will add some new wiki pages, just wanted to get some feedback first.
--jason
On Sep 9, 2008, at 8:12 PM, Donald Woods wrote:
I like the new option to force staging instead of publishing to
apache.releases (which I was bit
I like the new option to force staging instead of publishing to
apache.releases (which I was bit by last week.) Would be nice if the
default was to force staging and require a command line override to
allow publishing to apache.releases (as I think every project to publish
to a staging directory
On Sep 9, 2008, at 1:48 AM, Jason Dillon wrote:
No comments?
Your description sounds great but I won't really know until I try it
out or study it in great detail which I haven't had time for. The
organization looks way better than what we have now.
Can we use the stage plugin to copy f
No comments?
--jason
On Fri, Sep 5, 2008 at 12:53 AM, Jason Dillon <[EMAIL PROTECTED]> wrote:
> Folks, I've been pounding away at Genesis 2.0, in between hospitalization
> and system failures, and I think it is about ready. I'm sending this email
> to inform folks about the state of the sub-pro
Folks, I've been pounding away at Genesis 2.0, in between
hospitalization and system failures, and I think it is about ready.
I'm sending this email to inform folks about the state of the sub-
project as to enlist any suggestions on changes before I go about
documenting it fully.
* * *
