That's certainly won't be a problem in reality, as Jacopo said.
What I'm curious about is if what happens if Freemarker gets into the
Incubator but then sadly later fails to graduate, so then it has to
continue outside ASF, probably with the earlier owners. I guess then
we will have to fork the
On Tue, Jun 2, 2015 at 8:07 PM Ralph Goers ralph.go...@dslextreme.com
wrote:
IMO, once the source code is migrated to the ASF you should not do any
more releases outside the ASF. I would attempt to clear up as many IP
issues as you can before entering but I believe several projects have
I would proceed with the plan that the project will succeed in graduating.
Usually project names stay with the ASF. I am not sure what the policy would be
for a project that failed to graduate. I would suspect the project could keep
it after leaving. However, if the project fails to graduate
IMO, once the source code is migrated to the ASF you should not do any more
releases outside the ASF. I would attempt to clear up as many IP issues as you
can before entering but I believe several projects have resolved their IP
issues while in the incubator. In the worst case some code may
Hi,
+1 binding
- hashes and signatures check out
- incubating in release name
- DISCLAIMER exists
- LICENSE and NOTICE correct
- No binary files in release (except one compressed text archive)
- All source files have headers
- Can compile from source
Thanks,
Justin
But before that... a question. Let's say the voting has a positive
result. Can we still do Freemarker releases outside ASF (with the
current owners and source code repository) after that? For how long?
My concern is that when we are already in the incubator, we can't
release from it as far as ASF
Thanks for checking early!
On Mon, Jun 1, 2015 at 9:54 AM, amareshwarisr . amareshw...@gmail.com
wrote:
Please ignore my previous mail. Just checked
http://incubator.apache.org/report-groups.txt, Lens report is due July,
not
June.
Thanks
Amareshwari
On Mon, Jun 1, 2015 at 11:53 AM,
