Re: 2.7.7 snapshot

A bit of a stab in the dark, but I had that kind of problem at work
recently, and it was just because the Windows Firewall didn't like
maven's FTP Wagon. I can't say I like it either, but I was quite keen
on having it work.

2009/9/23 Antonio Cunei :
> Josh,
>
> The settings.xml file was the same that we recently used for uploading the
> releases. However, I found that the failure in the upload process was
> related to the configuration of the specific machine I was trying to upload
> from. I moved the files elsewhere, and eventually the deployment went ok.
>
> The mavenized 2.7.7 nightly files are now hopefully available on
> scala-tools.org, in:
>
> http://www.scala-tools.org/repo-snapshots/org/scala-lang/scala-compiler/...
>
> and companion directories.
> Toni
>
>

Thanks Toni,

Sorry for the inconvenience.  BTW, what happened to the 2.7.x nightly releases that used to happen?

- Josh

On Wed, Sep 23, 2009 at 5:42 PM, Antonio Cunei <antonio.cunei@epfl.ch> wrote:

Josh,

The settings.xml file was the same that we recently used for uploading the releases. However, I found that the failure in the upload process was related to the configuration of the specific machine I was trying to upload from. I moved the files elsewhere, and eventually the deployment went ok.

The mavenized 2.7.7 nightly files are now hopefully available on scala-tools.org, in:

http://www.scala-tools.org/repo-snapshots/org/scala-lang/scala-compiler/2.7.7-SNAPSHOT

and companion directories.
Toni

On Thu, September 24, 2009 1:05 am, Josh Suereth wrote:
> Thanks Toni,
>
> Sorry for the inconvenience. BTW, what happened to the 2.7.x nightly
> releases that used to happen?
>
> - Josh
>

The script was deactivated after the release of 2.7.5, which was deemed to
be the very last in the line, hence nightly builds were no longer
necessary. After that we received repeated requests to fix a single
outstanding bug, we eventually caved in and released 2.7.6. Of course, the
moral is that no good deed goes unpunished.

The 2.7.x nightly build script is now re-enabled, but it won't push files
automatically as some other services were changed in the meantime. We will
do that manually when/if there are any further changes to the branch.
After 2.7.7 is released, however, we'll close down the corresponding
nightly and the whole branch for good.
Toni

>>>>> "Antonio" == Antonio Cunei writes:

Antonio> The script was deactivated after the release of 2.7.5, which
Antonio> was deemed to be the very last in the line, [...]

Antonio> After 2.7.7 is released, however, we'll close down the
Antonio> corresponding nightly and the whole branch for good.

I would suggest caution, and realism, on this point.

The 2.7.4 release announcement said "This version will be the last
release of the 2.7.x branch."

Then 2.7.5 was thought to be the last one.

Then 2.7.6 was going to be the last one.

Now only weeks later 2.7.7 is thought to be the last one.

The fact is, these things have a way of dragging on longer than anyone
wants or expects them to. Wishing there to be no need for a 2.7.8,
eventually, can't make it so.

+1

On Thu, Sep 24, 2009 at 5:28 AM, Seth Tisue <seth@tisue.net> wrote:

>>>>> "Antonio" == Antonio Cunei <antonio.cunei@epfl.ch> writes:

 Antonio> The script was deactivated after the release of 2.7.5, which
 Antonio> was deemed to be the very last in the line, [...]

 Antonio> After 2.7.7 is released, however, we'll close down the
 Antonio> corresponding nightly and the whole branch for good.

I would suggest caution, and realism, on this point.

The 2.7.4 release announcement said "This version will be the last
release of the 2.7.x branch."

Then 2.7.5 was thought to be the last one.

Then 2.7.6 was going to be the last one.

Now only weeks later 2.7.7 is thought to be the last one.

The fact is, these things have a way of dragging on longer than anyone
wants or expects them to.  Wishing there to be no need for a 2.7.8,
eventually, can't make it so.

--
Seth Tisue @ Northwestern University / http://tisue.net
lead developer, NetLogo: http://ccl.northwestern.edu/netlogo/

Jorge, Seth,

Critical bugs will always be addressed, of course. The 2.7 branch is our
current stable release and we will support it at the very least until 2.8
sees its first stable release. However, we do have to set the bar somewhere
for what constitutes a "critical bug", and that will be scrutinized rather
more strictly for future releases.

