You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by "Henning P. Schmiedehausen" <hp...@intermeta.de> on 2005/09/21 13:41:02 UTC
fulcrum jars @ ibiblio
Hi,
[fulcrum-yaafi 1.0.4 is missing, that's how I came here...]
there are a number of jars mirrored from
www.apache.org/dist/java-repository up to ibiblio. The Apache
guidelines require us to actually run CfV's whenever we put stuff
there, so we might want to make sure that we adhere to these
guidelines. Having a number of official releases will also help us
with visibility.
Best regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +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
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: fulcrum jars @ ibiblio
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Siegfried Goeschl <si...@it20one.at> writes:
>Henning P. Schmiedehausen wrote:
>>Siegfried Goeschl <si...@it20one.at> writes:
>>
>>
>>
>>>PS: What's a "CfV"?!
>>>
>>>
>>
>>Geee.. :-)
>>
>>
>>
>Argghhh, brain dead while writing a XSLT .... :-)
I understand. It takes a special mind mode to do this. It is almost
the same as writing a sendmail cf file. I found out that two glasses
of red wine do the trick just fine. ;-)
Best regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +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
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: fulcrum jars @ ibiblio
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Henning,
I uploaded the
+) fulcrum-yaafi-1.0.4.jar
+) fulcrum-testcontainer-1.0.5.jar
+) fulcrum-groovy-1.0.1-dev
+) fulcrum-resourcemanager-1.0.1-dev.jar
to the unofficial Turbine repo
(http://jakarta.apache.org/turbine/repo/fulcrum/jars/)
I assume I should also update http://cvs.apache.org/dist/ but I skip
that since I should read the docs and I'm currently under some pressure
to get my work done.
Cheers,
Siegfried Goeschl
Siegfried Goeschl wrote:
> Hi Henning,
>
> see my comments below ....
>
> Cheers,
>
> Siegfried Goeschl
>
>
>
> Henning P. Schmiedehausen wrote:
>
>> Siegfried Goeschl <si...@it20one.at> writes:
>>
>>
>>
>>> PS: What's a "CfV"?!
>>>
>>
>>
>> Geee.. :-)
>>
>>
>>
> Argghhh, brain dead while writing a XSLT .... :-)
>
>> A "CfV" is a "Call for Vote". CfV's are mandatory for everything that
>> should hit www.apache.org/dist/ at some point.
>>
>> Ok, so this is how it goes/should go:
>>
>> We can develop and work all we want. However, if we decide that a
>> certain version should be "official" or hit the ASF infrastructure, we
>> have the following options:
>>
>> There is the "unofficial turbine maven repository" at
>> http://jakarta.apache.org/turbine/repo/ which has been invented to get
>> around the "upload to ibiblio" headaches a long time ago.
>>
>> This repo works with a delay of two hours as it is mirrored onto the
>> delivery server from minotaur.
>>
>> There is also the official way on how to deal with non-released
>> versions which is to go through http://cvs.apache.org/dist/
>> (.../jakarta/turbine in our case.) This location is _intended_ to be
>> used for snapshots, nightlies, rc's, alphas, betas and so on.
>>
>> You can find more information about that on
>> http://www.apache.org/dev/release.html
>>
>> For the current 2.3 RC's and META RC's, I've created
>> http://cvs.apache.org/dist/jakarta/turbine/java-repository which we
>> can use as our repo. This has also the advantage that there is no two
>> hour lag to the delivery servers.
>>
>> The official releases go into www.apache.org/dist. This is the
>> location that is picked up by the apache mirror system and distributes
>> the releases all over the world. Due to this fact, it is very
>> important to make sure that a release confirms to the official ASF
>> guidelines.
>>
>> When we want to 'officially' publish releases of components, the core
>> or anything else, we must hold a vote, send this vote to the PMC for
>> approval and then do "official" publishing as described at the various
>> http://www.apache.org/dev/ pages. Important is e.g. that we do
>> checksums and GPG signing. Using maven, you can do most of the stuff
>> using maven dist:deploy if you project has all the small bits and
>> pieces set correctly. You can look at the current 2.3.2-rc to see how
>> to do it.
>>
>> (This whole mail sounds very buerocratic. It shouldn't. The process
>> itself is not at all complicated but it should make sure that we don't
>> distribute anything that we are not allowed to by accident and have to
>> pull releases later).
>>
>>
> Not buerocratic - it is sometimes difficult to find all the bits and
> pieces to make a release ....
>
>> Best regards
>> Henning
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: fulcrum jars @ ibiblio
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Henning,
see my comments below ....
Cheers,
Siegfried Goeschl
Henning P. Schmiedehausen wrote:
>Siegfried Goeschl <si...@it20one.at> writes:
>
>
>
>>PS: What's a "CfV"?!
>>
>>
>
>Geee.. :-)
>
>
>
Argghhh, brain dead while writing a XSLT .... :-)
>A "CfV" is a "Call for Vote". CfV's are mandatory for everything that
>should hit www.apache.org/dist/ at some point.
>
>Ok, so this is how it goes/should go:
>
>We can develop and work all we want. However, if we decide that a
>certain version should be "official" or hit the ASF infrastructure, we
>have the following options:
>
>There is the "unofficial turbine maven repository" at
>http://jakarta.apache.org/turbine/repo/ which has been invented to get
>around the "upload to ibiblio" headaches a long time ago.
>
>This repo works with a delay of two hours as it is mirrored onto the
>delivery server from minotaur.
>
>There is also the official way on how to deal with non-released
>versions which is to go through http://cvs.apache.org/dist/
>(.../jakarta/turbine in our case.) This location is _intended_ to be
>used for snapshots, nightlies, rc's, alphas, betas and so on.
>
>You can find more information about that on
>http://www.apache.org/dev/release.html
>
>For the current 2.3 RC's and META RC's, I've created
>http://cvs.apache.org/dist/jakarta/turbine/java-repository which we
>can use as our repo. This has also the advantage that there is no two
>hour lag to the delivery servers.
>
>The official releases go into www.apache.org/dist. This is the
>location that is picked up by the apache mirror system and distributes
>the releases all over the world. Due to this fact, it is very
>important to make sure that a release confirms to the official ASF
>guidelines.
>
>When we want to 'officially' publish releases of components, the core
>or anything else, we must hold a vote, send this vote to the PMC for
>approval and then do "official" publishing as described at the various
>http://www.apache.org/dev/ pages. Important is e.g. that we do
>checksums and GPG signing. Using maven, you can do most of the stuff
>using maven dist:deploy if you project has all the small bits and
>pieces set correctly. You can look at the current 2.3.2-rc to see how
>to do it.
>
>(This whole mail sounds very buerocratic. It shouldn't. The process
>itself is not at all complicated but it should make sure that we don't
>distribute anything that we are not allowed to by accident and have to
>pull releases later).
>
>
Not buerocratic - it is sometimes difficult to find all the bits and
pieces to make a release ....
> Best regards
> Henning
>
>
>
Re: fulcrum jars @ ibiblio
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Siegfried Goeschl <si...@it20one.at> writes:
>PS: What's a "CfV"?!
Geee.. :-)
A "CfV" is a "Call for Vote". CfV's are mandatory for everything that
should hit www.apache.org/dist/ at some point.
Ok, so this is how it goes/should go:
We can develop and work all we want. However, if we decide that a
certain version should be "official" or hit the ASF infrastructure, we
have the following options:
There is the "unofficial turbine maven repository" at
http://jakarta.apache.org/turbine/repo/ which has been invented to get
around the "upload to ibiblio" headaches a long time ago.
This repo works with a delay of two hours as it is mirrored onto the
delivery server from minotaur.
There is also the official way on how to deal with non-released
versions which is to go through http://cvs.apache.org/dist/
(.../jakarta/turbine in our case.) This location is _intended_ to be
used for snapshots, nightlies, rc's, alphas, betas and so on.
You can find more information about that on
http://www.apache.org/dev/release.html
For the current 2.3 RC's and META RC's, I've created
http://cvs.apache.org/dist/jakarta/turbine/java-repository which we
can use as our repo. This has also the advantage that there is no two
hour lag to the delivery servers.
The official releases go into www.apache.org/dist. This is the
location that is picked up by the apache mirror system and distributes
the releases all over the world. Due to this fact, it is very
important to make sure that a release confirms to the official ASF
guidelines.
When we want to 'officially' publish releases of components, the core
or anything else, we must hold a vote, send this vote to the PMC for
approval and then do "official" publishing as described at the various
http://www.apache.org/dev/ pages. Important is e.g. that we do
checksums and GPG signing. Using maven, you can do most of the stuff
using maven dist:deploy if you project has all the small bits and
pieces set correctly. You can look at the current 2.3.2-rc to see how
to do it.
(This whole mail sounds very buerocratic. It shouldn't. The process
itself is not at all complicated but it should make sure that we don't
distribute anything that we are not allowed to by accident and have to
pull releases later).
Best regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +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
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: fulcrum jars @ ibiblio
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Henning,
I uploaded the JARs to the internal Turbine repo which is definitely not
the proper way - I upload the libraries to
www.apache.org/dist/java-repository tommorrow since I'm currently at a
customer site.
Cheers,
Siegfried Goeschl
PS: What's a "CfV"?!
Henning P. Schmiedehausen wrote:
>Hi,
>
>[fulcrum-yaafi 1.0.4 is missing, that's how I came here...]
>
>there are a number of jars mirrored from
>www.apache.org/dist/java-repository up to ibiblio. The Apache
>guidelines require us to actually run CfV's whenever we put stuff
>there, so we might want to make sure that we adhere to these
>guidelines. Having a number of official releases will also help us
>with visibility.
>
> Best regards
> Henning
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org