Mailing-List: contact dev-help@shale.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shale.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <459B99CE.1070908@erols.com>
Date: Wed, 03 Jan 2007 06:55:58 -0500
From: Gregg Leichtman <gsl1@erols.com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060725)
MIME-Version: 1.0
To: dev@shale.apache.org
Subject: Re: [FWD: [v1.0.4] shale-tiles and release notes (was Re: svn commit:
 r490857 ...)]
References: 
 <20061228160613.3eb95c3cf77b2348806009e1dbac435b.12088d99db.wbe@email.secureserver.net>
	 <91478db0612290732x79344539q1a66999bd9f45a71@mail.gmail.com>
 <ce1f2ea80612290844w248dee54q51de84c5f1422976@mail.gmail.com>
In-Reply-To: <ce1f2ea80612290844w248dee54q51de84c5f1422976@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig5032A9DB07C10D3387066748"

--------------enig5032A9DB07C10D3387066748
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Just a suggestion. It would be helpful, to me at least, if you were to
include within the release notes one or more snapshot version numbers of
standalone Tiles, one or more version numbers of Spring and one or more
version numbers of other targeted components that work with Shale with
which you the development group believes v1.0.4 appears to work. I
realize that items like Tiles in sandboxes are fast moving targets, but
it helps us users avoid having to do a lot of trial and error just to
find a single combination of components that works. If we have one
working set, substituting different components one at a time using trial
and error during component upgrades is far less burdensome that not
knowing anything about what works together.

                                                              -=3D> Gregg=
 <=3D-

Rahul Akolkar wrote:
> On 12/29/06, Greg Reddin <greddin@apache.org> wrote:
>> > > From: "Rahul Akolkar" <rahul.akolkar@gmail.com>
>> > > Date: Thu, December 28, 2006 4:56 pm
>> > > To: commits@shale.apache.org
>> > >
>> > > The above "projected quality" paragraph needs to be updated to
>> reflect
>> > > the current sentiment. Of the two items in that list, 1.0.4 will
>> > > address most of the dialog issues (so I've removed that).
>> > >
>> > > Someone more familiar with shale-tiles (and changes implied by goi=
ng
>> > > TLP) should update the above paragraph in the release notes. TIA.
>>
>>
>>
>> The TLP hasn't changed the status of Tiles just yet.  Tiles will
>> still be a
>> snapshot for a while because it will take some time to get the TLP
>> infrastructure set up.
>>
> <snip/>
>
> Thanks, the related bits are in section 1 and 4 of the release notes
> -- you're welcome (as is everyone else) to tweak the wording (long,
> possibly fragmented URL):
>
> http://svn.apache.org/repos/asf/shale/framework/trunk/src/site/resource=
s/docs/release-notes-1.0.4.html
>
>
> -Rahul
>
>
>> Greg
>>
>>
>


--------------enig5032A9DB07C10D3387066748
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFFm5nTMcSsEtbyA2cRAo6XAJsHhPpXzPSshs/YHHK3gSUn8dwfiQCfbbUP
GqZwOiDoRRfxamVbIIJ1BzI=
=lA5m
-----END PGP SIGNATURE-----

--------------enig5032A9DB07C10D3387066748--