| clear query|facets|time |
Search criteria: release computer.
Results from 21 to 30 from
643 (0.324s).
|
|
|
Did you mean:
|
|
Loading phrases to help you
refine your search...
|
|
|
No results found for release computer.
|
|
|
Search results for release :
|
|
|
Re: Release? - ManifoldCF - [mail # dev]
|
|
.... *could* obtain. wrote: the need wrote: converted documents to Not however. wiki see wrote: included in the release zip/tar, just that snapshotting and versioning of the wiki should be done...
|
|
... we have explicitly asked for permission on it in the form of patches and then committed by a committer. Since we don't lock down our wiki, we can't do it. get a version/release as well...
|
[+ show more]
[- hide]
| ...? Presumably we want doc for currently supported releases, and the doc can vary between releases. Can we easily snapshot the wiki? whether the person has permission to donate it.. released without... |
| ... a nightly build, but it would be nice to say that we also have a "rolling trunk release" which is just the latest build off trunk and the latest wiki/doc as well. So, some people may want... |
| ... On Nov 19, 2010, at 6:18 AM, Karl Wright wrote: Yep, sorry, have been in meetings. Next steps would be to generate a candidate release which the rest of us can download. Put it up... |
|
|
Author: Grant Ingersoll,
2010-11-19, 13:34
|
|
|
Re: Release? - ManifoldCF - [mail # dev]
|
|
.... wrote: wrote: included in the release zip/tar, just that snapshotting and versioning of the wiki should be done, if feasible, so that a user who is on an older release can still see the doc...
|
|
... and then committed by a committer. Since we don't lock down our wiki, we can't do it. a version/release as well? Presumably we want doc for currently supported releases, and the doc can vary between...
|
[+ show more]
[- hide]
| ... releases. Can we easily snapshot the wiki? whether the person has permission to donate it.. released without a nightly build, but it would be nice to say that we also have a "rolling trunk... |
| ... release" which is just the latest build off trunk and the latest wiki/doc as well. So, some people may want the official 0.1, but others may want to run straight from trunk/nightly build... |
| ... it until the vote passes to save yourself some work. I doubt we need to branch since we won't be releasing bug fixes for a 0.1 release but will instead just point people to 0.2, etc. yes... |
|
|
Author: Grant Ingersoll,
2010-11-19, 13:30
|
|
|
Re: Release? - ManifoldCF - [mail # dev]
|
|
... On Nov 9, 2010, at 1:56 PM, Karl Wright wrote: I think so. This first release is about getting something out there that people can dig into a bit. It also is about laying the legal...
|
|
... groundwork (NOTICE.txt, licenses, etc.) to show that we know how to do releases. -Grant ...
|
|
|
Author: Grant Ingersoll,
2010-11-15, 15:24
|
|
|
Re: Release? - ManifoldCF - [mail # dev]
|
|
... On Nov 15, 2010, at 1:23 PM, Jack Krupansky wrote: in the release zip/tar, just that snapshotting and versioning of the wiki should be done, if feasible, so that a user who...
|
|
... generated content in a release unless we have explicitly asked for permission on it in the form of patches and then committed by a committer. Since we don't lock down our wiki, we can't do it...
|
[+ show more]
[- hide]
| .... version/release as well? Presumably we want doc for currently supported releases, and the doc can vary between releases. Can we easily snapshot the wiki? the person has permission to donate it... |
| ..... without a nightly build, but it would be nice to say that we also have a "rolling trunk release" which is just the latest build off trunk and the latest wiki/doc as well. So, some people may... |
| ... is on an older release can still see the doc for that release. I am just thinking ahead for future releases. So, 0.1 does not need this right now. Right, and I'm saying that we can't include user... |
|
|
Author: Grant Ingersoll,
2010-11-16, 22:36
|
|
|
Re: Release? - ManifoldCF - [mail # dev]
|
|
... snapshot the wiki? You can't put Wiki in a release, as their is no way to track whether the person has permission to donate it.. without a nightly build, but it would be nice to say that we...
|
|
... also have a "rolling trunk release" which is just the latest build off trunk and the latest wiki/doc as well. So, some people may want the official 0.1, but others may want to run straight...
|
[+ show more]
[- hide]
| ... On Nov 10, 2010, at 1:22 AM, Jack Krupansky wrote: version/release as well? Presumably we want doc for currently supported releases, and the doc can vary between releases. Can we easily... |
|
|
Author: Grant Ingersoll,
2010-11-15, 15:23
|
|
|
Signing the release - Lucene - [mail # dev]
|
|
... that you (and anyone else who does Lucene releases) are in the Apache Web of Trust (we can teach you the secret handshake and motto, too! Ha, ha, ha! I'm kidding, it's just Web Of Trust is so...
|
|
|
Author: Grant Ingersoll,
2009-08-27, 23:28
|
|
|
Re: "Book release" - ManifoldCF - [mail # dev]
|
|
...While I understand the dilemma you are in for the book very much, the two are independent events (such is the life of an author). My personal feeling is MCF is not a 1.0 release yet...
|
|
... and that we should just continue on w/ the next release being 0.3. Moreover, a 1.0 release typically means, in my opinion, some important things for a project: 1. maturity in the development...
|
[+ show more]
[- hide]
| ... community, 2. That we are committing to those APIs for the 1.x line and will make backward compatible changes. Are we ready to do that? My instinct also says a 1.0 release is something... |
| ... that should be done by a graduated project and not an incubating one b/c it's generally a policy that incubating projects don't do much PR, etc. and a 1.0 release should be a big deal. (I... |
|
|
Author: Grant Ingersoll,
2011-05-04, 14:40
|
|
|
Brainstorming on Improving the Release Process - Lucene - [mail # dev]
|
|
... of these, then we are not ready to release. 5. Most of the steps in http://wiki.apache.org/lucene-java/ReleaseTodo under the Branching & Feature Freeze section can be automated. Same...
|
|
...(Long post, please bear with me and please read!) Now that we have the release done (I'm working through the publication process now), I want to start the process of thinking about how we...
|
[+ show more]
[- hide]
| ... can improve the release process. As I see it, building the artifacts and checking the legal items are now almost completely automated and testable at earlier stages in the game. We have... |
| ... kept saying we want to release more often, but we have never defined actionable steps with which we can get there. Goals without actionable steps are useless. So, with that in mind, I... |
| ... as opposed to in the past where one person mostly just did the release in the background and then we all voted. So, let's start with what we have right: 1. The Ant process for building a release... |
|
|
Author: Grant Ingersoll,
2011-03-30, 12:22
|
|
|
Re: Next release? - ManifoldCF - [mail # dev]
|
|
...0.2 makes sense. I think we need to figure out how to attract more contribution. It may have been a mistake to have separate user and dev lists at this point in &nbs...
|
|
|
Author: Grant Ingersoll,
2011-03-01, 16:06
|
|
|
Re: 0. release complete - Mahout - [mail # dev]
|
|
...On Oct 31, 2010, at 12:17 PM, Sean Owen wrote: I will do it. Congrats to all on their hard work!...
|
|
|
Author: Grant Ingersoll,
2010-10-31, 21:23
|
|
|
|
|
|
|
