On 21/04/13 17:51, Sergio Fernández wrote:
So... not, what should be do?
We got some discussion, right, but no enough for getting votes from any
other IPMC member not directly involved in Marmotta (i.e., not a mentor).
Should we try to re-focues the discussion? I mean, there are few things
could be improved, as always; so, identify those concrete details, find
the way to solve it, and, in case those things are not blocking the
release, be executive on getting Marmotta released during 2013. I fear
this process is taking too long...
Looking over the email on geneal@incubator, the last message in the
general conversation was Marven Humphrey's. He's provided quite a lot
of commentary. There is a JIRA item (206) about the format of the ASF
copyright statement.
I don't see a reply on the general list or here on dev@ to know what the
project thinks about this. I guess the project needs to come to a
position on this maybe via a discussion on dev@.
If anythign is unclear, the project, ideally the release manager (so
it's a single conversation) can also ask for any further clarification
from sebb and/or Marvin.
Andy
On 18/04/13 14:49, Nandana Mihindukulasooriya wrote:
Hi,
On Thu, Apr 18, 2013 at 10:55 AM, Andy Seaborne<[email protected]> wrote:
In any case, I'd suggest that we either:
- cancel the vote and try to fix the NOTICE
- proceed with the release and fix the NOTICE in 3.0.1
What is your feeling?
IMO Leave the vote open and see what further reaction there is. Marvin
may do more review judging by his email. It's a lot of time to do a
review
and 3 days for something this big is not long and they are coming to it
without background.
+1. I also think it would be good to keep the vote open for some more
time.
As Andy said, I think one traction is the fact that having four
relatively
big distributions and reviewing needs a considerable time and effort. On
the other hand, it is apparent from the thread that people are having a
look at the NOTICE and LICENCE files and providing feedback which is very
good as that is clearly the tricky part of the release. While the the
current discussion on the [email protected] gets attention, it might be quite
possible that more people will check that.
So I also recommend to keep the vote open and keep the discussion on the
parallel thread going to reach some consensus and only if necessary
re-spin
the release to fix the NOTICE.
Best Regards,
Nandana
