"Eric Pugh" <[EMAIL PROTECTED]> writes:
>All of this sounds good. I'll probably only get to it tomarrow. I'll deploy
>the jars somewhere convenient for you to grab them. PS, would you mind
No problem. We should really hurry. I did the 2.3 turbine release on
2003-08-17... =8-) Maybe we can beat our "one relase per year"
cycle... :-)
>signing my upcoming configuration.jar milestone as well? The key stuff
>seems to have totally beat me to a pulp in trying to get it to work on
>Windows.
No Windows, no Cry. ;-)
Regards
Henning
>Eric
>> -----Original Message-----
>> From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]
>> Sent: Friday, August 13, 2004 9:54 AM
>> To: [EMAIL PROTECTED]
>> Subject: Re: Any objection to posting Turbine 2.4 Milestone 1
>>
>>
>> "Eric Pugh" <[EMAIL PROTECTED]> writes:
>>
>> >Hi guys..
>>
>> >In the tradition of the Eclipse project and it's many many milestones, I
>> >wanted to see about publishing a 2.4 Milestone 1 tomorrow.
>> Basically, there
>> >are various projects that are using various flavors of Turbine 2.4.
>>
>> +1 Release early, release often is a good thing. As we do just a
>> milestone release, please remember to do a CVS tag so we can reproduce
>> the code that you have built the milestone from.
>>
>> If you send me the jars, I can sign them with the turbine release key
>> and put them onto the apache download servers.
>>
>> >Antelope, any META Turbine 2.4 flavor, and my personal copy of Scarab all
>> >come to mind.
>>
>> I want to make a "META_1_2" tag this weekend and put the plugin onto
>> ibiblio. It is about time IMHO.
>>
>> Scott, as you seem to be the lone Torque guy currently: Any objections
>> for calling a vote to release torque-3.1.1? I finally want to get an
>> "official" version of the Torque plugin out.
>>
>> I feel that it is time to do some maintenance releases of the various
>> Turbine branches for quite some time. However, I want to sort out the
>> commons-logging issue for the 2.3 branch before rolling a release. And
>> I would really like to have torque-3.1.1 (not 3.2-dev or HEAD!) in a
>> 2.3 relase.
>>
>> >It would be nice for people to have a version called
>> turbine-2.4-m1.jar that
>> >would be an explicit line in the sand in terms of features. It would
>> >include the pipeline, PipelineData, and everything else we have
>> done in 2.4.
>>
>> +1
>>
>> >It won't include any changes/resolution to updating the Avalon container
>> >used in Turbine. It also won't include any of the new Fulcrum
>> equivalents
>> >to Turbine services that haven't already been integrated.
>>
>> We should also do a fulcrum milestone. I wouldn't want to see SNAPSHOT
>> references in the META flavor files.
>>
>> Regards
>> Henning
>>
>>
>> --
>> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
>> [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
>>
>> RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
>> Linux, Java, perl, Solaris -- Consulting, Training, Development
>>
>> "Fighting for one's political stand is an honorable action, but re-
>> fusing to acknowledge that there might be weaknesses in one's
>> position - in order to identify them so that they can be remedied -
>> is a large enough problem with the Open Source movement that it
>> deserves to be on this list of the top five problems."
>> -- Michelle Levesque, "Fundamental Issues with
>> Open Source Software Development"
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honorable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
