>
> I don't understand why ManifoldCF needs this special "skin" processing
> that then needs to live in your svn.
> At Forrest, we advise not to create their own skin unless absolutely
> necessary. We prefer to address any needs in the default skin.
>
> With a quick flick through the ManifoldCF sit
Karl Wright wrote:
> The RAT report after these changes looks good except for two files,
> which come from the skins in the site:
>
> [rat:report] Unapproved licenses:
> [rat:report]
> [rat:report]
> C:/wip/mcf-release/release-0.1-branch/site/src/documentation/skins/common/xslt/html/split.xsl
>
The PhotArk community has completed a vote on it's third milestone
release (PhotArk M3-Incubating) and is now looking for IPMC approval
to publish the release. This release candidate has minimal changes compared
to the previous release candidate and address the license/notice issues
raised on this
The community wanted to include both a source and a source+binary
distribution. Accordingly, I spun up one of those, which is RC5. The
RC4 candidate is still up there, so I guess you can vote on either
one.
Thanks!
Karl
On Fri, Jan 7, 2011 at 11:25 AM, Mattmann, Chris A (388J)
wrote:
> Hi Karl
Hi Karl,
Great job. +1 from me.
SIGS check out:
[chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --verify
apache-manifoldcf-0.1-incubating.tar.gz.asc
gpg: Signature made Fri Jan 7 02:44:17 2011 PST using RSA key ID 03824582
gpg: Good signature from "Karl David Wright (CODE SIGNI
oki that's fine then. Only did read 0.1 and didn't get the suffix.
LieGrue,
stru
--- On Fri, 1/7/11, Karl Wright wrote:
> From: Karl Wright
> Subject: Re: [VOTE] Release Apache ManifoldCF 0.1
> To: general@incubator.apache.org
> Date: Friday, January 7, 2011, 10:14 AM
> The release is numbered
On Thu, Jan 6, 2011 at 3:48 PM, sebb wrote:
> On 6 January 2011 20:29, Karl Wright wrote:
>> The official name of the project has changed repeatedly. The current
>> official name is "ManifoldCF". The community expects to change both
>> the SVN root and the web-site root upon incubation in any c
I have uploaded a new artifact now.
I could call this a release candidate except for the following:
- This artifact has not been voted on by the ManifoldCF community. It
is probably necessary to revote since what is included in the package
has changed (e.g. no build artifacts except for docs).
-
http://incubator.apache.org/guides/releasemanagement.html#naming
Florent
On Fri, Jan 7, 2011 at 11:14 AM, Karl Wright wrote:
> The release is numbered 0.1-incubator right now. I could not find any
> rule that said what the actual format of the release number should be.
> Can you point me to th
Actually 0.1-incubating or 0.1.0-incubating if I'm not mistaken.
Florent
On Fri, Jan 7, 2011 at 10:35 AM, Mark Struberg wrote:
> btw, the release number should not be 0.1 but incubation-0.1 according to the
> Incubator rules.
>
> LieGrue,
> strub
>
> --- On Fri, 1/7/11, David Crossley wrote:
>
The release is numbered 0.1-incubator right now. I could not find any
rule that said what the actual format of the release number should be.
Can you point me to the document that describes this?
Thanks,
Karl
On Fri, Jan 7, 2011 at 4:35 AM, Mark Struberg wrote:
> btw, the release number should
btw, the release number should not be 0.1 but incubation-0.1 according to the
Incubator rules.
LieGrue,
strub
--- On Fri, 1/7/11, David Crossley wrote:
> From: David Crossley
> Subject: Re: [VOTE] Release Apache ManifoldCF 0.1
> To: general@incubator.apache.org
> Date: Friday, January 7, 2011
Karl Wright wrote:
> The ManifoldCF documentation already requires Forrest 0.9-dev. If
> there was a downloadable binary version of 0.9-dev available, I'd be
> willing to consider requiring the user to install it. But that added
> step is just too much, I think, to expect people to do as part of
The ManifoldCF documentation already requires Forrest 0.9-dev. If
there was a downloadable binary version of 0.9-dev available, I'd be
willing to consider requiring the user to install it. But that added
step is just too much, I think, to expect people to do as part of an
initial ManifoldCF setup
14 matches
Mail list logo
