OK, replying to myself
I found in D2 of CreatingReleases:
"If vote fails, undo and redo previous steps as appropriate (make sure
SVN tag is deleted before recreating). And rest assured that most
releases need more than one release candidate ..."
I am assuming that the process with the tag na
Matt Benson wrote at Dienstag, 12. Mai 2009 15:11:
>
>
>
> --- On Tue, 5/12/09, Jörg Schaible wrote:
>
>> From: Jörg Schaible
>> Subject: Re: [all] Core library dependencies [was COLLECTIONS 3.3
>> release] To: dev@commons.apache.org
>> Date: Tuesday, May 12, 2009, 7:54 AM
>> John Bollinger
James Carman wrote at Mittwoch, 13. Mai 2009 04:30:
> On Tue, May 12, 2009 at 9:38 PM, Dan Fabulich wrote:
>> If you feel like you'd want to call it "lang2" or "lang-ng" then just
>> call it lang 2.0 or 3.0 or whatever and keep a lang-1.x branch around for
>> stability fixes.
>
> I thought we ag
On Tue, May 12, 2009 at 8:57 PM, James Carman
wrote:
> We could probably use the release plugin to create a branch for each
> rc, right? Then, run the release process off that branch and it'll
> create the correct tag.
How can one configure this? I think it can be done somehow in th
eparent pom
On Tue, May 12, 2009 at 7:41 PM, Dan Fabulich wrote:
> When I ran it, the release plugin prompted me for the tag name to create.
> Rather than accept defaults, I manually typed in the appropriate tag name.
OK, will try the same now, but at dbutils its only one tag availabe
even if you did some mo
On Tue, May 12, 2009 at 9:38 PM, Dan Fabulich wrote:
> If you feel like you'd want to call it "lang2" or "lang-ng" then just call
> it lang 2.0 or 3.0 or whatever and keep a lang-1.x branch around for
> stability fixes.
I thought we agreed that we would "jump" major version numbers (as you
sugges
Gary Gregory wrote:
Ah, em, we cannot do exactly that of course but the idea is that a new
project/version can reflect two ideas: A new JRE requirement and/or a
new implementation of the project SO different to warrant a new project.
I also don't like "-ng" or even "blah2".
Specifically, I d
> -Original Message-
> From: Gary Gregory [mailto:ggreg...@seagullsoftware.com]
> Sent: Tuesday, May 12, 2009 6:19 PM
> To: Commons Developers List
> Subject: RE: [all] Rebooting commons projects
>
> > -Original Message-
> > From: James Carman [mailto:ja...@carmanconsulting.com]
>
> -Original Message-
> From: James Carman [mailto:ja...@carmanconsulting.com]
> Sent: Tuesday, May 12, 2009 5:33 PM
> To: Commons Developers List
> Subject: Re: [all] Rebooting commons projects
>
> On Tue, May 12, 2009 at 7:12 PM, Stephen Colebourne
> wrote:
> >
> > Lets also say that the
On Tue, May 12, 2009 at 7:12 PM, Stephen Colebourne
wrote:
>
> Lets also say that the new project name cannot be numerically based, so no
> [lang2] or [lang5] projects, thats way too confusing. But [lang-ng] would be
> ok.
And, when we want to "reboot" again, we name it [lang-nng]?
-
On May 12, 2009, at 4:12 PM, Stephen Colebourne wrote:
Every so often, projects need to "reboot". Its healthy and useful,
as most developers want innovate rather than maintain.
Up until now, we've tried to do this within the existing project.
Its failed miserably.
So, lets just accept
Henri Yandell wrote:
+1 to Stephen on backwards compat (which is probably surprising given
how much I argue with him on that subject).
I agree with it - but it frustrates me immensely due to the sheer
damage I think it does to a project. I'm of the opinion nowadays that
in a project there are tw
Matt Benson wrote:
What [functor] needs is the confidence to stand up and say
"hey, come and use me, here's what I offer".
I somewhat resent the implication that I and others might be trying to buffalo
> [functor] into "proper" status, but I'm known for paranoia, so forgive me
> if I've read mo
James Carman wrote:
On Tue, May 12, 2009 at 7:29 AM, Stephen Colebourne
wrote:
The 'functors' in [collections] and [functor] are very different:
I would argue that they're not inherently different, though. A
Predicate in collections-speak is the same thing as a UnaryPredicate
in functor-spea
On 12/05/2009, Niall Pemberton wrote:
> On Tue, May 12, 2009 at 8:14 PM, sebb wrote:
> > On 12/05/2009, Niall Pemberton wrote:
> >> On Mon, May 11, 2009 at 8:26 AM, Jochen Wiedmann
> >>
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > as I have absolutely no idea about OSGI: Can anyone confi
On Tue, May 12, 2009 at 8:14 PM, sebb wrote:
> On 12/05/2009, Niall Pemberton wrote:
>> On Mon, May 11, 2009 at 8:26 AM, Jochen Wiedmann
>>
>> wrote:
>>
>> > Hi,
>> >
>> > as I have absolutely no idea about OSGI: Can anyone confirm or deny
>> > this statement from the bug report:
>>
>>
>> I d
On 12/05/2009, Niall Pemberton wrote:
> On Mon, May 11, 2009 at 8:26 AM, Jochen Wiedmann
>
> wrote:
>
> > Hi,
> >
> > as I have absolutely no idea about OSGI: Can anyone confirm or deny
> > this statement from the bug report:
>
>
> I don't know if its an error or not and whether its fixed in a
We could probably use the release plugin to create a branch for each
rc, right? Then, run the release process off that branch and it'll
create the correct tag.
On Tue, May 12, 2009 at 1:41 PM, Dan Fabulich wrote:
> When I ran it, the release plugin prompted me for the tag name to create.
> Rathe
On Mon, May 11, 2009 at 8:26 AM, Jochen Wiedmann
wrote:
> Hi,
>
> as I have absolutely no idea about OSGI: Can anyone confirm or deny
> this statement from the bug report:
I don't know if its an error or not and whether its fixed in a later
version of the maven-bundle-plugin or not. I'll ask on t
On Mon, May 11, 2009 at 1:45 PM, sebb wrote:
> On 11/05/2009, Christian Grobmeier wrote:
>> Hi all,
>>
>> as already discussed, I just created a RC1 for the first [compress] release
>> :-)
>> Let me know if you can find any problems.
>>
>> Cheers,
>> Christian
>>
>>
>> Tag:
>>
>> https://
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-compress has an issue affecting its community integration.
This is
When I ran it, the release plugin prompted me for the tag name to create.
Rather than accept defaults, I manually typed in the appropriate tag name.
-Dan
Christian Grobmeier wrote:
Hi,
currently the
mvn -Prc release:perform
creates a tag with the release name instead of f.e. commons-compress
On Tue, May 12, 2009 at 7:29 AM, Stephen Colebourne
wrote:
> The 'functors' in [collections] and [functor] are very different:
> http://commons.apache.org/collections/api-release/org/apache/commons/collections/package-summary.html
> http://commons.apache.org/sandbox/functor/apidocs/org/apache/comm
--- On Tue, 5/12/09, Stephen Colebourne wrote:
> From: Stephen Colebourne
> Subject: Re: [all] Core library dependencies [was COLLECTIONS 3.3 release]
> To: "Commons Developers List"
> Date: Tuesday, May 12, 2009, 6:29 AM
>
> From: John Bollinger
> > Which is exactly why Collections should
--- On Tue, 5/12/09, Jörg Schaible wrote:
> From: Jörg Schaible
> Subject: Re: [all] Core library dependencies [was COLLECTIONS 3.3 release]
> To: dev@commons.apache.org
> Date: Tuesday, May 12, 2009, 7:54 AM
> John Bollinger wrote at Dienstag, 12.
> Mai 2009 14:19:
>
> >
> >
> > Stephen C
On 12/05/2009, Jörg Schaible wrote:
> sebb wrote at Dienstag, 12. Mai 2009 13:47:
>
>
> > On 12/05/2009, Jörg Schaible wrote:
> >> sebb wrote at Dienstag, 12. Mai 2009 11:22:
> >>
> >> [snip]
> >>
> >>
> >> > One other change needed to SVN:
> >> >
> >> > svn ps svn:eol-style native
>
John Bollinger wrote at Dienstag, 12. Mai 2009 14:19:
>
>
> Stephen Colebourne wrote:
>> The 'functors' in [collections] and [functor] are very different:
>
> Thanks for clearing that up. It obviously moots my argument as it applies
> to Collections / Functor, though I think the distinction be
sebb wrote at Dienstag, 12. Mai 2009 13:47:
> On 12/05/2009, Jörg Schaible wrote:
>> sebb wrote at Dienstag, 12. Mai 2009 11:22:
>>
>> [snip]
>>
>>
>> > One other change needed to SVN:
>> >
>> > svn ps svn:eol-style native
>> >
src/main/java/org/apache/commons/compress/changes/ChangeSetResul
On 12/05/2009, Christian Grobmeier wrote:
> >> > Yes, I know; the original instructions (shown as outdated, at the
> >> > bottom) imply that it is possible; seems to me it would be a lot
> >> > better.
> >>
> >>
> >> No its not outdated - just the last paragraph is outdated by the above
>
Stephen Colebourne wrote:
> The 'functors' in [collections] and [functor] are very different:
Thanks for clearing that up. It obviously moots my argument as it applies
to Collections / Functor, though I think the distinction between private
dependencies and public ones is still generally releva
>> > Yes, I know; the original instructions (shown as outdated, at the
>> > bottom) imply that it is possible; seems to me it would be a lot
>> > better.
>>
>>
>> No its not outdated - just the last paragraph is outdated by the above
>> writings:
>
> That's what I meant - the last para is marke
On 12/05/2009, Christian Grobmeier wrote:
> >> I think similar, but this has been done automatically when following:
> >> http://wiki.apache.org/commons/CreatingReleases
> >
> > Yes, I know; the original instructions (shown as outdated, at the
> > bottom) imply that it is possible; seems to m
On 12/05/2009, Jörg Schaible wrote:
> sebb wrote at Dienstag, 12. Mai 2009 11:22:
>
> [snip]
>
>
> > One other change needed to SVN:
> >
> > svn ps svn:eol-style native
> > src/main/java/org/apache/commons/compress/changes/ChangeSetResults.java
> > svn ps svn:eol-style native src/site/xdoc/d
From: John Bollinger
> Which is exactly why Collections should not copy Functor. Either Functor
> should be absorbed back into Collections, or Collections should have
> Functor as a dependency, for otherwise users must maintain separate
> functors for use with Collections and for other purposes.
Hi,
currently the
mvn -Prc release:perform
creates a tag with the release name instead of f.e. commons-compress-1_0-RC1.
1) Do I have to remove the tag commons-compress-1_0 manually when
doing a second release candidate? Just want to make sure, don't want
to break the rules.
2) Is it really good
>> I think similar, but this has been done automatically when following:
>> http://wiki.apache.org/commons/CreatingReleases
>
> Yes, I know; the original instructions (shown as outdated, at the
> bottom) imply that it is possible; seems to me it would be a lot
> better.
No its not outdated - just
sebb wrote at Dienstag, 12. Mai 2009 11:22:
[snip]
> One other change needed to SVN:
>
> svn ps svn:eol-style native
> src/main/java/org/apache/commons/compress/changes/ChangeSetResults.java
> svn ps svn:eol-style native src/site/xdoc/download_compress.xml
> svn ps svn:eol-style native
>
src/tes
On 12/05/2009, Christian Grobmeier wrote:
> >> Tag:
> >>
> https://svn.apache.org/repos/asf/commons/proper/compress/tags/commons-compress-1.0/
> >
> > I don't like the use of final tag names for release candidates; tags
> > should be immutable, so how can one generate another release candid
38 matches
Mail list logo
