incubator-sanselan-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Matthew Chen" <charlesmc...@gmail.com>
Subject Re: Questions
Date Tue, 11 Dec 2007 07:25:25 GMT
I've fixed this Carsten; sorry about that.

Charles.


On Dec 10, 2007 11:17 AM, Carsten Ziegeler <cziegeler@apache.org> wrote:
> Currently, there is one test case failing. I added some initial
> configuration for building the release artifacts.
>
> Carsten
>
>
> Carsten Ziegeler wrote:
> > Charles Matthew Chen wrote:
> >>    Can anyone help me build our first binary and source distributions?
> >>  I think its fairly clear what we want in each distribution.
> >>
> >> Binary:
> >> .jar of the core classes.
> >> javadocs
> >> license info etc.
> >>
> >> Source:
> >> source of all of the classes (including unit tests, example code, etc.)
> >> javadocs
> >> license info etc.
> >>
> >>    I need help with two things:
> >>
> >>    First, there's a number of details mentioned in
> >> http://incubator.apache.org/guides/releasemanagement.html that I don't
> >> understand.  For example, "Check that LICENSE and NOTICE documents
> >> contain required sections."  I'm also unclear on how signing should
> >> work.
> >>
> >>    Secondly, how exactly do we go about releasing these builds?  ie.
> >> do we build locally and upload?  To what server & where?  Or are
> >> release builds generated by an automated build system?
> >>
> > We can use maven to build the distribution, maven is also able to
> > directly sign the release etc. I think we need some additional
> > information in our pom for this (I have to look at the maven docs for this).
> > The release should be signed, so people can download the release and
> > verify the signature.
> >
> > Now, for the process, this is actually a two step process. First, the
> > release is cut which means the corresponding artifacts are created and
> > signed and then put up somewhere (usually projects use people.apache.org
> > for such things) so others can download it and verify if everything is
> > correct. Then a vote has to take place on these uploaded binaries and if
> > the vote is successful, these binaries become the official release and
> > the release is put on the Apache download server. If something is wrong
> > with the artifacts, they're simply deleted, the problems will be fixed
> > and the process is repeated - with a different version number!
> > All of this is a manual process.
> >
> > The LICENSE file should list all used licences throughout the artifact,
> > so in our case this is just the Apache license. The NOTICE files
> > contains references to used projects and lists the origin of the used
> > parts. As we are not using other libraries, again this list only Apache.
> > We have to take care that these files will end up in the distributed
> > artifacts as well.
> >
> > So I think the first step is to get maven build the distributions. I can
> > help with this next week.
> >
> > Carsten
>
>
> --
> Carsten Ziegeler
> cziegeler@apache.org
>

Mime
View raw message