: This prompts the question (in my mind anyway): should source releases include
third-party binary jars?
if i remember correctly, the historical argument has been that this way
the source release contains everything you need to compile the source.
except that if i remember correctly (and i'm v
Sounds like a good idea.
Robert Muir wrote:
> collation could be made smaller, it probably uses entire icu4j jar,
> which includes large data pieces unnecessary for collation
>
> it this sounds like a good idea i will create a smaller one with the below
> link:
>
> http://apps.icu-project.org/dat
Hi Mark,
On 8/29/2009 at 4:24 PM, Mark Miller wrote:
> It looks like 2.9 will be a much larger release. The 2.4.1 src dist I
> have is 5.9MB zipped - the 2.9 version is 15.3 MB zipped.
[snip]
> collation 0 -> 5.5
The source code under collation is much smaller than 5.5MB - this must mostly
be
collation could be made smaller, it probably uses entire icu4j jar,
which includes large data pieces unnecessary for collation
it this sounds like a good idea i will create a smaller one with the below link:
http://apps.icu-project.org/datacustom/
On Thu, Aug 27, 2009 at 4:23 PM, Mark Miller wro
It looks like 2.9 will be a much larger release. The 2.4.1 src dist I
have is 5.9MB zipped - the 2.9 version is 15.3 MB zipped.
It all looks legit to me though. I'll post a list of the biggest changes
so someone can flag if they think something is off. It appears legit to
me though:
src dist 2.4.
Mark Miller wrote:
> I'm tempted to say lets start the freeze tomorrow instead - I could do
> another full day of doc/packaging no problem I think (a bunch left to do
> on the website stuff alone) - and technically the releaseToDo wants
> everything to go through a patch in JIRA first while in free
I'm tempted to say lets start the freeze tomorrow instead - I could do
another full day of doc/packaging no problem I think (a bunch left to do
on the website stuff alone) - and technically the releaseToDo wants
everything to go through a patch in JIRA first while in freeze (not a
bad idea at all)
+1
So cut the branch at the end of the freeze.
Mike
On Tue, Aug 25, 2009 at 4:18 PM, Mark Miller wrote:
> I still think we should wait to branch the trunk until after the week.
> Its easy enough to work in JIRA with patches for that brief period if
> someone really wants to get going. But if we
I still think we should wait to branch the trunk until after the week.
Its easy enough to work in JIRA with patches for that brief period if
someone really wants to get going. But if we just start switching
everything to Java 1.5 and removing deprecated API's, its going to be a
real pain patching b
Mark Miller wrote:
> bq. Though we have 9 2.9 issues now...
>
> Right - we are kind of contingent on that - most look near done though,
> and some are documentation.
In fact, the number 9 is very misleading:
LUCENE-1798FieldCacheSanityChecker called directly by FieldCache.get*
looks about d
I don't look at it as just the week really. We got to 0 issues last
week, and these new issues have all really been cleanup and and bug
fixes. We have been in quasi feature freeze really. A lot of the issues
that are being addressed would have made sense to address over the
normal feature freeze. I
bq. Though we have 9 2.9 issues now...
Right - we are kind of contingent on that - most look near done though,
and some are documentation. I'd be happy to plow mindless work into
anything someone doesn't think they can finish soon if thats an issue.
bq. At the end of the freeze you'd create the r
Hmm, I wondering if one week is rather short considering the amount of
new features we have in 2.9 and the frequency of new issues coming in at
the moment...
Michael
On 8/24/09 2:20 PM, Michael McCandless wrote:
I like freezing for 1 week starting Wed. We should fix the javadocs&
any bugs d
I like freezing for 1 week starting Wed. We should fix the javadocs &
any bugs during this time. Though we have 9 2.9 issues now...
At the end of the freeze you'd create the release candidate(s)?
Mike
On Mon, Aug 24, 2009 at 9:51 AM, Mark Miller wrote:
> I know there is still some discussion a
I know there is still some discussion about the 2.9 release, so things
could change -
but I think its a good idea to start discussion on a schedule anyway.
I'll throw out to start:
Feature freeze Wednesday (Aug 26th) - we already are kind of in feature
freeze, but this would make it official.
Le
15 matches
Mail list logo
