On 14/10/2013 02:55, Henri Yandell wrote:
On Tuesday, October 8, 2013, Benedikt Ritter wrote:
Hi,
one of the points that seem to always come up once in a while is the
process of releasing components. I've never done it myself so I'm asking
people who have done it:
I find myself
On 14/10/2013 05:26, Stefan Bodewig wrote:
On 2013-10-14, sebb wrote:
On 9 October 2013 05:43, Stefan Bodewig bode...@apache.org wrote:
why vote on Nexus staged artifacts if the tarball is fine? I'm not
talking about releasing to MC directly but rather about not pushing
anything to Nexus
Le 14/10/2013 07:45, Henri Yandell a écrit :
On Sun, Oct 13, 2013 at 9:12 PM, Phil Steitz phil.ste...@gmail.com wrote:
Could be I am misunderstanding the proposal. Do you mean a) RM is
not obligated to do anything but tag a release and create tarballs
or b) RM should just be trusted to do
Le 14/10/2013 03:55, Henri Yandell a écrit :
I find myself wondering why a release vote is anything more than:
I propose that r6525 of dir be tagged as 3.2. What say ye all?
+1, assuming the revision has almost everything ready for a release (at
least up to date release notes).
That may
On Mon, Oct 14, 2013 at 12:16 AM, Mark Thomas ma...@apache.org wrote:
On 14/10/2013 02:55, Henri Yandell wrote:
On Tuesday, October 8, 2013, Benedikt Ritter wrote:
Hi,
one of the points that seem to always come up once in a while is the
process of releasing components. I've never
On 14/10/2013 09:41, Henri Yandell wrote:
On Mon, Oct 14, 2013 at 12:16 AM, Mark Thomas ma...@apache.org wrote:
On 14/10/2013 02:55, Henri Yandell wrote:
On Tuesday, October 8, 2013, Benedikt Ritter wrote:
Hi,
one of the points that seem to always come up once in a while is the
process
On 9 October 2013 05:43, Stefan Bodewig bode...@apache.org wrote:
On 2013-10-08, Benedikt Ritter wrote:
you are involved in other projects (like log4j2) how do they do it? Is
it easier to release log4j2 than it is to release for example [lang]?
Over the past year I've cut releases at the ASF
On Tuesday, October 8, 2013, Benedikt Ritter wrote:
Hi,
one of the points that seem to always come up once in a while is the
process of releasing components. I've never done it myself so I'm asking
people who have done it:
I find myself wondering why a release vote is anything more than:
On Mon, Oct 14, 2013 at 2:55 AM, Henri Yandell flame...@gmail.com wrote:
I propose release votes be simple revision based requests and involve no
artifact churn :)
Hen,
This is a pretty good idea.
But I still think that artifact churn will be a necessary process in order
to get enough valid
On 10/13/13 6:55 PM, Henri Yandell wrote:
On Tuesday, October 8, 2013, Benedikt Ritter wrote:
Hi,
one of the points that seem to always come up once in a while is the
process of releasing components. I've never done it myself so I'm asking
people who have done it:
I find myself wondering
On 2013-10-14, sebb wrote:
On 9 October 2013 05:43, Stefan Bodewig bode...@apache.org wrote:
why vote on Nexus staged artifacts if the tarball is fine? I'm not
talking about releasing to MC directly but rather about not pushing
anything to Nexus before the vote on the tarball has passed.
On Sun, Oct 13, 2013 at 7:09 PM, Ted Dunning ted.dunn...@gmail.com wrote:
On Mon, Oct 14, 2013 at 2:55 AM, Henri Yandell flame...@gmail.com wrote:
I propose release votes be simple revision based requests and involve no
artifact churn :)
Hen,
This is a pretty good idea.
But I still
On Sun, Oct 13, 2013 at 9:12 PM, Phil Steitz phil.ste...@gmail.com wrote:
Could be I am misunderstanding the proposal. Do you mean a) RM is
not obligated to do anything but tag a release and create tarballs
or b) RM should just be trusted to do the right thing in getting
stuff published
Hi,
one of the points that seem to always come up once in a while is the
process of releasing components. I've never done it myself so I'm asking
people who have done it:
What are the problems and how can we make releasing easier?
Is the complexity of the parent pom a problem? (Do we really need
Le 08/10/2013 18:46, Benedikt Ritter a écrit :
What are the problems and how can we make releasing easier?
I have a real example with JCI. I get an error when running the release
profile with mvn package -DskipTests -Prelease :
[INFO]
IMO the problems are dealing with Nexus, a web site, and a 'dist'
directory; that THREE things to get just right, none are 100% automated.
With Nexus you have to do some manual steps. If you look at all the
instructions for any commons component, it is long, a combo of manual and
Maven+Nexus magic
Maybe it's a problem with the maven-bundle-plugin. It should generate the
Manifest for you. I'm on my mobile right now and will not have the time to have
a look until tomorrow.
Benedikt
Send from my mobile device
Am 08.10.2013 um 19:25 schrieb Emmanuel Bourg ebo...@apache.org:
Le
Hey Gary,
you are involved in other projects (like log4j2) how do they do it? Is it
easier to release log4j2 than it is to release for example [lang]?
Benedikt
Send from my mobile device
Am 08.10.2013 um 19:52 schrieb Gary Gregory garydgreg...@gmail.com:
IMO the problems are dealing with
Luckily, Ralph handles release manager duties, for which I am
grateful. So I cannot speak to the ease or difficulty of the process
there.
Gary
On Oct 8, 2013, at 14:08, Benedikt Ritter benerit...@gmail.com wrote:
Hey Gary,
you are involved in other projects (like log4j2) how do they do it?
I think I understand what Gary means.
I once wrote down the process to release Apache Portals Application for other
PMC members here:
- http://wiki.apache.org/portals/Applications/Release_Process
I guess the process is almost the same in other projects (log4j2 or possibly
lang).
There are many
On 8 Oct 2013, at 20:07, Benedikt Ritter wrote:
Hey Gary,
you are involved in other projects (like log4j2) how do they do it? Is
it easier to release log4j2 than it is to release for example [lang]?
Check this guide:
http://wiki.apache.org/logging/Log4j2ReleaseGuide
In fact we have an ASF
On 8 October 2013 19:44, Christian Grobmeier grobme...@gmail.com wrote:
On 8 Oct 2013, at 20:07, Benedikt Ritter wrote:
Hey Gary,
you are involved in other projects (like log4j2) how do they do it? Is it
easier to release log4j2 than it is to release for example [lang]?
Check this guide:
On 8 October 2013 19:06, Benedikt Ritter benerit...@gmail.com wrote:
Maybe it's a problem with the maven-bundle-plugin. It should generate the
Manifest for you. I'm on my mobile right now and will not have the time to
have a look until tomorrow.
It's not only the osgi Manifest.
I tried
Do you have included the latest commons parent pom?
2013/10/8 sebb seb...@gmail.com
On 8 October 2013 19:06, Benedikt Ritter benerit...@gmail.com wrote:
Maybe it's a problem with the maven-bundle-plugin. It should generate
the Manifest for you. I'm on my mobile right now and will not have
Yes.
On 8 October 2013 20:40, Benedikt Ritter brit...@apache.org wrote:
Do you have included the latest commons parent pom?
2013/10/8 sebb seb...@gmail.com
On 8 October 2013 19:06, Benedikt Ritter benerit...@gmail.com wrote:
Maybe it's a problem with the maven-bundle-plugin. It should
I wrote the Log4j2 wiki page just so I could remember and repeat the few manual
steps I have to do for each release. The difficulty is getting the bugs out of
the first release. Log4j 2 still has some difficulties though around its build
process primarily because none of us are OSGi experts
On 2013-10-08, Benedikt Ritter wrote:
you are involved in other projects (like log4j2) how do they do it? Is
it easier to release log4j2 than it is to release for example [lang]?
Over the past year I've cut releases at the ASF for Commons Compress,
Ant and log4net and outside of the ASF of a
27 matches
Mail list logo
