ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Toni Menzel <t...@okidokiteam.com>
Subject Re: Next release
Date Thu, 24 Nov 2011 12:01:45 GMT
Finally you make your intend clear. Why not say so right from start?
Back to the topic: its up to the community to decide if the project knows
Apache rules or not. Looking at the commiter list i see quite some apache
veterans.  So i understand your (still valid but solved) complains are just
political ramblings on an apache list ?
On Nov 24, 2011 12:26 PM, "ant elder" <antelder@apache.org> wrote:

> Well personally i'd like to see more than that. To graduate the
> poddling should demonstrate it knows how to do ASF releases, the 0.8.0
> release had some problems and it didn't demonstrate that, so now i
> think it needs to be shown how thats going to be fixed, just saying
> don't worry it will be fixed later isn't enough IMHO.
>
>   ...ant
>
> On Thu, Nov 24, 2011 at 10:59 AM, Toni Menzel <toni@okidokiteam.com>
> wrote:
> > Ant,  thanks for your suggestions. You can be of great help when we will
> do
> > our next release. We also have maven experts on board, so I'm sure we
> know
> > what to do and we will raise possible issues when it is about time.
> > Hope this is ok?
> > Thanks, Toni
> > On Nov 24, 2011 10:12 AM, "ant elder" <ant.elder@gmail.com> wrote:
> >
> >> On Wed, Nov 23, 2011 at 8:14 PM, Karl Pauls <karlpauls@gmail.com>
> wrote:
> >> > On Wed, Nov 23, 2011 at 8:39 PM, Marcel Offermans
> >> > <marcel.offermans@luminis.nl> wrote:
> >> >> +1, I think providing such a script is a good way to do it, it makes
> >> checking and building the individual components a lot easier whilst
> still
> >> maintaining the flexibility of being able to release any subset of
> >> artifacts. I also agree that we should correct the oversight of not
> >> shipping the pom.xml file as part of the source distribution for future
> >> releases.
> >> >
> >> > Yeah, again, that is just a configuration we have to set so that it
> >> > not only generates the -sources.jar but also the -project.{zip,tar.gz}
> >> > just like we do at felix. Without that (and there I totally agree with
> >> > ant and sebb on this one), it sucks rocks as you have to massage the
> >> > stuff quite a bit to get it to work and don't even have the tests,
> >> > etc. :-(.
> >> >
> >> > I think having the -projects plus the two scripts are a good way to go
> >> > (technically, its close to releasing the reactor pom - which would be
> >> > even easier -  but this way, we don't have to tag the trunk).
> >>
> >> If having the reactor pom would be even easier then why not do that?
> >>
> >> This isn't just about making it possible for reviewers to easily build
> >> the release when voting its about having a source release that you can
> >> actually use to do development on the code. If you don't release the
> >> recator pom then for example how do you set up the source in a IDE -
> >> you'd have to manually go into each artifact any type something like
> >> mvn eclipse:eclipse, and even then that would give isolated eclipse
> >> projects so IDE refactoring wouldn't go across the projects and IDE
> >> changes in one project wouldn't be picked up until after a maven build
> >> was done and the projects refreshed, so really not a very practical
> >> approach.
> >>
> >>   ...ant
> >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message