You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2008/08/16 14:52:09 UTC
Re: Click: next steps
I just committed a basic click.xml and refreshed the site (it will
take an hour or so for this to become live).
BTW, we should start using the dev list for the project discussions,
so I am sending the message to the list. Still cc'ing the original
group in case someone's not subscribed.
Cheers,
Andrus
On Aug 14, 2008, at 10:15 PM, Bob Schellink wrote:
> Hi all,
>
> One of the tasks is to create a click.xml status file in the
> incubator site. Can I do this or should
> one of the mentors tackle it? :)
>
> kind regards
>
> bob
Re: Click: next steps
Posted by Andrus Adamchik <an...@objectstyle.org>.
Yeah, SVN migration is the logical next step. Also creating a Jira
instance and migrating the web site.
Regarding the releases. You can do releases from the incubator,
however this requires extra effort. A few things I remember offhand:
* Convert the code to org.apache.click package namespace
* Make sure all the code confirms to the ASF legal requirements (all
CLA's are on files, there's no (L)GPL dependencies, all files have the
license headers, etc.)
* Create NOTICE and LICENSE files.
* Append "-incubating" to all release artifacts
* Vote for the release internally among Click iPMC
* Let Incubator PMC vote for the release.
One possible strategy to minimize the overhead is to maintain a stable
release branch on SourceForge, and develop the new release at Apache.
Not sure if Click implements "bug fix only" code freeze procedure for
the release candidates. If it does, once you fork 1.5 to a stable
branch, this could be a good point to migrate the repo.
Andrus
On Aug 19, 2008, at 12:13 AM, Bob Schellink wrote:
> Andrus Adamchik wrote:
>> I just committed a basic click.xml and refreshed the site (it will
>> take an hour or so for this to become live).
>
> Thanks Andrus.
>
> I assume we should start looking at migrating our svn repository.
> Will we be able to make releases outside
> Apache from the Apache repository? There was some discussion on the
> incubator list about this issue, but
> seemed there are two contradicting opinions on whether this is
> allowed or not.
>
> We are currently preparing for a release candidate and a final
> release soon afterwards. If we cannot make
> releases from Apache's svn, I think we should wait until 1.5 goes
> final.
>
> What do you recommend?
>
> kind regards
>
> bob
>
Re: Click: next steps
Posted by Bob Schellink <sa...@gmail.com>.
Andrus Adamchik wrote:
> I just committed a basic click.xml and refreshed the site (it will
> take an hour or so for this to become live).
Thanks Andrus.
I assume we should start looking at migrating our svn repository. Will
we be able to make releases outside
Apache from the Apache repository? There was some discussion on the
incubator list about this issue, but
seemed there are two contradicting opinions on whether this is allowed
or not.
We are currently preparing for a release candidate and a final release
soon afterwards. If we cannot make
releases from Apache's svn, I think we should wait until 1.5 goes final.
What do you recommend?
kind regards
bob