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/01/23 05:12:03 UTC
New non-Apache Sanselan release
Hi all,
I've released a new non-Apache build (0.88) of Sanselan. It's
available here:
http://fightingquaker.com/sanselan/
It reflects the current state of the repo (though it is missing the
unit tests, test image suite, etc.). The package hierarchy in this
release has been changed to not use org.apache.*
The concise release notes are:
>>>
Version 0.88 released January 22nd, 2008.
* Added EXIF insert/update/remove functionality. See
WriteExifMetadataExample.java for examples.
* Rewrote JPEG and TIFF parsing.
* Greatly elaborated the unit test suite and test image suite. In
the process found and resolved many bugs.
* Once again, I hope this is the last non-apache release. =)
>>>
This project - Exif insert/update/remove - turned out to be much
more involved than I initially thought. I ended up rewriting a great
deal of the Tiff/Jpeg/Exif related code in the process of doing it.
On the last point, I wonder what we can do to reach the point of
our first apache build. I saw the following message on the
incubator's general mailing list a few weeks ago. Would it be a good
idea to enlist Robert's help?
Charles.
---------- Forwarded message ----------
From: "Robert Burrell Donkin" <ro...@gmail.com>
To: general@incubator.apache.org
Date: Wed, 2 Jan 2008 22:51:23 +0000
Subject: Re: Uploading Releases to apache.org/dist/incubator
On Jan 2, 2008 10:26 PM, Frank Barnaby <Fr...@sun.com> wrote:
>
> Hi folks,
hi frank
> I've found some information regarding the need to distribute incubating
> releases through www.apache.org/dist/incubator/podling-name
> (ie, people.apache.org:/www/www.apache.org/dist/incubator/podling-name)
> and have read a readme in the dist/incubator directory, which states
> that
> I should consult this mailing list before populating the dist area.
yep - i created that document
policy is now that official releases issued by the incubator need to
be distributed through the standard apache distribution mechanism
the documentation is still being worked on ATM so i've volunteered to
walk anyone who wants to release though the process
if i'm right in assuming that this is river-related, let's hop back
onto river-dev (i'm subscribing now). if not, please jump in
- robert
Re: New non-Apache Sanselan release
Posted by Carsten Ziegeler <cz...@apache.org>.
Charles Matthew Chen wrote:
> On reflection, I think we should make the test data separate from
> the unit tests. Not all of the unit tests use the test data.
> Moreover, the test data is quite large (and will hopefully continue to
> grow).
>
I'm not exactly sure what you mean by separating?
I hope to make a test run for building a release sometime next week, so
we can all have a look and see which things are missing/need to change
in terms of a distribution.
Carsten
> Charles.
>
> On Jan 26, 2008 1:35 AM, Charles Matthew Chen <ch...@gmail.com> wrote:
>> +1 to both points.
>>
>> thanks,
>> charles.
>>
>>
>>
>> On Jan 25, 2008 1:58 PM, Craig L Russell <Cr...@sun.com> wrote:
>>> On Jan 25, 2008, at 9:48 AM, Carsten Ziegeler wrote:
>>>
>>>> Hi,
>>>>
>>>> as we are using maven to build sanselan, we get this for free; the
>>>> only extra work we have to do later on is to put the maven artifact
>>>> (the jar and the pom) into the maven repository (but that's fairly
>>>> simple).
>>> +1
>>>>
>>>> For the download distribution I don't think we should add the wiki
>>>> docs itself as this might give us some legal headaches right now -
>>>> everyone who wrote something on the wiki needs to have a signed CLA
>>>> on file *if* we include this in our releases. I think a link to the
>>>> wiki is enough - at least for a first step.
>>> RIght. I don't see a need to put wiki content into the releases.
>>>
>>> Craig
>>>
>>>>
>>>> Regards
>>>> Carsten
>>>>
>>>> Craig L Russell wrote:
>>>>> Hi Charles,
>>>>> On Jan 24, 2008, at 9:32 PM, Charles Matthew Chen wrote:
>>>>>> Hi Craig,
>>>>>>
>>>>>> I'm not really familiar with that option. Can you elaborate or
>>>>>> perhaps share a url?
>>>>> http://maven.apache.org is the starting point for information. I've
>>>>> been using maven for a while now and it's very popular among open
>>>>> source projects. In order to use sanselan in a project, all you
>>>>> need to do is to include a few lines of code in an xml file and
>>>>> you're done. Maven will download the jar file and include it in
>>>>> your build and run environments.
>>>>> For example, to use sanselan in another project, you'd declare this
>>>>> in your configuration file:
>>>>> <dependency>
>>>>> <groupId>org.apache.sanselan</groupId>
>>>>> <artifactId>sanselan</artifactId>
>>>>> <version>1.0.0-SNAPSHOT</version>
>>>>> </dependency>
>>>>>>
>>>>>> What trade-offs do we face in this decision?
>>>>> It's just a bit more work setting up the publication of the jar
>>>>> file in the maven repository. All the usual due diligence is still
>>>>> required to prepare the jar file for publication.
>>>>
>>>> --
>>>> Carsten Ziegeler
>>>> cziegeler@apache.org
>>>
>>> Craig 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!
>>>
>>>
>
--
Carsten Ziegeler
cziegeler@apache.org
Re: New non-Apache Sanselan release
Posted by Charles Matthew Chen <ch...@gmail.com>.
On reflection, I think we should make the test data separate from
the unit tests. Not all of the unit tests use the test data.
Moreover, the test data is quite large (and will hopefully continue to
grow).
Charles.
On Jan 26, 2008 1:35 AM, Charles Matthew Chen <ch...@gmail.com> wrote:
> +1 to both points.
>
> thanks,
> charles.
>
>
>
> On Jan 25, 2008 1:58 PM, Craig L Russell <Cr...@sun.com> wrote:
> >
> > On Jan 25, 2008, at 9:48 AM, Carsten Ziegeler wrote:
> >
> > > Hi,
> > >
> > > as we are using maven to build sanselan, we get this for free; the
> > > only extra work we have to do later on is to put the maven artifact
> > > (the jar and the pom) into the maven repository (but that's fairly
> > > simple).
> >
> > +1
> > >
> > >
> > > For the download distribution I don't think we should add the wiki
> > > docs itself as this might give us some legal headaches right now -
> > > everyone who wrote something on the wiki needs to have a signed CLA
> > > on file *if* we include this in our releases. I think a link to the
> > > wiki is enough - at least for a first step.
> >
> > RIght. I don't see a need to put wiki content into the releases.
> >
> > Craig
> >
> > >
> > >
> > > Regards
> > > Carsten
> > >
> > > Craig L Russell wrote:
> > >> Hi Charles,
> > >> On Jan 24, 2008, at 9:32 PM, Charles Matthew Chen wrote:
> > >>> Hi Craig,
> > >>>
> > >>> I'm not really familiar with that option. Can you elaborate or
> > >>> perhaps share a url?
> > >> http://maven.apache.org is the starting point for information. I've
> > >> been using maven for a while now and it's very popular among open
> > >> source projects. In order to use sanselan in a project, all you
> > >> need to do is to include a few lines of code in an xml file and
> > >> you're done. Maven will download the jar file and include it in
> > >> your build and run environments.
> > >> For example, to use sanselan in another project, you'd declare this
> > >> in your configuration file:
> > >> <dependency>
> > >> <groupId>org.apache.sanselan</groupId>
> > >> <artifactId>sanselan</artifactId>
> > >> <version>1.0.0-SNAPSHOT</version>
> > >> </dependency>
> > >>>
> > >>>
> > >>> What trade-offs do we face in this decision?
> > >> It's just a bit more work setting up the publication of the jar
> > >> file in the maven repository. All the usual due diligence is still
> > >> required to prepare the jar file for publication.
> > >
> > >
> > > --
> > > Carsten Ziegeler
> > > cziegeler@apache.org
> >
> >
> > Craig 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: New non-Apache Sanselan release
Posted by Charles Matthew Chen <ch...@gmail.com>.
+1 to both points.
thanks,
charles.
On Jan 25, 2008 1:58 PM, Craig L Russell <Cr...@sun.com> wrote:
>
> On Jan 25, 2008, at 9:48 AM, Carsten Ziegeler wrote:
>
> > Hi,
> >
> > as we are using maven to build sanselan, we get this for free; the
> > only extra work we have to do later on is to put the maven artifact
> > (the jar and the pom) into the maven repository (but that's fairly
> > simple).
>
> +1
> >
> >
> > For the download distribution I don't think we should add the wiki
> > docs itself as this might give us some legal headaches right now -
> > everyone who wrote something on the wiki needs to have a signed CLA
> > on file *if* we include this in our releases. I think a link to the
> > wiki is enough - at least for a first step.
>
> RIght. I don't see a need to put wiki content into the releases.
>
> Craig
>
> >
> >
> > Regards
> > Carsten
> >
> > Craig L Russell wrote:
> >> Hi Charles,
> >> On Jan 24, 2008, at 9:32 PM, Charles Matthew Chen wrote:
> >>> Hi Craig,
> >>>
> >>> I'm not really familiar with that option. Can you elaborate or
> >>> perhaps share a url?
> >> http://maven.apache.org is the starting point for information. I've
> >> been using maven for a while now and it's very popular among open
> >> source projects. In order to use sanselan in a project, all you
> >> need to do is to include a few lines of code in an xml file and
> >> you're done. Maven will download the jar file and include it in
> >> your build and run environments.
> >> For example, to use sanselan in another project, you'd declare this
> >> in your configuration file:
> >> <dependency>
> >> <groupId>org.apache.sanselan</groupId>
> >> <artifactId>sanselan</artifactId>
> >> <version>1.0.0-SNAPSHOT</version>
> >> </dependency>
> >>>
> >>>
> >>> What trade-offs do we face in this decision?
> >> It's just a bit more work setting up the publication of the jar
> >> file in the maven repository. All the usual due diligence is still
> >> required to prepare the jar file for publication.
> >
> >
> > --
> > Carsten Ziegeler
> > cziegeler@apache.org
>
>
> Craig 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: New non-Apache Sanselan release
Posted by Craig L Russell <Cr...@Sun.COM>.
On Jan 25, 2008, at 9:48 AM, Carsten Ziegeler wrote:
> Hi,
>
> as we are using maven to build sanselan, we get this for free; the
> only extra work we have to do later on is to put the maven artifact
> (the jar and the pom) into the maven repository (but that's fairly
> simple).
+1
>
>
> For the download distribution I don't think we should add the wiki
> docs itself as this might give us some legal headaches right now -
> everyone who wrote something on the wiki needs to have a signed CLA
> on file *if* we include this in our releases. I think a link to the
> wiki is enough - at least for a first step.
RIght. I don't see a need to put wiki content into the releases.
Craig
>
>
> Regards
> Carsten
>
> Craig L Russell wrote:
>> Hi Charles,
>> On Jan 24, 2008, at 9:32 PM, Charles Matthew Chen wrote:
>>> Hi Craig,
>>>
>>> I'm not really familiar with that option. Can you elaborate or
>>> perhaps share a url?
>> http://maven.apache.org is the starting point for information. I've
>> been using maven for a while now and it's very popular among open
>> source projects. In order to use sanselan in a project, all you
>> need to do is to include a few lines of code in an xml file and
>> you're done. Maven will download the jar file and include it in
>> your build and run environments.
>> For example, to use sanselan in another project, you'd declare this
>> in your configuration file:
>> <dependency>
>> <groupId>org.apache.sanselan</groupId>
>> <artifactId>sanselan</artifactId>
>> <version>1.0.0-SNAPSHOT</version>
>> </dependency>
>>>
>>>
>>> What trade-offs do we face in this decision?
>> It's just a bit more work setting up the publication of the jar
>> file in the maven repository. All the usual due diligence is still
>> required to prepare the jar file for publication.
>
>
> --
> Carsten Ziegeler
> cziegeler@apache.org
Craig 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: New non-Apache Sanselan release
Posted by Carsten Ziegeler <cz...@apache.org>.
Hi,
as we are using maven to build sanselan, we get this for free; the only
extra work we have to do later on is to put the maven artifact (the jar
and the pom) into the maven repository (but that's fairly simple).
For the download distribution I don't think we should add the wiki docs
itself as this might give us some legal headaches right now - everyone
who wrote something on the wiki needs to have a signed CLA on file *if*
we include this in our releases. I think a link to the wiki is enough -
at least for a first step.
Regards
Carsten
Craig L Russell wrote:
> Hi Charles,
>
> On Jan 24, 2008, at 9:32 PM, Charles Matthew Chen wrote:
>
>> Hi Craig,
>>
>> I'm not really familiar with that option. Can you elaborate or
>> perhaps share a url?
>
> http://maven.apache.org is the starting point for information. I've been
> using maven for a while now and it's very popular among open source
> projects. In order to use sanselan in a project, all you need to do is
> to include a few lines of code in an xml file and you're done. Maven
> will download the jar file and include it in your build and run
> environments.
>
> For example, to use sanselan in another project, you'd declare this in
> your configuration file:
>
> <dependency>
> <groupId>org.apache.sanselan</groupId>
> <artifactId>sanselan</artifactId>
> <version>1.0.0-SNAPSHOT</version>
> </dependency>
>
>>
>>
>> What trade-offs do we face in this decision?
>
> It's just a bit more work setting up the publication of the jar file in
> the maven repository. All the usual due diligence is still required to
> prepare the jar file for publication.
>
--
Carsten Ziegeler
cziegeler@apache.org
Re: New non-Apache Sanselan release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Charles,
On Jan 24, 2008, at 9:32 PM, Charles Matthew Chen wrote:
> Hi Craig,
>
> I'm not really familiar with that option. Can you elaborate or
> perhaps share a url?
http://maven.apache.org is the starting point for information. I've
been using maven for a while now and it's very popular among open
source projects. In order to use sanselan in a project, all you need
to do is to include a few lines of code in an xml file and you're
done. Maven will download the jar file and include it in your build
and run environments.
For example, to use sanselan in another project, you'd declare this in
your configuration file:
<dependency>
<groupId>org.apache.sanselan</groupId>
<artifactId>sanselan</artifactId>
<version>1.0.0-SNAPSHOT</version>
</dependency>
>
>
> What trade-offs do we face in this decision?
It's just a bit more work setting up the publication of the jar file
in the maven repository. All the usual due diligence is still required
to prepare the jar file for publication.
Best,
Craig
>
>
> Charles.
>
>
> On Jan 24, 2008 8:19 PM, Craig L Russell <Cr...@sun.com>
> wrote:
>> Hi Charles,
>>
>> Does it make sense to ship the binary release as a maven artifact?
>>
>> This would be useful (mostly) if users wrote code and wanted to
>> automatically include it in their programs. It would be suitable if
>> the primary release artifact is "just a jar with a bunch of java
>> classes and legal notices (meta-inf) in it".
>>
>> Craig
>>
>>
>> On Jan 23, 2008, at 11:15 PM, Charles Matthew Chen wrote:
>>
>>> Hi Craig,
>>>
>>> It seems like our needs are fairly ordinary. Like most projects, I
>>> think we would do well to produce "source" and "binary" releases.
>>>
>>> The binary release would include a .jar file with the core classes
>>> (no unit tests or test data), the javadocs and basic files such as
>>> the
>>> license, changelist, a snapshot of the wiki docs (or at least a
>>> reference to them), etc. The .jar file wouldn't neccessarily have
>>> to
>>> be signed, or packaged in a particular way.
>>>
>>> The source release would include all of the sources files (core and
>>> test), the test data, the javadocs, and the basic files. It would
>>> include nearly everything in the repo. I'm not sure what it
>>> wouldn't
>>> include.
>>>
>>> The binary and source releases would be available as both .zip and
>>> .tar.gz archives.
>>>
>>> Charles.
>>>
>>>
>>>
>>> On Jan 23, 2008 1:04 AM, Craig L Russell <Cr...@sun.com>
>>> wrote:
>>>> Hi Charles,
>>>>
>>>>
>>>> On Jan 22, 2008, at 9:12 PM, Charles Matthew Chen wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I've released a new non-Apache build (0.88) of Sanselan. It's
>>>>> available here:
>>>>>
>>>>> http://fightingquaker.com/sanselan/
>>>> ...
>>>>>
>>>>> On the last point, I wonder what we can do to reach the point of
>>>>> our first apache build. I saw the following message on the
>>>>> incubator's general mailing list a few weeks ago. Would it be a
>>>>> good
>>>>> idea to enlist Robert's help?
>>>>
>>>> What Robert is discussing here is where to post the release
>>>> artifacts.
>>>>
>>>> Before we get there, we need to make sure we're ready to release
>>>> something.
>>>>
>>>> Let's start with this: What do we release? How do we package it?
>>>>
>>>> Craig
>>>>>
>>>>>
>>>>> Charles.
>>>>>
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: "Robert Burrell Donkin" <ro...@gmail.com>
>>>>> To: general@incubator.apache.org
>>>>> Date: Wed, 2 Jan 2008 22:51:23 +0000
>>>>> Subject: Re: Uploading Releases to apache.org/dist/incubator
>>>>> On Jan 2, 2008 10:26 PM, Frank Barnaby <Fr...@sun.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi folks,
>>>>>
>>>>> hi frank
>>>>>
>>>>>> I've found some information regarding the need to distribute
>>>>>> incubating
>>>>>> releases through www.apache.org/dist/incubator/podling-name
>>>>>> (ie, people.apache.org:/www/www.apache.org/dist/incubator/podling-name)
>>>>>> and have read a readme in the dist/incubator directory, which
>>>>>> states
>>>>>> that
>>>>>> I should consult this mailing list before populating the dist
>>>>>> area.
>>>>>
>>>>> yep - i created that document
>>>>>
>>>>> policy is now that official releases issued by the incubator
>>>>> need to
>>>>> be distributed through the standard apache distribution mechanism
>>>>>
>>>>> the documentation is still being worked on ATM so i've volunteered
>>>>> to
>>>>> walk anyone who wants to release though the process
>>>>>
>>>>> if i'm right in assuming that this is river-related, let's hop
>>>>> back
>>>>> onto river-dev (i'm subscribing now). if not, please jump in
>>>>>
>>>>> - robert
>>>>
>>>> Craig 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 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 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: New non-Apache Sanselan release
Posted by Charles Matthew Chen <ch...@gmail.com>.
Hi Craig,
I'm not really familiar with that option. Can you elaborate or
perhaps share a url?
What trade-offs do we face in this decision?
Charles.
On Jan 24, 2008 8:19 PM, Craig L Russell <Cr...@sun.com> wrote:
> Hi Charles,
>
> Does it make sense to ship the binary release as a maven artifact?
>
> This would be useful (mostly) if users wrote code and wanted to
> automatically include it in their programs. It would be suitable if
> the primary release artifact is "just a jar with a bunch of java
> classes and legal notices (meta-inf) in it".
>
> Craig
>
>
> On Jan 23, 2008, at 11:15 PM, Charles Matthew Chen wrote:
>
> > Hi Craig,
> >
> > It seems like our needs are fairly ordinary. Like most projects, I
> > think we would do well to produce "source" and "binary" releases.
> >
> > The binary release would include a .jar file with the core classes
> > (no unit tests or test data), the javadocs and basic files such as the
> > license, changelist, a snapshot of the wiki docs (or at least a
> > reference to them), etc. The .jar file wouldn't neccessarily have to
> > be signed, or packaged in a particular way.
> >
> > The source release would include all of the sources files (core and
> > test), the test data, the javadocs, and the basic files. It would
> > include nearly everything in the repo. I'm not sure what it wouldn't
> > include.
> >
> > The binary and source releases would be available as both .zip and
> > .tar.gz archives.
> >
> > Charles.
> >
> >
> >
> > On Jan 23, 2008 1:04 AM, Craig L Russell <Cr...@sun.com>
> > wrote:
> >> Hi Charles,
> >>
> >>
> >> On Jan 22, 2008, at 9:12 PM, Charles Matthew Chen wrote:
> >>
> >>> Hi all,
> >>>
> >>> I've released a new non-Apache build (0.88) of Sanselan. It's
> >>> available here:
> >>>
> >>> http://fightingquaker.com/sanselan/
> >> ...
> >>>
> >>> On the last point, I wonder what we can do to reach the point of
> >>> our first apache build. I saw the following message on the
> >>> incubator's general mailing list a few weeks ago. Would it be a
> >>> good
> >>> idea to enlist Robert's help?
> >>
> >> What Robert is discussing here is where to post the release
> >> artifacts.
> >>
> >> Before we get there, we need to make sure we're ready to release
> >> something.
> >>
> >> Let's start with this: What do we release? How do we package it?
> >>
> >> Craig
> >>>
> >>>
> >>> Charles.
> >>>
> >>>
> >>> ---------- Forwarded message ----------
> >>> From: "Robert Burrell Donkin" <ro...@gmail.com>
> >>> To: general@incubator.apache.org
> >>> Date: Wed, 2 Jan 2008 22:51:23 +0000
> >>> Subject: Re: Uploading Releases to apache.org/dist/incubator
> >>> On Jan 2, 2008 10:26 PM, Frank Barnaby <Fr...@sun.com>
> >>> wrote:
> >>>>
> >>>> Hi folks,
> >>>
> >>> hi frank
> >>>
> >>>> I've found some information regarding the need to distribute
> >>>> incubating
> >>>> releases through www.apache.org/dist/incubator/podling-name
> >>>> (ie, people.apache.org:/www/www.apache.org/dist/incubator/podling-name)
> >>>> and have read a readme in the dist/incubator directory, which
> >>>> states
> >>>> that
> >>>> I should consult this mailing list before populating the dist area.
> >>>
> >>> yep - i created that document
> >>>
> >>> policy is now that official releases issued by the incubator need to
> >>> be distributed through the standard apache distribution mechanism
> >>>
> >>> the documentation is still being worked on ATM so i've volunteered
> >>> to
> >>> walk anyone who wants to release though the process
> >>>
> >>> if i'm right in assuming that this is river-related, let's hop back
> >>> onto river-dev (i'm subscribing now). if not, please jump in
> >>>
> >>> - robert
> >>
> >> Craig 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 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: New non-Apache Sanselan release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Charles,
Does it make sense to ship the binary release as a maven artifact?
This would be useful (mostly) if users wrote code and wanted to
automatically include it in their programs. It would be suitable if
the primary release artifact is "just a jar with a bunch of java
classes and legal notices (meta-inf) in it".
Craig
On Jan 23, 2008, at 11:15 PM, Charles Matthew Chen wrote:
> Hi Craig,
>
> It seems like our needs are fairly ordinary. Like most projects, I
> think we would do well to produce "source" and "binary" releases.
>
> The binary release would include a .jar file with the core classes
> (no unit tests or test data), the javadocs and basic files such as the
> license, changelist, a snapshot of the wiki docs (or at least a
> reference to them), etc. The .jar file wouldn't neccessarily have to
> be signed, or packaged in a particular way.
>
> The source release would include all of the sources files (core and
> test), the test data, the javadocs, and the basic files. It would
> include nearly everything in the repo. I'm not sure what it wouldn't
> include.
>
> The binary and source releases would be available as both .zip and
> .tar.gz archives.
>
> Charles.
>
>
>
> On Jan 23, 2008 1:04 AM, Craig L Russell <Cr...@sun.com>
> wrote:
>> Hi Charles,
>>
>>
>> On Jan 22, 2008, at 9:12 PM, Charles Matthew Chen wrote:
>>
>>> Hi all,
>>>
>>> I've released a new non-Apache build (0.88) of Sanselan. It's
>>> available here:
>>>
>>> http://fightingquaker.com/sanselan/
>> ...
>>>
>>> On the last point, I wonder what we can do to reach the point of
>>> our first apache build. I saw the following message on the
>>> incubator's general mailing list a few weeks ago. Would it be a
>>> good
>>> idea to enlist Robert's help?
>>
>> What Robert is discussing here is where to post the release
>> artifacts.
>>
>> Before we get there, we need to make sure we're ready to release
>> something.
>>
>> Let's start with this: What do we release? How do we package it?
>>
>> Craig
>>>
>>>
>>> Charles.
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: "Robert Burrell Donkin" <ro...@gmail.com>
>>> To: general@incubator.apache.org
>>> Date: Wed, 2 Jan 2008 22:51:23 +0000
>>> Subject: Re: Uploading Releases to apache.org/dist/incubator
>>> On Jan 2, 2008 10:26 PM, Frank Barnaby <Fr...@sun.com>
>>> wrote:
>>>>
>>>> Hi folks,
>>>
>>> hi frank
>>>
>>>> I've found some information regarding the need to distribute
>>>> incubating
>>>> releases through www.apache.org/dist/incubator/podling-name
>>>> (ie, people.apache.org:/www/www.apache.org/dist/incubator/podling-name)
>>>> and have read a readme in the dist/incubator directory, which
>>>> states
>>>> that
>>>> I should consult this mailing list before populating the dist area.
>>>
>>> yep - i created that document
>>>
>>> policy is now that official releases issued by the incubator need to
>>> be distributed through the standard apache distribution mechanism
>>>
>>> the documentation is still being worked on ATM so i've volunteered
>>> to
>>> walk anyone who wants to release though the process
>>>
>>> if i'm right in assuming that this is river-related, let's hop back
>>> onto river-dev (i'm subscribing now). if not, please jump in
>>>
>>> - robert
>>
>> Craig 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 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: New non-Apache Sanselan release
Posted by Charles Matthew Chen <ch...@gmail.com>.
Hi Craig,
It seems like our needs are fairly ordinary. Like most projects, I
think we would do well to produce "source" and "binary" releases.
The binary release would include a .jar file with the core classes
(no unit tests or test data), the javadocs and basic files such as the
license, changelist, a snapshot of the wiki docs (or at least a
reference to them), etc. The .jar file wouldn't neccessarily have to
be signed, or packaged in a particular way.
The source release would include all of the sources files (core and
test), the test data, the javadocs, and the basic files. It would
include nearly everything in the repo. I'm not sure what it wouldn't
include.
The binary and source releases would be available as both .zip and
.tar.gz archives.
Charles.
On Jan 23, 2008 1:04 AM, Craig L Russell <Cr...@sun.com> wrote:
> Hi Charles,
>
>
> On Jan 22, 2008, at 9:12 PM, Charles Matthew Chen wrote:
>
> > Hi all,
> >
> > I've released a new non-Apache build (0.88) of Sanselan. It's
> > available here:
> >
> > http://fightingquaker.com/sanselan/
> ...
> >
> > On the last point, I wonder what we can do to reach the point of
> > our first apache build. I saw the following message on the
> > incubator's general mailing list a few weeks ago. Would it be a good
> > idea to enlist Robert's help?
>
> What Robert is discussing here is where to post the release artifacts.
>
> Before we get there, we need to make sure we're ready to release
> something.
>
> Let's start with this: What do we release? How do we package it?
>
> Craig
> >
> >
> > Charles.
> >
> >
> > ---------- Forwarded message ----------
> > From: "Robert Burrell Donkin" <ro...@gmail.com>
> > To: general@incubator.apache.org
> > Date: Wed, 2 Jan 2008 22:51:23 +0000
> > Subject: Re: Uploading Releases to apache.org/dist/incubator
> > On Jan 2, 2008 10:26 PM, Frank Barnaby <Fr...@sun.com> wrote:
> >>
> >> Hi folks,
> >
> > hi frank
> >
> >> I've found some information regarding the need to distribute
> >> incubating
> >> releases through www.apache.org/dist/incubator/podling-name
> >> (ie, people.apache.org:/www/www.apache.org/dist/incubator/podling-name)
> >> and have read a readme in the dist/incubator directory, which states
> >> that
> >> I should consult this mailing list before populating the dist area.
> >
> > yep - i created that document
> >
> > policy is now that official releases issued by the incubator need to
> > be distributed through the standard apache distribution mechanism
> >
> > the documentation is still being worked on ATM so i've volunteered to
> > walk anyone who wants to release though the process
> >
> > if i'm right in assuming that this is river-related, let's hop back
> > onto river-dev (i'm subscribing now). if not, please jump in
> >
> > - robert
>
> Craig 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: New non-Apache Sanselan release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Charles,
On Jan 22, 2008, at 9:12 PM, Charles Matthew Chen wrote:
> Hi all,
>
> I've released a new non-Apache build (0.88) of Sanselan. It's
> available here:
>
> http://fightingquaker.com/sanselan/
...
>
> On the last point, I wonder what we can do to reach the point of
> our first apache build. I saw the following message on the
> incubator's general mailing list a few weeks ago. Would it be a good
> idea to enlist Robert's help?
What Robert is discussing here is where to post the release artifacts.
Before we get there, we need to make sure we're ready to release
something.
Let's start with this: What do we release? How do we package it?
Craig
>
>
> Charles.
>
>
> ---------- Forwarded message ----------
> From: "Robert Burrell Donkin" <ro...@gmail.com>
> To: general@incubator.apache.org
> Date: Wed, 2 Jan 2008 22:51:23 +0000
> Subject: Re: Uploading Releases to apache.org/dist/incubator
> On Jan 2, 2008 10:26 PM, Frank Barnaby <Fr...@sun.com> wrote:
>>
>> Hi folks,
>
> hi frank
>
>> I've found some information regarding the need to distribute
>> incubating
>> releases through www.apache.org/dist/incubator/podling-name
>> (ie, people.apache.org:/www/www.apache.org/dist/incubator/podling-name)
>> and have read a readme in the dist/incubator directory, which states
>> that
>> I should consult this mailing list before populating the dist area.
>
> yep - i created that document
>
> policy is now that official releases issued by the incubator need to
> be distributed through the standard apache distribution mechanism
>
> the documentation is still being worked on ATM so i've volunteered to
> walk anyone who wants to release though the process
>
> if i'm right in assuming that this is river-related, let's hop back
> onto river-dev (i'm subscribing now). if not, please jump in
>
> - robert
Craig 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!