| clear query|facets|time |
Search criteria: release computer.
Results from 81 to 90 from
643 (0.191s).
|
|
|
Did you mean:
|
|
Loading phrases to help you
refine your search...
|
|
|
No results found for release computer.
|
|
|
Search results for release :
|
|
|
Code Freeze, Release Process, etc. - Solr - [mail # dev]
|
|
...OK, so we are in code freeze right now. I'm going to follow the Release process at http://wiki.apache.org/solr/HowToRelease I will put up an RC now, then people can try it out, etc. I...
|
|
... would then like to have a goal of putting up an official set of artifacts to be voted on next Monday. In the interim, we should review docs, etc. and update the wiki where possible. How...
|
|
|
Author: Grant Ingersoll,
2009-10-13, 13:15
|
|
|
Re: pre-release activities - Solr - [mail # dev]
|
|
...I think the Clustering example is up to date, but I'm curious if I missed something. I will double check. On Oct 14, 2009, at 4:43 PM, Yonik Seeley wrote: ...
|
|
|
Author: Grant Ingersoll,
2009-10-15, 18:43
|
|
|
Re: ReleaseTodo steps - Lucene - [mail # dev]
|
|
...On Sep 17, 2009, at 3:07 PM, Mark Miller wrote: They need to be there. ...
|
|
|
Author: Grant Ingersoll,
2009-09-17, 22:14
|
|
|
Re: Release 1.4 - Solr - [mail # dev]
|
|
...I'd also like to get clustering in, SOLR-769. I will have a some time for it after ApacheCon (or, possibly, during) -Grant On Mar 18, 2009, at 3:29 PM, Shalin Shekh...
|
|
|
Author: Grant Ingersoll,
2009-03-20, 11:50
|
|
|
[LUCENE-3000] Lucene release artifacts should be named apache-lucene-* - Lucene - [issue]
|
|
...Our artifact names should be prefixed with apache-, as in apache-lucene-4.0-src.tar.gz (or whatever)...
|
|
|
http://issues.apache.org/jira/browse/LUCENE-3000
Author: Grant Ingersoll,
2012-09-12, 12:50
|
|
|
[MAHOUT-69] 0.1 RELEASE TODO - Mahout - [issue]
|
|
...We need to figure out all the things that need to be done for a 0.1 release.
These include, but are not limited to:
Legal issues (NOTICES.txt, license files, etc.)
Documentation
Wiki...
|
|
... page on making releases (See Lucene or Solr wiki page on said topic)
Release Managers should setup signatures
Remaining issues to be resolved for 0.1. We should go through the issues...
|
[+ show more]
[- hide]
| ... and make decisions by setting the fix version to be 0.1
Others? I've personally never done an Apache release before, so we will want to take our time and make sure things are right.... |
|
|
http://issues.apache.org/jira/browse/MAHOUT-69
Author: Grant Ingersoll,
2011-05-21, 04:24
|
|
|
Re: Think about 0.5 release? - Mahout - [mail # dev]
|
|
...Wow, you read my mind. I was just thinking about this exact thing this morning. On Mar 25, 2011, at 11:12 AM, Sean Owen wrote: +1. I think it would also be good to get a release out...
|
|
|
Author: Grant Ingersoll,
2011-03-25, 15:50
|
|
|
[LUCENE-1154] System Reqs page should be release specific - Lucene - [issue]
|
|
...The System Requirements page, currently under the Main->Resources section of the website should be part of a given version's documentation, since it will be changing for a given release...
|
|
....
I will "deprecate" the existing one, but leave it in place(with a message) to cover the existing releases that don't have this, but will also add it to the release docs for future releases....
|
|
|
http://issues.apache.org/jira/browse/LUCENE-1154
Author: Grant Ingersoll,
2012-05-24, 15:42
|
|
|
Re: [DISCUSSION] Trunk and Stable release strategy - Lucene - [mail # dev]
|
|
... in LUCENE-2720, and the interesting question was "if we say 4.0 is required to read all 3x indexes, how would 4.0 support a future version of 3x, that did not even exist when 4.0 was released". 3...
|
|
....0, but the same issue will arise after we make 4.0 Stable and 5.0 Trunk. propose to the list: we continue to release 3x until we stabilize trunk. When we're happy with trunk, we release it, say 4...
|
[+ show more]
[- hide]
| ....0, and the last 3x release becomes the bug fix release for 3x and from that point we maintain 4.0 (new features and all, while maintaining API back-compat) and Trunk becomes the next big thing (5... |
| ....0). situation where we released 4.0 and then release 3.2, w/ say index format change (that we just had to make). changes whatsoever, we think this proposal makes sense. There's no point maintaining 2... |
|
|
Author: Grant Ingersoll,
2011-01-25, 15:15
|
|
|
Re: [Solr4.0] Release Date - Solr - [mail # user]
|
|
...I think 3.1 will be next, but I don't see a date yet. I would hope sometime soon, but I haven't checked the outstanding issues recently. On Jan 5, 2011, at 11:36 PM, Adam Estrad...
|
|
|
Author: Grant Ingersoll,
2011-01-06, 13:15
|
|
|
|
