incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martijn Dashorst" <>
Subject Re: [DISCUSS] Podlings with existing releases and community
Date Thu, 03 Jul 2008 20:06:37 GMT
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


On Thu, Jul 3, 2008 at 9:16 PM, Martijn Dashorst
<> wrote:
> 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 with The Apache Software Foundation.
> I'd propose podlings to adopt this practice as well.
> Martijn
> On Thu, Jul 3, 2008 at 7:42 PM, 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 issue of how to build on their existing communities while
>> they work on doing project management the Apache way, changing package
>> names, voting on releases, updating licenses, and documenting provenance.
>> Most of what I've seen about how to do this is in the mentor guide: "IP
>> Clearance: Initial Clean Up; and On Repackaging". The focus here is on
>> cleaning up the code base. No mention of cutting non-Apache releases from
>> the import part of the repository.
>> I'd like to expand on this a bit. It's very difficult to manage two code
>> bases in two different repositories during a several-month (best case) to
>> years (worst case) incubation period.
>> I'd like to propose explicitly allowing existing communities to continue to
>> develop code in the "import" part of their repository while they are
>> cleaning up their IP, updating licenses, and changing package names.
>> We can document that existing projects with communities may need to have a
>> few releases using the original package names during incubation. While
>> transitioning to releases the Apache way, a podling can release code from
>> the "import" part of their repository. These releases are not incubator
>> releases and do not need to be approved by an Apache PMC.
>> Does anyone see issues with this, before I propose a patch to the guides?
>> Thanks,
>> Craig
>> Craig L Russell
>> Architect, Sun Java Enterprise System
>> 408 276-5638
>> P.S. A good JDO? O, Gasp!
> --
> Become a Wicket expert, learn from the best:
> Apache Wicket 1.3.4 is released
> Get it now:

Become a Wicket expert, learn from the best:
Apache Wicket 1.3.4 is released
Get it now:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message