If I may go back to the original discussion, however, I would like to
proceed with the release candidate and move a step closer to the 2.7.7
final. As I mentioned, releasing an RC however would be pointless if the
fix did not address the 2.7.6 issue that the Lift build process exposed.

The 2.7.7 snapshot has been in the scala-tools repository since yesterday,
which makes it "available", I believe :) Are there any other obstacles to
testing Lift with it? Please let me know if there is anything else that
needs to be done.

Thank you.
Toni

Jorge Ortiz wrote:
> +1
>
> On Thu, Sep 24, 2009 at 5:28 AM, Seth Tisue wrote:
>
>>>>>>> "Antonio" == Antonio Cunei writes:
>> Antonio> The script was deactivated after the release of 2.7.5, which
>> Antonio> was deemed to be the very last in the line, [...]
>>
>> Antonio> After 2.7.7 is released, however, we'll close down the
>> Antonio> corresponding nightly and the whole branch for good.
>>
>> I would suggest caution, and realism, on this point.
>>
>> The 2.7.4 release announcement said "This version will be the last
>> release of the 2.7.x branch."
>>
>> Then 2.7.5 was thought to be the last one.
>>
>> Then 2.7.6 was going to be the last one.
>>
>> Now only weeks later 2.7.7 is thought to be the last one.
>>
>> The fact is, these things have a way of dragging on longer than anyone
>> wants or expects them to. Wishing there to be no need for a 2.7.8,
>> eventually, can't make it so.
>>
>> --
>> Seth Tisue @ Northwestern University / http://tisue.net
>> lead developer, NetLogo: http://ccl.northwestern.edu/netlogo/
>>
>

>>>>> "Antonio" == Antonio Cunei writes:

Antonio> Jorge, Seth, Critical bugs will always be addressed, of
Antonio> course. The 2.7 branch is our current stable release and we
Antonio> will support it at the very least until 2.8 sees its first
Antonio> stable release. However, we do have to set the bar somewhere
Antonio> for what constitutes a "critical bug", and that will be
Antonio> scrutinized rather more strictly for future releases.

fair enough :-)

On Thu, Sep 24, 2009 at 1:12 PM, Antonio Cunei <antonio.cunei@epfl.ch> wrote:

Jorge, Seth,

Critical bugs will always be addressed, of course. The 2.7 branch is our current stable release and we will support it at the very least until 2.8 sees its first stable release. However, we do have to set the bar somewhere for what constitutes a "critical bug", and that will be scrutinized rather more strictly for future releases.

If I may go back to the original discussion, however, I would like to proceed with the release candidate and move a step closer to the 2.7.7 final. As I mentioned, releasing an RC however would be pointless if the fix did not address the 2.7.6 issue that the Lift build process exposed.

The 2.7.7 snapshot has been in the scala-tools repository since yesterday, which makes it "available", I believe :)

Quoting you:

It's all in the open: we don't hide that information.
... your best bet is
just checking the log in order to decide
 

Are there any other obstacles to testing Lift with it? Please let me know if there is anything else that needs to be done.

Thank you.
Toni


Jorge Ortiz wrote:

+1

On Thu, Sep 24, 2009 at 5:28 AM, Seth Tisue <seth@tisue.net> wrote:

"Antonio" == Antonio Cunei <antonio.cunei@epfl.ch> writes:

 Antonio> The script was deactivated after the release of 2.7.5, which
 Antonio> was deemed to be the very last in the line, [...]

 Antonio> After 2.7.7 is released, however, we'll close down the
 Antonio> corresponding nightly and the whole branch for good.

I would suggest caution, and realism, on this point.

The 2.7.4 release announcement said "This version will be the last
release of the 2.7.x branch."

Then 2.7.5 was thought to be the last one.

Then 2.7.6 was going to be the last one.

Now only weeks later 2.7.7 is thought to be the last one.

The fact is, these things have a way of dragging on longer than anyone
wants or expects them to.  Wishing there to be no need for a 2.7.8,
eventually, can't make it so.

--
Seth Tisue @ Northwestern University / http://tisue.net
lead developer, NetLogo: http://ccl.northwestern.edu/netlogo/

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics