[kepler-dev] Re: [SDM-SPA] New distribution of Ptolemy for LLNL users
Bertram Ludaescher
ludaesch at sdsc.edu
Thu Mar 4 06:23:50 PST 2004
Hi Matt:
I think your suggestions for a more orderly way of going about Kepler
releases are great!
Indeed it would make the life of the developers much easier if they
knew well in advance what's coming, when the deadlines for final
additions, tests are etc.
Also from your experience it sounds like Bugzilla is the way to go, so
I would like the SDM/SPA folks to adopt that as well, provided we can
address their concerns:
At a recent ad-hoc SPA conference call, which was also attended by
SEEK and Ptolemy members, it was suggested to have a "protected" SPA
area under Bugzilla so that non-public documents could be attached to
"bugs" etc.
I'm not sure how how easy it is to set up such a "group-eyes only" SPA
area.
Either way, I think it would be beneficial if we could align our
Kepler efforts across SEEK, SPA, GEON etc.
Bertram
>>>>> "MJ" == Matt Jones <jones at nceas.ucsb.edu> writes:
MJ>
MJ> Hi Bertram,
MJ> I think more frequent releases are a good idea. That said, here's a couple of
MJ> caveats and comments.
MJ>
MJ> 1) Personally, I think we should start a more formal release system for
MJ> Kepler. In particular, I would like to see us label our releases in terms of
MJ> their quality (e.g., alpha, beta, ...). I'd be fine with releasing the current
MJ> CVS head as an alpha release, but I think we'd need to do some more formal
MJ> testing to call it a beta, and we're certainly not ready for a full release
MJ> because we haven't completed all of the desired features. So my preference
MJ> would be to release it as "kepler-1.0.0alpha1" or something like that.
MJ> I'm not sure what the major version number should be given that Ptolemy is
MJ> at 3.0.2, and so we should discuss this.
MJ>
MJ> 2) To have more frequent releases, we should have a more stringent list of
MJ> features and bugs that we are targeting for each release. In the past we've
MJ> used Bugzilla for this and it works well. Each feature or bug gets labeled
MJ> with a target milestone, and when all of the tasks for a milestone are marked as
MJ> done then the release is bundled up. If some tasks are causing the release to
MJ> be delayed, they can be retargeted at a later release in a project discussion.
MJ> To accomodate this, chad has set up a series of target milestones in the
MJ> Kepler bugzilla which I have edited today. The milestones currently are:
MJ>
MJ> 1.0.0alpha1
MJ> 1.0.0beta1-05.01.2004
MJ> 1.0.0beta2-06.01.2004
MJ> 1.0.0-06.12.2004
MJ> Post-rel-1.0.0
MJ> Postpone
MJ>
MJ> So, aiming for the first beta release at the begininning of May in time for the Scotland scientific workflows meeting. We should discuss the timing of one or
MJ> more alpha releases before that. When new bugs are entered in the system, they
MJ> default to the "Postpone" milestone. The developer who gets that bug should
MJ> choose an appropriate target milestone for the bug when they accept it.
MJ>
MJ> 3) The installer software should work on Windows, Mac, Linux if possible. We
MJ> have used InstallAnywhere successfully in the past. It works well on all of
MJ> the OS's listed, and is free. It also allows you to build installers with and
MJ> without a JVM included. It would be nice if building the installer was
MJ> incorporated directly into the ant build script so that "ant dist" or similar
MJ> automatically built the installer apps for all platforms.
MJ>
MJ> I can't make a conference call this week, but Chad may be able to and that
MJ> should be fine in terms of representing SEEK.
MJ>
MJ> Matt
MJ>
MJ> On Sun, 29 Feb 2004, Bertram Ludaescher wrote:
MJ>
>>
>> Chad, Matt, and Ptolemy members:
>>
>> Please feel free to chime into this one. It's originated by SDM/SPA
>> folks but due to relevance for Kepler, it will be helpful to hear your
>> POV and coordinate on packaging efforts.
>>
>> We can also send around a summary of the phone call, and follow up
>> through email/another call (since I know some can't make it; in fact,
>> I may be one of those..)
>> Bertram
>>
>> >>>>> "V" == Vouk <vouk at ncsu.edu> writes:
V>
V> Monday is Ad Hoc
V> We do not have an 800 number, but I will arrange for an NC State
V> MeetMe number (it will cost you long distance charges).
V> mav
V>
V> Bertram Ludaescher wrote:
V>
>> >>>>>>> "V" == Vouk <vouk at ncsu.edu> writes:
>> >>>>>>>
>> >>>>>>>
V>
V> David,
V> Yes. No problem.
V> Let's do a teleconference on Monday (say 9am your time)
V> to nail down the details.
>> >>
>> >> Do we have a regular SPA call on Monday or an ad-hoc one?
>> >>
>> >> In the case of the latter, and if we talk about packaging, we could
>> >> also invite some of our colleagues from the Kepler team at SEEK/UCSB
>> >> and of course Ptolemy/UCB, if they are interested and available.
>> >>
>> >> We may also decide to have different packaging efforts (e.g., one
>> >> based on InstallShield, one based on InstallAnyWhere, and yet another
>> >> one based on Web Start or so -- whichever works best).
>> >>
>> >> What does everyone think?
>> >>
>> >> Bertram
>> >>
>> >>
V> Transfac is not quite here yet, but will be next week (actually
V> Monday it may be available already)
V>
V> We have been snowed-out again so things are not moving
V> as fast as we would like.
V>
V> No Mac distribution yet. It is not difficult to do,
V> just different (probably a week to work out bugs
V> the first time it is done)
V>
V> mav
V>
V>
V> David Buttler wrote:
V>
>> >>
>> >>
>> >>>> Hi,
>> >>>>
>> >>>> I would like to create a new distribution of Ptolemy for our users
>> >>>> here at LLNL. From our conversation a couple of weeks ago, it sounded
>> >>>> like NCSU should be able to quickly create a new version using Install
>> >>>> Shield. The main reasons I would like a new distribution is to cover
>> >>>> the following concerns:
>> >>>> 1) Include the new Transfac service
>> >>>> 2) Include the new Web Service actors, to provide access to both the
>> >>>> services available at NCSU as well as other bioinformatics web services
>> >>>>
>> >>>> Is this possible to do? Have there been any problems with finding a
>> >>>> Transfac replacement?
>> >>>>
>> >>>> As a side question, has there been any work yet on creating a Mac
>> >>>> distribution? Do we have any estimates of how difficult it will be or
>> >>>> when a Mac version may be available?
>> >>>>
>> >>>> Thanks!
>> >>>> Dave
>> >>>>
>> >>>>
>> >>>>
>> >>
>> >>
>> >>
V> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
V> <html>
V> <head>
V> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
V> <title></title>
V> </head>
V> <body text="#000000" bgcolor="#ffffff">
V> Monday is Ad Hoc<br>
V> We do not have an 800 number, but I will arrange for an NC State<br>
V> MeetMe number (it will cost you long distance charges).<br>
V> mav<br>
V> <br>
V> Bertram Ludaescher wrote:<br>
V> <blockquote type="cite"
V> cite="mid16448.43598.582213.984171 at multivac.sdsc.edu">
V> <blockquote type="cite">
V> <blockquote type="cite">
V> <blockquote type="cite">
V> <blockquote type="cite">
V> <blockquote type="cite">
V> <pre wrap="">"V" == Vouk <a class="moz-txt-link-rfc2396E" href="mailto:vouk at ncsu.edu"><vouk at ncsu.edu></a> writes:
V> </pre>
V> </blockquote>
V> </blockquote>
V> </blockquote>
V> </blockquote>
V> </blockquote>
V> <pre wrap=""><!---->V>
V> V> David,
V> V> Yes. No problem.
V> V> Let's do a teleconference on Monday (say 9am your time)
V> V> to nail down the details.
V>
V> Do we have a regular SPA call on Monday or an ad-hoc one?
V>
V> In the case of the latter, and if we talk about packaging, we could
V> also invite some of our colleagues from the Kepler team at SEEK/UCSB
V> and of course Ptolemy/UCB, if they are interested and available.
V>
V> We may also decide to have different packaging efforts (e.g., one
V> based on InstallShield, one based on InstallAnyWhere, and yet another
V> one based on Web Start or so -- whichever works best).
V>
V> What does everyone think?
V>
V> Bertram
V>
V>
V> V> Transfac is not quite here yet, but will be next week (actually
V> V> Monday it may be available already)
V> V>
V> V> We have been snowed-out again so things are not moving
V> V> as fast as we would like.
V> V>
V> V> No Mac distribution yet. It is not difficult to do,
V> V> just different (probably a week to work out bugs
V> V> the first time it is done)
V> V>
V> V> mav
V> V>
V> V>
V> V> David Buttler wrote:
V> V>
V> </pre>
V> <blockquote type="cite">
V> <blockquote type="cite">
V> <pre wrap="">Hi,
V>
V> I would like to create a new distribution of Ptolemy for our users
V> here at LLNL. From our conversation a couple of weeks ago, it sounded
V> like NCSU should be able to quickly create a new version using Install
V> Shield. The main reasons I would like a new distribution is to cover
V> the following concerns:
V> 1) Include the new Transfac service
V> 2) Include the new Web Service actors, to provide access to both the
V> services available at NCSU as well as other bioinformatics web services
V>
V> Is this possible to do? Have there been any problems with finding a
V> Transfac replacement?
V>
V> As a side question, has there been any work yet on creating a Mac
V> distribution? Do we have any estimates of how difficult it will be or
V> when a Mac version may be available?
V>
V> Thanks!
V> Dave
V>
V> </pre>
V> </blockquote>
V> </blockquote>
V> <pre wrap=""><!---->
V> </pre>
V> </blockquote>
V> </body>
V> </html>
>> _______________________________________________
>> kepler-dev mailing list
>> kepler-dev at ecoinformatics.org
>> http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
>>
MJ>
MJ> --
MJ> ******************************************************************
MJ> Matt Jones jones at nceas.ucsb.edu
MJ> http://www.nceas.ucsb.edu/ Fax: 425-920-2439 Ph: 907-789-0496
MJ> National Center for Ecological Analysis and Synthesis (NCEAS)
MJ> ******************************************************************
More information about the Kepler-dev
mailing list