BTW: this is not just cover our ass, but also promotes the idea that
the podling is in incubation, destined to become an Apache project. It
may attract more folks, it will also show that the project is
supportive of old releases, making it feel like a more mature
community.
Martijn
On Thu, Jul 3,
On Thu, Jul 3, 2008 at 9:16 PM, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
> ...There is just one extra thing we did and that
> was add a disclaimer to the release notes that the project was
> currently incubating at apache and that the release was not endorsed
> by, nor associated in any way with
This is the practice established during Wicket's incubation and it
helped us considerably. There is just one extra thing we did and that
was add a disclaimer to the release notes that the project was
currently incubating at apache and that the release was not endorsed
by, nor associated in any way
+1
I think this is good, as it codifies an existing practice.
/Janne
On 3 Jul 2008, at 20:42, Craig L Russell wrote:
Hi,
Many projects that come to Apache already have existing releases.
Some are still beta but others have already shipped a few
production versions.
This raises the iss
Hi,
Many projects that come to Apache already have existing releases. Some
are still beta but others have already shipped a few production
versions.
This raises the issue of how to build on their existing communities
while they work on doing project management the Apache way, changing
p
