Home » Language IDEs » AspectJ » Lancaster?
| Lancaster? [message #29424] |
Wed, 14 January 2004 13:25  |
Eclipse User |
|
|
|
What is the current state of Lancaster? Is the "developer build"
mentioned in AJDT download page a build of Lancaster? If so, how
stable/usable is it?
Is there a rough roadmap for Lancaster?
Guillaume
|
|
|
| Re: Lancaster? [message #29463 is a reply to message #29424] |
Thu, 22 January 2004 18:01  |
| Eclipse User |
|
|
|
Originally posted by: newsserver_mails.bodden.de
Have a look at what Adrian posted as well as
http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.ajd t/main.html?rev=1.28
Eric
-----------
From: aspectj-dev-admin@eclipse.org [mailto:aspectj-dev-admin@eclipse.org]
On Behalf Of Adrian Colyer
Sent: Donnerstag, 15. Januar 2004 21:10
To: aspectj-dev@eclipse.org
Subject: [aspectj-dev] Schedule options for AspectJ 1.2 release
I propose the following strategy for the management of the AspectJ 1.2
release schedule:
We'd like to put a release out in time for the AOSD 2004 conference, week of
22nd March. Ideally this would be the 1.2 final release. To get there, we'll
need a release candidate out around the last week of February, to give users
a chance to report any remaining bugs. I propose we shoot for these dates -
if things go well with the first release candidate we'll put out 1.2 final
in March, otherwise we'll put out a second release candidate, and delay the
final release until we have achieved the desired quality levels.
Note that this strategy does not include alpha or beta releases as we have
done before. This is for 2 reasons - (1) the package, test and release cycle
consumes precious project resources everytime we go through it, time that
could be spent improving the quality of the code base instead, and (2) since
our last release we have an introduced a stage to our automated build
process that posts the results of the most recent build to Eclipse.org,
making it easy for alpha and beta testers to download the most recent build
at any time. If we change the cruise control scripts so that the
aspectj-DEVELOPMENT.jar is only posted to eclipse.org when a build passes
all of the test suite, then this will effectively become the 'best-so-far'
build. Part of the release strategy would then be to publicize more widely
the location of the install jar (i.e. to aspectj-users) so that those who
want to participate in early testing can do so.
If we find we cannot make a release candidate by the end of February for any
reason, then rc1 will instead go out in March in time for the AOSD
conference, but I hope that this delay will not be necessary.
-- Adrian
Adrian_Colyer@uk.ibm.com
--
------------------------------------------------------------ -----
Eric Bodden
ICQ UIN: 12656220
Website: http://www.bodden.de
PGP key available
|
|
|
| Re: Lancaster? [message #30196 is a reply to message #29463] |
Wed, 04 February 2004 16:58 |
| Eclipse User |
|
|
|
The screenshots are amazing!
Are the current builds usable? What is missing?
Eric Bodden wrote:
> Have a look at what Adrian posted as well as
>
> http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.ajd t/main.html?rev=1.28
>
> Eric
>
> -----------
>
>
>
> From: aspectj-dev-admin@eclipse.org [mailto:aspectj-dev-admin@eclipse.org]
> On Behalf Of Adrian Colyer
>
> Sent: Donnerstag, 15. Januar 2004 21:10
>
> To: aspectj-dev@eclipse.org
>
> Subject: [aspectj-dev] Schedule options for AspectJ 1.2 release
>
>
>
> I propose the following strategy for the management of the AspectJ 1.2
> release schedule:
>
>
> We'd like to put a release out in time for the AOSD 2004 conference, week of
> 22nd March. Ideally this would be the 1.2 final release. To get there, we'll
> need a release candidate out around the last week of February, to give users
> a chance to report any remaining bugs. I propose we shoot for these dates -
> if things go well with the first release candidate we'll put out 1.2 final
> in March, otherwise we'll put out a second release candidate, and delay the
> final release until we have achieved the desired quality levels.
>
>
> Note that this strategy does not include alpha or beta releases as we have
> done before. This is for 2 reasons - (1) the package, test and release cycle
> consumes precious project resources everytime we go through it, time that
> could be spent improving the quality of the code base instead, and (2) since
> our last release we have an introduced a stage to our automated build
> process that posts the results of the most recent build to Eclipse.org,
> making it easy for alpha and beta testers to download the most recent build
> at any time. If we change the cruise control scripts so that the
> aspectj-DEVELOPMENT.jar is only posted to eclipse.org when a build passes
> all of the test suite, then this will effectively become the 'best-so-far'
> build. Part of the release strategy would then be to publicize more widely
> the location of the install jar (i.e. to aspectj-users) so that those who
> want to participate in early testing can do so.
>
>
> If we find we cannot make a release candidate by the end of February for any
> reason, then rc1 will instead go out in March in time for the AOSD
> conference, but I hope that this delay will not be necessary.
>
>
> -- Adrian
>
> Adrian_Colyer@uk.ibm.com
>
>
>
>
|
|
|
| Re: Lancaster? [message #30231 is a reply to message #30196] |
Wed, 04 February 2004 17:08 |
| Eclipse User |
|
|
|
Ah, which version of eclipse did you use to produce these screenshots?
Guillaume Pothier wrote:
> The screenshots are amazing!
> Are the current builds usable? What is missing?
>
> Eric Bodden wrote:
>
>> Have a look at what Adrian posted as well as
>>
>> http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.ajd t/main.html?rev=1.28
>>
>>
>> Eric
>>
>> -----------
>>
>>
>>
>> From: aspectj-dev-admin@eclipse.org
>> [mailto:aspectj-dev-admin@eclipse.org]
>> On Behalf Of Adrian Colyer
>>
>> Sent: Donnerstag, 15. Januar 2004 21:10
>>
>> To: aspectj-dev@eclipse.org
>>
>> Subject: [aspectj-dev] Schedule options for AspectJ 1.2 release
>>
>>
>>
>> I propose the following strategy for the management of the AspectJ 1.2
>> release schedule:
>>
>>
>> We'd like to put a release out in time for the AOSD 2004 conference,
>> week of
>> 22nd March. Ideally this would be the 1.2 final release. To get there,
>> we'll
>> need a release candidate out around the last week of February, to give
>> users
>> a chance to report any remaining bugs. I propose we shoot for these
>> dates -
>> if things go well with the first release candidate we'll put out 1.2
>> final
>> in March, otherwise we'll put out a second release candidate, and
>> delay the
>> final release until we have achieved the desired quality levels.
>>
>>
>> Note that this strategy does not include alpha or beta releases as we
>> have
>> done before. This is for 2 reasons - (1) the package, test and release
>> cycle
>> consumes precious project resources everytime we go through it, time that
>> could be spent improving the quality of the code base instead, and (2)
>> since
>> our last release we have an introduced a stage to our automated build
>> process that posts the results of the most recent build to Eclipse.org,
>> making it easy for alpha and beta testers to download the most recent
>> build
>> at any time. If we change the cruise control scripts so that the
>> aspectj-DEVELOPMENT.jar is only posted to eclipse.org when a build passes
>> all of the test suite, then this will effectively become the
>> 'best-so-far'
>> build. Part of the release strategy would then be to publicize more
>> widely
>> the location of the install jar (i.e. to aspectj-users) so that those who
>> want to participate in early testing can do so.
>>
>>
>> If we find we cannot make a release candidate by the end of February
>> for any
>> reason, then rc1 will instead go out in March in time for the AOSD
>> conference, but I hope that this delay will not be necessary.
>>
>>
>> -- Adrian
>>
>> Adrian_Colyer@uk.ibm.com
>>
>>
>>
>>
>
|
|
| |
| Re: Lancaster? [message #30549 is a reply to message #30266] |
Mon, 09 February 2004 09:31 |
| Eclipse User |
|
|
|
Originally posted by: clemas.uk.ibm.com
The Lancaster AJDT screenshots are from an Eclipse 3.0M6 - Lancaster is a
brand new AJDT codebase. We hope to have something available by the AOSD
conference in March, as Eric correctly guessed ;)
Andy.
Andy Clement
AJDT/AspectJ Development
|
|
|
| Re: Lancaster? [message #574082 is a reply to message #29424] |
Thu, 22 January 2004 18:01 |
| Eclipse User |
|
|
|
Have a look at what Adrian posted as well as
http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.ajd t/main.html?rev=1.28
Eric
-----------
From: aspectj-dev-admin@eclipse.org [mailto:aspectj-dev-admin@eclipse.org]
On Behalf Of Adrian Colyer
Sent: Donnerstag, 15. Januar 2004 21:10
To: aspectj-dev@eclipse.org
Subject: [aspectj-dev] Schedule options for AspectJ 1.2 release
I propose the following strategy for the management of the AspectJ 1.2
release schedule:
We'd like to put a release out in time for the AOSD 2004 conference, week of
22nd March. Ideally this would be the 1.2 final release. To get there, we'll
need a release candidate out around the last week of February, to give users
a chance to report any remaining bugs. I propose we shoot for these dates -
if things go well with the first release candidate we'll put out 1.2 final
in March, otherwise we'll put out a second release candidate, and delay the
final release until we have achieved the desired quality levels.
Note that this strategy does not include alpha or beta releases as we have
done before. This is for 2 reasons - (1) the package, test and release cycle
consumes precious project resources everytime we go through it, time that
could be spent improving the quality of the code base instead, and (2) since
our last release we have an introduced a stage to our automated build
process that posts the results of the most recent build to Eclipse.org,
making it easy for alpha and beta testers to download the most recent build
at any time. If we change the cruise control scripts so that the
aspectj-DEVELOPMENT.jar is only posted to eclipse.org when a build passes
all of the test suite, then this will effectively become the 'best-so-far'
build. Part of the release strategy would then be to publicize more widely
the location of the install jar (i.e. to aspectj-users) so that those who
want to participate in early testing can do so.
If we find we cannot make a release candidate by the end of February for any
reason, then rc1 will instead go out in March in time for the AOSD
conference, but I hope that this delay will not be necessary.
-- Adrian
Adrian_Colyer@uk.ibm.com
--
------------------------------------------------------------ -----
Eric Bodden
ICQ UIN: 12656220
Website: http://www.bodden.de
PGP key available
|
|
|
| Re: Lancaster? [message #574522 is a reply to message #29463] |
Wed, 04 February 2004 16:58 |
| Eclipse User |
|
|
|
The screenshots are amazing!
Are the current builds usable? What is missing?
Eric Bodden wrote:
> Have a look at what Adrian posted as well as
>
> http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.ajd t/main.html?rev=1.28
>
> Eric
>
> -----------
>
>
>
> From: aspectj-dev-admin@eclipse.org [mailto:aspectj-dev-admin@eclipse.org]
> On Behalf Of Adrian Colyer
>
> Sent: Donnerstag, 15. Januar 2004 21:10
>
> To: aspectj-dev@eclipse.org
>
> Subject: [aspectj-dev] Schedule options for AspectJ 1.2 release
>
>
>
> I propose the following strategy for the management of the AspectJ 1.2
> release schedule:
>
>
> We'd like to put a release out in time for the AOSD 2004 conference, week of
> 22nd March. Ideally this would be the 1.2 final release. To get there, we'll
> need a release candidate out around the last week of February, to give users
> a chance to report any remaining bugs. I propose we shoot for these dates -
> if things go well with the first release candidate we'll put out 1.2 final
> in March, otherwise we'll put out a second release candidate, and delay the
> final release until we have achieved the desired quality levels.
>
>
> Note that this strategy does not include alpha or beta releases as we have
> done before. This is for 2 reasons - (1) the package, test and release cycle
> consumes precious project resources everytime we go through it, time that
> could be spent improving the quality of the code base instead, and (2) since
> our last release we have an introduced a stage to our automated build
> process that posts the results of the most recent build to Eclipse.org,
> making it easy for alpha and beta testers to download the most recent build
> at any time. If we change the cruise control scripts so that the
> aspectj-DEVELOPMENT.jar is only posted to eclipse.org when a build passes
> all of the test suite, then this will effectively become the 'best-so-far'
> build. Part of the release strategy would then be to publicize more widely
> the location of the install jar (i.e. to aspectj-users) so that those who
> want to participate in early testing can do so.
>
>
> If we find we cannot make a release candidate by the end of February for any
> reason, then rc1 will instead go out in March in time for the AOSD
> conference, but I hope that this delay will not be necessary.
>
>
> -- Adrian
>
> Adrian_Colyer@uk.ibm.com
>
>
>
>
|
|
|
| Re: Lancaster? [message #574539 is a reply to message #30196] |
Wed, 04 February 2004 17:08 |
| Eclipse User |
|
|
|
Ah, which version of eclipse did you use to produce these screenshots?
Guillaume Pothier wrote:
> The screenshots are amazing!
> Are the current builds usable? What is missing?
>
> Eric Bodden wrote:
>
>> Have a look at what Adrian posted as well as
>>
>> http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.ajd t/main.html?rev=1.28
>>
>>
>> Eric
>>
>> -----------
>>
>>
>>
>> From: aspectj-dev-admin@eclipse.org
>> [mailto:aspectj-dev-admin@eclipse.org]
>> On Behalf Of Adrian Colyer
>>
>> Sent: Donnerstag, 15. Januar 2004 21:10
>>
>> To: aspectj-dev@eclipse.org
>>
>> Subject: [aspectj-dev] Schedule options for AspectJ 1.2 release
>>
>>
>>
>> I propose the following strategy for the management of the AspectJ 1.2
>> release schedule:
>>
>>
>> We'd like to put a release out in time for the AOSD 2004 conference,
>> week of
>> 22nd March. Ideally this would be the 1.2 final release. To get there,
>> we'll
>> need a release candidate out around the last week of February, to give
>> users
>> a chance to report any remaining bugs. I propose we shoot for these
>> dates -
>> if things go well with the first release candidate we'll put out 1.2
>> final
>> in March, otherwise we'll put out a second release candidate, and
>> delay the
>> final release until we have achieved the desired quality levels.
>>
>>
>> Note that this strategy does not include alpha or beta releases as we
>> have
>> done before. This is for 2 reasons - (1) the package, test and release
>> cycle
>> consumes precious project resources everytime we go through it, time that
>> could be spent improving the quality of the code base instead, and (2)
>> since
>> our last release we have an introduced a stage to our automated build
>> process that posts the results of the most recent build to Eclipse.org,
>> making it easy for alpha and beta testers to download the most recent
>> build
>> at any time. If we change the cruise control scripts so that the
>> aspectj-DEVELOPMENT.jar is only posted to eclipse.org when a build passes
>> all of the test suite, then this will effectively become the
>> 'best-so-far'
>> build. Part of the release strategy would then be to publicize more
>> widely
>> the location of the install jar (i.e. to aspectj-users) so that those who
>> want to participate in early testing can do so.
>>
>>
>> If we find we cannot make a release candidate by the end of February
>> for any
>> reason, then rc1 will instead go out in March in time for the AOSD
>> conference, but I hope that this delay will not be necessary.
>>
>>
>> -- Adrian
>>
>> Adrian_Colyer@uk.ibm.com
>>
>>
>>
>>
>
|
|
|
| Re: Lancaster? [message #574584 is a reply to message #30231] |
Wed, 04 February 2004 20:18 |
| Eclipse User |
|
|
|
Hi.
Once upon a time <bvrqcv$p6l$1@eclipse.org>,
Guillaume Pothier <gpothier@free.fr> enriched the world with the following:
> Ah, which version of eclipse did you use to produce these screenshots?
Erm... you might wanna ask Adrian himself (I've got nothing to do with it),
but I believe that it was a late 3.0 build, presumably M4 (since M5 and M6
are currently not supported by the AJDT).
>> The screenshots are amazing!
>> Are the current builds usable?
It's not in the current build stream yet - just an internal version so far.
>> What is missing?
Sorry, cannot comment on that. But I strongly believe that you can expect a
stable Lancaster build by the time of the AOSD conference (@ Lancaster).
Eric
--
------------------------------------------------------------ -----
Eric Bodden
ICQ UIN: 12656220
Website: http://www.bodden.de
PGP key available
|
|
|
| Re: Lancaster? [message #574865 is a reply to message #30266] |
Mon, 09 February 2004 09:31 |
| Eclipse User |
|
|
|
The Lancaster AJDT screenshots are from an Eclipse 3.0M6 - Lancaster is a
brand new AJDT codebase. We hope to have something available by the AOSD
conference in March, as Eric correctly guessed ;)
Andy.
Andy Clement
AJDT/AspectJ Development
|
|
|
Goto Forum:
Current Time: Fri Sep 05 15:39:42 EDT 2025
Powered by FUDForum. Page generated in 0.07179 seconds |
Home