You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@abdera.apache.org by ant elder <an...@gmail.com> on 2009/10/25 10:53:39 UTC
Publishing the 1.0 release artifacts
There was a 1.0 release back in January but it doesn't look like the
release artifacts were ever published in the distribution area or
maven repository. I know there has since been a suggestion to do a new
1.0 to pick up all the latest trunk fixes but as thats taking some
time how about just publishing the January artifacts now and having
all the latest trunk code go out in a new release? WDYT?
...ant
Re: Publishing the 1.0 release artifacts
Posted by Luciano Resende <lu...@gmail.com>.
On Thu, Nov 5, 2009 at 11:45 PM, David Calavera
<da...@gmail.com> wrote:
> I don't know who was the last committer that modified the trunk code, but
> actually it doesn't compile even and I'm not sure if that code is too much
> stable.
>
> Luciano, seems you have much experience than us in legal stuff, any patch to
> solve those issues is very appreciated.
>
> Finally, I just want to remember that voting processes should go on 72
> hours, messages after that can be gracefully ignored.
>
> Cheers
I can try to send a patch over the weekend, as I'm at ApacheCon and
still have to present today...
--
Luciano Resende
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Publishing the 1.0 release artifacts
Posted by ant elder <an...@apache.org>.
On Fri, Nov 6, 2009 at 5:19 PM, Luciano Resende <lu...@gmail.com> wrote:
>
> All what I was trying to do was to give my advice on the legal side of
> the release being voted. As you said, I'm no binding, and I don't want
> to interfere with what the Abdera PMC thing it's the right thing to
> do. Please have fun....
>
Don't be like that. If we didn't publish these artifacts would you
actually help make new ones? By that I mean help fix trunk so it
builds again which is what needs to happen before any legal updates
could be done as we need to see what the distribution looks like.
...ant
Re: Publishing the 1.0 release artifacts
Posted by Luciano Resende <lu...@gmail.com>.
On Fri, Nov 6, 2009 at 8:39 AM, ant elder <an...@apache.org> wrote:
> I think it needs to be clear what state Abdera is in. There have been
> no releases since leaving the Incubator a year ago, there have been no
> commits for 6 months, committers have said they no longer have time
> for the project, most questions or patches on the dev list go ignored.
> The trunk code is broken from various changes at the start of the year
> including some non trivial refactoring and with the old committers not
> around to answer questions its difficult to work out fixes.
>
> At this stage Abdera could be retired to the Apache Attic, or try to
> get some new committers to get some life back in it. It does seem like
> there is a community willing to contribute and there is a sizable user
> base so it would be a shame to retire it. But right now its very
> difficult for anyone to help as trunk is broken and patches aren't
> getting applied.
>
> The 1.0 vote happened way back in January and passed with 4 binding +1
> votes and a non binding -1, and it seems reasonably clear from the
> thread and other later emails that the PMC considered the vote a pass
> and the artifacts could be published. I've checked the licensing,
> there are some inconsistencies but i don't see anything I'd consider a
> blocker and I'd don't see any problem with following through on the
> result of the vote and finally publishing the artifacts, especially
> given the current state of the project. That would give at least a
> point to try to go forward with and we could start bringing up trunk
> again, applying some patches, getting some new comitters, and then
> maybe it would be possible to get the latest code out in another
> release.
>
> ...ant
>
All what I was trying to do was to give my advice on the legal side of
the release being voted. As you said, I'm no binding, and I don't want
to interfere with what the Abdera PMC thing it's the right thing to
do. Please have fun....
--
Luciano Resende
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Publishing the 1.0 release artifacts
Posted by ant elder <an...@apache.org>.
I think it needs to be clear what state Abdera is in. There have been
no releases since leaving the Incubator a year ago, there have been no
commits for 6 months, committers have said they no longer have time
for the project, most questions or patches on the dev list go ignored.
The trunk code is broken from various changes at the start of the year
including some non trivial refactoring and with the old committers not
around to answer questions its difficult to work out fixes.
At this stage Abdera could be retired to the Apache Attic, or try to
get some new committers to get some life back in it. It does seem like
there is a community willing to contribute and there is a sizable user
base so it would be a shame to retire it. But right now its very
difficult for anyone to help as trunk is broken and patches aren't
getting applied.
The 1.0 vote happened way back in January and passed with 4 binding +1
votes and a non binding -1, and it seems reasonably clear from the
thread and other later emails that the PMC considered the vote a pass
and the artifacts could be published. I've checked the licensing,
there are some inconsistencies but i don't see anything I'd consider a
blocker and I'd don't see any problem with following through on the
result of the vote and finally publishing the artifacts, especially
given the current state of the project. That would give at least a
point to try to go forward with and we could start bringing up trunk
again, applying some patches, getting some new comitters, and then
maybe it would be possible to get the latest code out in another
release.
...ant
On Fri, Nov 6, 2009 at 7:45 AM, David Calavera <da...@gmail.com> wrote:
> I don't know who was the last committer that modified the trunk code, but
> actually it doesn't compile even and I'm not sure if that code is too much
> stable.
>
> Luciano, seems you have much experience than us in legal stuff, any patch to
> solve those issues is very appreciated.
>
> Finally, I just want to remember that voting processes should go on 72
> hours, messages after that can be gracefully ignored.
>
> Cheers
>
>
> On Fri, Nov 6, 2009 at 3:01 AM, Luciano Resende <lu...@gmail.com>wrote:
>
>> On Mon, Oct 26, 2009 at 12:37 AM, ant elder <an...@apache.org> wrote:
>> > Thanks for replying. I did find the old vote threads, the license
>> > issue was a question on the copyrights in the NOTICE file, I've had a
>> > look and I don't think there's any issue - not all copyrights need to
>> > be included its only required third-party notices that are necessary,
>> > and they seem ok. So it should be fine to publish those artifacts.
>> > I'll wait for a while to see if anyone else comments.
>> >
>>
>> I believe there were various enhancements applied to trunk after the
>> release was started (see [1]). as this is a 1.0 release, would it be
>> better to get these changes and start a new vote ?
>
>
>> I also think that the legal files should be reviewed, there seems to
>> be issues as described in [2], but there seems to be other issue as
>> well (e.g jaxen-LICENSE.txt is a ASL 2.0 license, and the license.txt
>> inside javen-1.1.1.jar is a BSD like one).
>>
>> [1] http://markmail.org/message/qnk6xo2e5eqtuyia
>> [2] http://markmail.org/message/vb2s6gay4dfqxnbt
>
>
>> --
>> Luciano Resende
>> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
>> http://lresende.blogspot.com/
>>
>
Re: Publishing the 1.0 release artifacts
Posted by David Calavera <da...@gmail.com>.
I don't know who was the last committer that modified the trunk code, but
actually it doesn't compile even and I'm not sure if that code is too much
stable.
Luciano, seems you have much experience than us in legal stuff, any patch to
solve those issues is very appreciated.
Finally, I just want to remember that voting processes should go on 72
hours, messages after that can be gracefully ignored.
Cheers
On Fri, Nov 6, 2009 at 3:01 AM, Luciano Resende <lu...@gmail.com>wrote:
> On Mon, Oct 26, 2009 at 12:37 AM, ant elder <an...@apache.org> wrote:
> > Thanks for replying. I did find the old vote threads, the license
> > issue was a question on the copyrights in the NOTICE file, I've had a
> > look and I don't think there's any issue - not all copyrights need to
> > be included its only required third-party notices that are necessary,
> > and they seem ok. So it should be fine to publish those artifacts.
> > I'll wait for a while to see if anyone else comments.
> >
>
> I believe there were various enhancements applied to trunk after the
> release was started (see [1]). as this is a 1.0 release, would it be
> better to get these changes and start a new vote ?
> I also think that the legal files should be reviewed, there seems to
> be issues as described in [2], but there seems to be other issue as
> well (e.g jaxen-LICENSE.txt is a ASL 2.0 license, and the license.txt
> inside javen-1.1.1.jar is a BSD like one).
>
> [1] http://markmail.org/message/qnk6xo2e5eqtuyia
> [2] http://markmail.org/message/vb2s6gay4dfqxnbt
> --
> Luciano Resende
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>
Re: Publishing the 1.0 release artifacts
Posted by Luciano Resende <lu...@gmail.com>.
On Mon, Oct 26, 2009 at 12:37 AM, ant elder <an...@apache.org> wrote:
> Thanks for replying. I did find the old vote threads, the license
> issue was a question on the copyrights in the NOTICE file, I've had a
> look and I don't think there's any issue - not all copyrights need to
> be included its only required third-party notices that are necessary,
> and they seem ok. So it should be fine to publish those artifacts.
> I'll wait for a while to see if anyone else comments.
>
I believe there were various enhancements applied to trunk after the
release was started (see [1]). as this is a 1.0 release, would it be
better to get these changes and start a new vote ?
I also think that the legal files should be reviewed, there seems to
be issues as described in [2], but there seems to be other issue as
well (e.g jaxen-LICENSE.txt is a ASL 2.0 license, and the license.txt
inside javen-1.1.1.jar is a BSD like one).
[1] http://markmail.org/message/qnk6xo2e5eqtuyia
[2] http://markmail.org/message/vb2s6gay4dfqxnbt
--
Luciano Resende
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Publishing the 1.0 release artifacts
Posted by ant elder <an...@apache.org>.
Thanks for replying. I did find the old vote threads, the license
issue was a question on the copyrights in the NOTICE file, I've had a
look and I don't think there's any issue - not all copyrights need to
be included its only required third-party notices that are necessary,
and they seem ok. So it should be fine to publish those artifacts.
I'll wait for a while to see if anyone else comments.
...ant
On Sun, Oct 25, 2009 at 11:22 AM, David Calavera
<da...@gmail.com> wrote:
> The artifacts published in January were petty much stable but there was
> license issues, some of them were missing. I can't find the thread were we
> discussed that right now. Btw, +1 to publish the same artifacts.
>
> On Sun, Oct 25, 2009 at 10:53 AM, ant elder <an...@gmail.com> wrote:
>
>> There was a 1.0 release back in January but it doesn't look like the
>> release artifacts were ever published in the distribution area or
>> maven repository. I know there has since been a suggestion to do a new
>> 1.0 to pick up all the latest trunk fixes but as thats taking some
>> time how about just publishing the January artifacts now and having
>> all the latest trunk code go out in a new release? WDYT?
>>
>> ...ant
>>
>
Re: Publishing the 1.0 release artifacts
Posted by David Calavera <da...@gmail.com>.
The artifacts published in January were petty much stable but there was
license issues, some of them were missing. I can't find the thread were we
discussed that right now. Btw, +1 to publish the same artifacts.
On Sun, Oct 25, 2009 at 10:53 AM, ant elder <an...@gmail.com> wrote:
> There was a 1.0 release back in January but it doesn't look like the
> release artifacts were ever published in the distribution area or
> maven repository. I know there has since been a suggestion to do a new
> 1.0 to pick up all the latest trunk fixes but as thats taking some
> time how about just publishing the January artifacts now and having
> all the latest trunk code go out in a new release? WDYT?
>
> ...ant
>
Re: Publishing the 1.0 release artifacts
Posted by David Calavera <da...@gmail.com>.
It's done. Thank you Ant!
On Sun, May 2, 2010 at 10:45 AM, ant elder <an...@gmail.com> wrote:
> On Sun, Oct 25, 2009 at 10:53 AM, ant elder <an...@gmail.com> wrote:
> > There was a 1.0 release back in January but it doesn't look like the
> > release artifacts were ever published in the distribution area or
> > maven repository. I know there has since been a suggestion to do a new
> > 1.0 to pick up all the latest trunk fixes but as thats taking some
> > time how about just publishing the January artifacts now and having
> > all the latest trunk code go out in a new release? WDYT?
> >
> > ...ant
> >
>
> Ok I've finally managed to get the 1.0 artifacts published, but i
> don't have access to update the live website. I've updated index.html
> in svn with the 1.0 info, could someone with access copy that to
> /x1/www/abdera.apache.org?
>
> ...ant
>
--
David Calavera
http://www.thinkincode.net
Re: Publishing the 1.0 release artifacts
Posted by ant elder <an...@gmail.com>.
On Sun, Oct 25, 2009 at 10:53 AM, ant elder <an...@gmail.com> wrote:
> There was a 1.0 release back in January but it doesn't look like the
> release artifacts were ever published in the distribution area or
> maven repository. I know there has since been a suggestion to do a new
> 1.0 to pick up all the latest trunk fixes but as thats taking some
> time how about just publishing the January artifacts now and having
> all the latest trunk code go out in a new release? WDYT?
>
> ...ant
>
Ok I've finally managed to get the 1.0 artifacts published, but i
don't have access to update the live website. I've updated index.html
in svn with the 1.0 info, could someone with access copy that to
/x1/www/abdera.apache.org?
...ant