Hehe, I *thought* I was having deja vu... we did already agree to
follow that style, not the httpd one. [1]
Though that was also in the context of milestones, and in the end we
ended up getting all the way to 1.1. Does anyone think we need to
reconsider in light of that, and the issue with the release?
I'm fine with either style. After due consideration, the only thing
I'm not in favour of is releasing/announcing the binaries of the
current 1.1 build since it would cause too much confusion.
Cheers,
Brett
[1] http://markmail.org/message/xijhr4tq5ktfu33z
On 11/07/2008, at 6:24 PM, Arnaud HERITIER wrote:
I'm also against the idea to have a 1.1.1 without 1.1. It was the
coice we
made for the release process (eclipse like vs httpd like)
The only blocker thing I see with the actual 1.1 is the problem to
merge
metadata.
I didn't check if it is fixed but if this was done I'm in favor to
include
it in 1.1
If we don't know when we'll be able to fix it, we continue the
release and
we document the issue.
Arnaud
On Fri, Jul 11, 2008 at 10:15 AM, Emmanuel Venisse <
[EMAIL PROTECTED]> wrote:
Will you rename 1.1.1 to 1.1?
I don't like the idea to release a 1.1.1 without a 1.1 before.
Emmanuel
On Fri, Jul 11, 2008 at 8:13 AM, Wendy Smoak <[EMAIL PROTECTED]>
wrote:
Based on all the discussion, my preference is to cancel the vote,
not
publish 1.1, and just move on with 1.1.1 soon.
I don't want to announce it but then advise people to wait for
1.1.1.
And putting it in the repo/on the mirrors _without_ announcing it
(as
suggested on irc this evening) doesn't make sense to me.
--
Wendy
On Tue, Jul 8, 2008 at 10:39 PM, Maria Odea Ching
<[EMAIL PROTECTED]>
wrote:
Hi Everyone,
Below is a summary of what has been discussed and agreed upon in
the
IRC
earlier today:
1. Still push 1.1 out and release 1.1.1 right after
2. Note the localhost issue in the 1.1 release notes so users are
aware
of
it
3. There are 3 new issues that will be included in 1.1.1, which
are:
- [MRM-870] - addRepositoryToGroup.action =>
AbstractMethodError on
DeferredDocumentImpl.getXmlStandalone()
- [MRM-871] - jetty.host and jetty.port properties are set by
default
in
jetty.xml preventing user from using other hostname if user is not
aware
of
these properties
- [MRM-730] - Index/Search by class, method or package name
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/