You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sanselan-dev@incubator.apache.org by Charles Matthew Chen <ch...@gmail.com> on 2008/07/14 21:02:26 UTC
Release
What's the next step in getting our initial release approved?
Should the builds be posted somewhere?
Charles.
Re: Release
Posted by Carsten Ziegeler <cz...@apache.org>.
Craig L Russell wrote:
> Hi Charles,
>
> I'd say it's ready for a vote, following the incubator guides for releases.
>
> It would be good to post the results of the RAT run or include it as an
> attachment to the vote message.
>
> Also take a look at the layout of the directory under dist. If the idea
> is to copy your dist to www.apache.org/dist, you would have a directory
> incubator/sanselan into which you would copy the 0.93 directory.
>
> And there are lots of extra .md5 and .sha1 files (there's no need to
> checksum signatures) that are probably the result of the maven plugin
> being overly aggressive. They can be removed before, during, or after
> the voting starts.
>
> Most Apache distributions consist of .zip and .tar.gz with the
> associated checksums and signatures. You might want to explain why you
> feel the bz2 format is needed.
>
That's by default generated by maven as well. I think we can just remove it.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Charles,
I'd say it's ready for a vote, following the incubator guides for
releases.
It would be good to post the results of the RAT run or include it as
an attachment to the vote message.
Also take a look at the layout of the directory under dist. If the
idea is to copy your dist to www.apache.org/dist, you would have a
directory incubator/sanselan into which you would copy the 0.93
directory.
And there are lots of extra .md5 and .sha1 files (there's no need to
checksum signatures) that are probably the result of the maven plugin
being overly aggressive. They can be removed before, during, or after
the voting starts.
Most Apache distributions consist of .zip and .tar.gz with the
associated checksums and signatures. You might want to explain why you
feel the bz2 format is needed.
Craig
On Jul 19, 2008, at 1:44 AM, Charles Matthew Chen wrote:
> What's the next step in the release process - is the proposed
> release ready to be voted on? It is here:
>
> http://people.apache.org/~cmchen/dist/
>
> Thanks,
> Charles.
>
>
> On Fri, Jul 18, 2008 at 9:15 AM, Charles Matthew Chen
> <ch...@gmail.com> wrote:
>> Hi Craig,
>>
>> RAT was a good idea - it found 6 classes missing the Apache License
>> header. I've produced a new build (0.93-incubator) at the same
>> location:
>>
>> http://people.apache.org/~cmchen/dist/
>>
>> Charles.
>>
>>
>>
>> On Thu, Jul 17, 2008 at 4:20 PM, Craig L Russell <Craig.Russell@sun.com
>> > wrote:
>>> Hi Charles,
>>>
>>> RAT is incubating at Apache but it's available in binary form from
>>> http://code.google.com/p/arat/
>>>
>>> It's pretty easy to install and run on an unzipped release.
>>>
>>> Craig
>>>
>>> On Jul 17, 2008, at 1:56 AM, Charles Matthew Chen wrote:
>>>
>>>> I don't see a binary release for RAT at:
>>>>
>>>> http://incubator.apache.org/rat/
>>>> http://www.apache.org/dist/incubator/
>>>>
>>>> Charles.
>>>
>>> Craig L Russell
>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>>>
>>
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Release
Posted by Charles Matthew Chen <ch...@gmail.com>.
What's the next step in the release process - is the proposed
release ready to be voted on? It is here:
http://people.apache.org/~cmchen/dist/
Thanks,
Charles.
On Fri, Jul 18, 2008 at 9:15 AM, Charles Matthew Chen
<ch...@gmail.com> wrote:
> Hi Craig,
>
> RAT was a good idea - it found 6 classes missing the Apache License
> header. I've produced a new build (0.93-incubator) at the same
> location:
>
> http://people.apache.org/~cmchen/dist/
>
> Charles.
>
>
>
> On Thu, Jul 17, 2008 at 4:20 PM, Craig L Russell <Cr...@sun.com> wrote:
>> Hi Charles,
>>
>> RAT is incubating at Apache but it's available in binary form from
>> http://code.google.com/p/arat/
>>
>> It's pretty easy to install and run on an unzipped release.
>>
>> Craig
>>
>> On Jul 17, 2008, at 1:56 AM, Charles Matthew Chen wrote:
>>
>>> I don't see a binary release for RAT at:
>>>
>>> http://incubator.apache.org/rat/
>>> http://www.apache.org/dist/incubator/
>>>
>>> Charles.
>>
>> Craig L Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>
Re: Release
Posted by Charles Matthew Chen <ch...@gmail.com>.
Hi Craig,
RAT was a good idea - it found 6 classes missing the Apache License
header. I've produced a new build (0.93-incubator) at the same
location:
http://people.apache.org/~cmchen/dist/
Charles.
On Thu, Jul 17, 2008 at 4:20 PM, Craig L Russell <Cr...@sun.com> wrote:
> Hi Charles,
>
> RAT is incubating at Apache but it's available in binary form from
> http://code.google.com/p/arat/
>
> It's pretty easy to install and run on an unzipped release.
>
> Craig
>
> On Jul 17, 2008, at 1:56 AM, Charles Matthew Chen wrote:
>
>> I don't see a binary release for RAT at:
>>
>> http://incubator.apache.org/rat/
>> http://www.apache.org/dist/incubator/
>>
>> Charles.
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
Re: Release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Charles,
RAT is incubating at Apache but it's available in binary form from http://code.google.com/p/arat/
It's pretty easy to install and run on an unzipped release.
Craig
On Jul 17, 2008, at 1:56 AM, Charles Matthew Chen wrote:
> I don't see a binary release for RAT at:
>
> http://incubator.apache.org/rat/
> http://www.apache.org/dist/incubator/
>
> Charles.
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Release
Posted by Charles Matthew Chen <ch...@gmail.com>.
Hi Craig,
I've made a public_html dir as you suggested:
http://people.apache.org/~cmchen/
> What I did was to create a dist directory that upon successful voting, gets
> copied directly into the incubator/dist directory. So whatever is in dist
> should exactly match incubator/dist.
Your suggestion sounds good. This raises the question of how our
releases should be organized inside dist? This seems to vary slightly
by project. ie. jdo and wicket have a separate dir for each release:
http://www.apache.org/dist/db/jdo/2.0/
http://www.apache.org/dist/wicket/1.4-m3/
Felix puts everything in one folder:
http://www.apache.org/dist/felix/
Maven separates binary and source releases:
http://www.apache.org/dist/maven/binaries/
http://www.apache.org/dist/maven/source/
Shall we follow the jdo appraoch? Presumably we will use:
http://www.apache.org/dist/incubator/sanselan
So, I've moved the release and a copy of KEYS into:
http://people.apache.org/~cmchen/dist/0.92-incubator/
With the intention that it would end up here:
http://www.apache.org/dist/incubator/sanselan/0.92-incubator/
Also, where should the maven-metadata.xml be placed?
> You should run RAT on the distribution artifacts to make sure that the
> LICENSE, NOTICE, etc. files are all ok.
I don't see a binary release for RAT at:
http://incubator.apache.org/rat/
http://www.apache.org/dist/incubator/
Charles.
> I wasn't able to access http://people.apache.org/~cmchen to look at your
> distribution. You might need to make a public directory public_html and put
> the distribution into it.
>
> You can look at how I've set up my personal directory as an example.
> http://people.apache.org/~clr/
>
> What I did was to create a dist directory that upon successful voting, gets
> copied directly into the incubator/dist directory. So whatever is in dist
> should exactly match incubator/dist.
>
> You should run RAT on the distribution artifacts to make sure that the
> LICENSE, NOTICE, etc. files are all ok.
>>
>>
>> ie.:
>>
>>
>> ~/org/apache/sanselan/sanselan/0.92-incubator/sanselan-0.92-incubator-bin.zip
>>
>> Shall we start up the voting? Is there anything obviously wrong
>> with this build?
>>
>> My first thought is about the source package. Craig said:
>>
>> On Tue, Jul 8, 2008 at 10:42 PM, Craig L Russell <Cr...@sun.com>
>> wrote:
>>>
>>> This project could have a single source distribution (.zip) and a single
>>> binary distribution (.jar).
>>>
>>> The source distro could be simply a zip of the source tree (rooted at
>>> trunk).
>>>
>>> The binary distro could be the result of building the .jar file and
>>> making
>>> sure that the appropriate LICENSE and NOTICE files are included when
>>> building it.
>>
>> The source distro in this build includes the tests and the test
>> resources (ie. the test image suite). This will make the source
>> distro much, much larger. Should we offer a no-test version of the
>> source distro?
>
> I'd lean toward making the source distribution be runnable (including tests)
> immediately after download, so I'd say "yes, include test images".
>
> Good start.
>
> Craig
>>
>>
>> Charles
>>
>>
>> On Tue, Jul 15, 2008 at 9:23 AM, Carsten Ziegeler <cz...@apache.org>
>> wrote:
>>>
>>> Charles Matthew Chen wrote:
>>>>
>>>> What's the next step in getting our initial release approved?
>>>> Should the builds be posted somewhere?
>>>>
>>> Yes, the first steps are detailed at the Felix project:
>>> http://felix.apache.org/site/release-management.html
>>>
>>> We can follow the steps including starting the vote. Once the vote is
>>> finished, we need to get additional permission from the incubator pmc.
>>> After this second vote, hopefully successful, is finished, we can
>>> continue
>>> with uploading the release to the appropriate incubator directories.
>>>
>>> So, the first step is: creating the release, tagging, signing and putting
>>> it
>>> up for review.
>>>
>>> Carsten
>>>
>>> --
>>> Carsten Ziegeler
>>> cziegeler@apache.org
>>>
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
Re: Release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Charles,
On Jul 16, 2008, at 3:42 PM, Charles Matthew Chen wrote:
> Okay, I've worked my way through the first portion of the Felix
> release management process.
>
>> http://felix.apache.org/site/release-management.html
>
> I've reached this step:
>
> """
> Upload these files to people.apache.org into your home folder and put
> them there together with the KEYS file containing your public key so
> we can verify the signatures.
> """
>
> I've uploaded my KEYS file and the output of the maven release
> build to my account (~cmchen) on people.apache.org. I kept the folder
> structure of the output, so most of the files are in:
>
> ~/org/apache/sanselan/sanselan/0.92-incubator/
I wasn't able to access http://people.apache.org/~cmchen to look at
your distribution. You might need to make a public directory
public_html and put the distribution into it.
You can look at how I've set up my personal directory as an example. http://people.apache.org/~clr/
What I did was to create a dist directory that upon successful voting,
gets copied directly into the incubator/dist directory. So whatever is
in dist should exactly match incubator/dist.
You should run RAT on the distribution artifacts to make sure that the
LICENSE, NOTICE, etc. files are all ok.
>
>
> ie.:
>
> ~/org/apache/sanselan/sanselan/0.92-incubator/sanselan-0.92-
> incubator-bin.zip
>
> Shall we start up the voting? Is there anything obviously wrong
> with this build?
>
> My first thought is about the source package. Craig said:
>
> On Tue, Jul 8, 2008 at 10:42 PM, Craig L Russell <Craig.Russell@sun.com
> > wrote:
>> This project could have a single source distribution (.zip) and a
>> single
>> binary distribution (.jar).
>>
>> The source distro could be simply a zip of the source tree (rooted at
>> trunk).
>>
>> The binary distro could be the result of building the .jar file and
>> making
>> sure that the appropriate LICENSE and NOTICE files are included when
>> building it.
>
> The source distro in this build includes the tests and the test
> resources (ie. the test image suite). This will make the source
> distro much, much larger. Should we offer a no-test version of the
> source distro?
I'd lean toward making the source distribution be runnable (including
tests) immediately after download, so I'd say "yes, include test
images".
Good start.
Craig
>
>
> Charles
>
>
> On Tue, Jul 15, 2008 at 9:23 AM, Carsten Ziegeler <cziegeler@apache.org
> > wrote:
>> Charles Matthew Chen wrote:
>>>
>>> What's the next step in getting our initial release approved?
>>> Should the builds be posted somewhere?
>>>
>> Yes, the first steps are detailed at the Felix project:
>> http://felix.apache.org/site/release-management.html
>>
>> We can follow the steps including starting the vote. Once the vote is
>> finished, we need to get additional permission from the incubator
>> pmc.
>> After this second vote, hopefully successful, is finished, we can
>> continue
>> with uploading the release to the appropriate incubator directories.
>>
>> So, the first step is: creating the release, tagging, signing and
>> putting it
>> up for review.
>>
>> Carsten
>>
>> --
>> Carsten Ziegeler
>> cziegeler@apache.org
>>
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Release
Posted by Charles Matthew Chen <ch...@gmail.com>.
Okay, I've worked my way through the first portion of the Felix
release management process.
> http://felix.apache.org/site/release-management.html
I've reached this step:
"""
Upload these files to people.apache.org into your home folder and put
them there together with the KEYS file containing your public key so
we can verify the signatures.
"""
I've uploaded my KEYS file and the output of the maven release
build to my account (~cmchen) on people.apache.org. I kept the folder
structure of the output, so most of the files are in:
~/org/apache/sanselan/sanselan/0.92-incubator/
ie.:
~/org/apache/sanselan/sanselan/0.92-incubator/sanselan-0.92-incubator-bin.zip
Shall we start up the voting? Is there anything obviously wrong
with this build?
My first thought is about the source package. Craig said:
On Tue, Jul 8, 2008 at 10:42 PM, Craig L Russell <Cr...@sun.com> wrote:
> This project could have a single source distribution (.zip) and a single
> binary distribution (.jar).
>
> The source distro could be simply a zip of the source tree (rooted at
> trunk).
>
> The binary distro could be the result of building the .jar file and making
> sure that the appropriate LICENSE and NOTICE files are included when
> building it.
The source distro in this build includes the tests and the test
resources (ie. the test image suite). This will make the source
distro much, much larger. Should we offer a no-test version of the
source distro?
Charles
On Tue, Jul 15, 2008 at 9:23 AM, Carsten Ziegeler <cz...@apache.org> wrote:
> Charles Matthew Chen wrote:
>>
>> What's the next step in getting our initial release approved?
>> Should the builds be posted somewhere?
>>
> Yes, the first steps are detailed at the Felix project:
> http://felix.apache.org/site/release-management.html
>
> We can follow the steps including starting the vote. Once the vote is
> finished, we need to get additional permission from the incubator pmc.
> After this second vote, hopefully successful, is finished, we can continue
> with uploading the release to the appropriate incubator directories.
>
> So, the first step is: creating the release, tagging, signing and putting it
> up for review.
>
> Carsten
>
> --
> Carsten Ziegeler
> cziegeler@apache.org
>
Re: Release
Posted by Carsten Ziegeler <cz...@apache.org>.
Charles Matthew Chen wrote:
> What's the next step in getting our initial release approved?
> Should the builds be posted somewhere?
>
Yes, the first steps are detailed at the Felix project:
http://felix.apache.org/site/release-management.html
We can follow the steps including starting the vote. Once the vote is
finished, we need to get additional permission from the incubator pmc.
After this second vote, hopefully successful, is finished, we can
continue with uploading the release to the appropriate incubator
directories.
So, the first step is: creating the release, tagging, signing and
putting it up for review.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org