You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by James Mitchell <jm...@apache.org> on 2003/07/21 02:58:23 UTC
Re: [Resources] When is the next release?
Unless I did something wrong, my search for issues on bugzilla turns up
nothing, and I'm not sure what to make of <issueTrackingUrl> in project.xml.
Does it mean that we should be using
http://nagoya.apache.org/scarab/servlet/scarab/ or is it something that was
just carried over when someone was creating this file?
Using Maven to build and run the tests on this project fails.
* Running "ant test" (with appropriate build.properties) will compile and
test fine.
* Running "maven" will compile fine, but does not copy the required
.properties and
.xml files needed by the tests.
I don't know enough about Maven to determine whether this is configuration
issue or a bug.
So, with that out of the way, what exactly is stopping us from releasing
commons-resources?
Do we need more tests? Is there a checklist somewhere that I'm missing?
--
James Mitchell
Software Developer/Struts Evangelist
http://www.struts-atlanta.org
678-910-8017
AIM:jmitchtx
----- Original Message -----
From: "Steve Peterson" <st...@zpfe.com>
To: "Struts Developers List" <st...@jakarta.apache.org>
Sent: Saturday, July 19, 2003 5:16 PM
Subject: RE: When is the next release?
> What needs to happen to get commons-resources out of the sandbox? I may
> have some time in the next week or two to contribute.
>
> Steve
>
> \At 05:05 PM 7/14/2003 -0700, David Graham wrote:
> >--- James Turner <tu...@blackbear.com> wrote:
> > > >David Graham wrote:
> > > > The plan all along was that 1.2.0 would include a move to
> > > > commons-resources and no other major changes. However,
> > > > commons-resources is still in the sandbox so I suggest we
> > > > postpone that move to the next release. I've committed all
> > > > of my interesting changes for 1.2.0 so I'd like to hear the
> > > > status on the nested and tiles bugs plus the one Martin has
> > > > assigned to himself. Also, is the validwhen vaildation working?
> > > >
> > >
> > > Well, validWhen is checked into the release, and it's the same code
I'm
> > > using on a live customer site, so my belief is that it is. We won't
> > > know how well it works until more users try it out and find bugs, but
> > > that's the nice thing about more frequent release cycles, right?
> >
> >I was just making sure there wasn't more to be done on it before a
> >release. Hopefully it will help alleviate all the questions on
requiredif
> >:-).
> >
> >David
> >
> > >
> > > James
> > >
> > >
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >SBC Yahoo! DSL - Now only $29.95 per month!
> >http://sbc.yahoo.com
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Resources] When is the next release?
Posted by Joe Germuska <Jo...@Germuska.com>.
>1) The action items in STATUS.html need to be addressed. The first (Review
>Abstractions) is especially important, since we need to set the right
>"tone" for Resources before it goes out into the big wide world as an
>official release. IMNSHO, there is still some serious work needed here
>(which I'm willing to contribute to).
Is there (or can you offer) a summary of the issues?
I am using commons-resources in a modest fashion in one project now,
and it works fine for what I need, but I wouldn't claim to have used
it in a way which would have flushed out architectural limitations.
Joe
--
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"If nature worked that way, the universe would crash all the time."
--Jaron Lanier
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Resources] When is the next release?
Posted by Joe Germuska <Jo...@Germuska.com>.
>1) The action items in STATUS.html need to be addressed. The first (Review
>Abstractions) is especially important, since we need to set the right
>"tone" for Resources before it goes out into the big wide world as an
>official release. IMNSHO, there is still some serious work needed here
>(which I'm willing to contribute to).
Is there (or can you offer) a summary of the issues?
I am using commons-resources in a modest fashion in one project now,
and it works fine for what I need, but I wouldn't claim to have used
it in a way which would have flushed out architectural limitations.
Joe
--
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"If nature worked that way, the universe would crash all the time."
--Jaron Lanier
Re: [Resources] When is the next release?
Posted by David Graham <gr...@yahoo.com>.
--- Martin Cooper <ma...@apache.org> wrote:
> Here are a few things that need to happen:
>
> 1) The action items in STATUS.html need to be addressed. The first
> (Review
> Abstractions) is especially important, since we need to set the right
> "tone" for Resources before it goes out into the big wide world as an
> official release. IMNSHO, there is still some serious work needed here
> (which I'm willing to contribute to).
Specifically, we should change the MessageList methods that return an
Iterator. They need more descriptive names and should return some form of
Collection (or Collection view). Getting an Iterator from a method isn't
a common Java idiom (for good reason) and the client can do more with a
Collection anyways. I think the Iterator business was carried over from
the Struts Validator.
David
>
> 2) It looks like the build process needs to be sorted out. Currently,
> this
> appears to be in a no-mans land, with a manually constructed Ant build
> file, and a partially functional Maven build file. My preference would
> be
> to move to a Maven build with a generated Ant build file. This really
> makes the release process easier, and makes updating the web site a
> snap.
>
> 3) Once we feel that the overall architecture is in place, and the code
> is
> in pretty good shape for a release, then we need to propose a vote to
> move
> Resources out of the sandbox and into Commons Proper.
>
> 4) After we get to Commons Proper, we need to go through Beta and
> Release
> Candidate stages to make sure we're addressing the needs of those
> clients
> who will pick us up in Proper who would not have paid attention to us in
> the Sandbox. (My experience with other Commons components has taught me
> just how important this is to a successful release.)
>
> It's really important to realise that a lack of bug reports does not
> mean
> the software is ready for a public release, especially when that
> software
> is in the sandbox. The sandbox is a playground for experimentation, and
> lots of (potentially drastic) changes can happen before the component is
> deemed ready for public consumption.
>
> Don't get me wrong - I would really like to see a Resources 1.0 release.
> In fact, I'd be quite happy to be the Release Manager for it. I just
> think
> we have some work ahead of us before we're ready for that.
>
> --
> Martin Cooper
>
>
> On Mon, 4 Aug 2003, Rob Leland wrote:
>
> > James Mitchell wrote:
> >
> > >Unless I did something wrong, my search for issues on bugzilla turns
> up
> > >nothing, and I'm not sure what to make of <issueTrackingUrl> in
> project.xml.
> > >Does it mean that we should be using
> > >http://nagoya.apache.org/scarab/servlet/scarab/ or is it something
> that was
> > >just carried over when someone was creating this file?
> > >
> > >Using Maven to build and run the tests on this project fails.
> > > * Running "ant test" (with appropriate build.properties) will
> compile and
> > >test fine.
> > > * Running "maven" will compile fine, but does not copy the required
> > >.properties and
> > > .xml files needed by the tests.
> > >
> > >I don't know enough about Maven to determine whether this is
> configuration
> > >issue or a bug.
> > >
> > >So, with that out of the way, what exactly is stopping us from
> releasing
> > >commons-resources?
> > >Do we need more tests? Is there a checklist somewhere that I'm
> missing?
> > >
> > >
> > >
> > James:
> >
> > Did anyone reply to this message, as to what needs to be done for a
> > release ?
> >
> >
> >
> >
> > --
> > -----
> > Rob Leland (703-525-3580)
> >
> >
> > Choose a job you love, and you will never have to work a day of your
> life.
> >
> -Confucius.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Re: [Resources] When is the next release?
Posted by David Graham <gr...@yahoo.com>.
--- Martin Cooper <ma...@apache.org> wrote:
> Here are a few things that need to happen:
>
> 1) The action items in STATUS.html need to be addressed. The first
> (Review
> Abstractions) is especially important, since we need to set the right
> "tone" for Resources before it goes out into the big wide world as an
> official release. IMNSHO, there is still some serious work needed here
> (which I'm willing to contribute to).
Specifically, we should change the MessageList methods that return an
Iterator. They need more descriptive names and should return some form of
Collection (or Collection view). Getting an Iterator from a method isn't
a common Java idiom (for good reason) and the client can do more with a
Collection anyways. I think the Iterator business was carried over from
the Struts Validator.
David
>
> 2) It looks like the build process needs to be sorted out. Currently,
> this
> appears to be in a no-mans land, with a manually constructed Ant build
> file, and a partially functional Maven build file. My preference would
> be
> to move to a Maven build with a generated Ant build file. This really
> makes the release process easier, and makes updating the web site a
> snap.
>
> 3) Once we feel that the overall architecture is in place, and the code
> is
> in pretty good shape for a release, then we need to propose a vote to
> move
> Resources out of the sandbox and into Commons Proper.
>
> 4) After we get to Commons Proper, we need to go through Beta and
> Release
> Candidate stages to make sure we're addressing the needs of those
> clients
> who will pick us up in Proper who would not have paid attention to us in
> the Sandbox. (My experience with other Commons components has taught me
> just how important this is to a successful release.)
>
> It's really important to realise that a lack of bug reports does not
> mean
> the software is ready for a public release, especially when that
> software
> is in the sandbox. The sandbox is a playground for experimentation, and
> lots of (potentially drastic) changes can happen before the component is
> deemed ready for public consumption.
>
> Don't get me wrong - I would really like to see a Resources 1.0 release.
> In fact, I'd be quite happy to be the Release Manager for it. I just
> think
> we have some work ahead of us before we're ready for that.
>
> --
> Martin Cooper
>
>
> On Mon, 4 Aug 2003, Rob Leland wrote:
>
> > James Mitchell wrote:
> >
> > >Unless I did something wrong, my search for issues on bugzilla turns
> up
> > >nothing, and I'm not sure what to make of <issueTrackingUrl> in
> project.xml.
> > >Does it mean that we should be using
> > >http://nagoya.apache.org/scarab/servlet/scarab/ or is it something
> that was
> > >just carried over when someone was creating this file?
> > >
> > >Using Maven to build and run the tests on this project fails.
> > > * Running "ant test" (with appropriate build.properties) will
> compile and
> > >test fine.
> > > * Running "maven" will compile fine, but does not copy the required
> > >.properties and
> > > .xml files needed by the tests.
> > >
> > >I don't know enough about Maven to determine whether this is
> configuration
> > >issue or a bug.
> > >
> > >So, with that out of the way, what exactly is stopping us from
> releasing
> > >commons-resources?
> > >Do we need more tests? Is there a checklist somewhere that I'm
> missing?
> > >
> > >
> > >
> > James:
> >
> > Did anyone reply to this message, as to what needs to be done for a
> > release ?
> >
> >
> >
> >
> > --
> > -----
> > Rob Leland (703-525-3580)
> >
> >
> > Choose a job you love, and you will never have to work a day of your
> life.
> >
> -Confucius.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Resources] When is the next release?
Posted by Martin Cooper <ma...@apache.org>.
Here are a few things that need to happen:
1) The action items in STATUS.html need to be addressed. The first (Review
Abstractions) is especially important, since we need to set the right
"tone" for Resources before it goes out into the big wide world as an
official release. IMNSHO, there is still some serious work needed here
(which I'm willing to contribute to).
2) It looks like the build process needs to be sorted out. Currently, this
appears to be in a no-mans land, with a manually constructed Ant build
file, and a partially functional Maven build file. My preference would be
to move to a Maven build with a generated Ant build file. This really
makes the release process easier, and makes updating the web site a snap.
3) Once we feel that the overall architecture is in place, and the code is
in pretty good shape for a release, then we need to propose a vote to move
Resources out of the sandbox and into Commons Proper.
4) After we get to Commons Proper, we need to go through Beta and Release
Candidate stages to make sure we're addressing the needs of those clients
who will pick us up in Proper who would not have paid attention to us in
the Sandbox. (My experience with other Commons components has taught me
just how important this is to a successful release.)
It's really important to realise that a lack of bug reports does not mean
the software is ready for a public release, especially when that software
is in the sandbox. The sandbox is a playground for experimentation, and
lots of (potentially drastic) changes can happen before the component is
deemed ready for public consumption.
Don't get me wrong - I would really like to see a Resources 1.0 release.
In fact, I'd be quite happy to be the Release Manager for it. I just think
we have some work ahead of us before we're ready for that.
--
Martin Cooper
On Mon, 4 Aug 2003, Rob Leland wrote:
> James Mitchell wrote:
>
> >Unless I did something wrong, my search for issues on bugzilla turns up
> >nothing, and I'm not sure what to make of <issueTrackingUrl> in project.xml.
> >Does it mean that we should be using
> >http://nagoya.apache.org/scarab/servlet/scarab/ or is it something that was
> >just carried over when someone was creating this file?
> >
> >Using Maven to build and run the tests on this project fails.
> > * Running "ant test" (with appropriate build.properties) will compile and
> >test fine.
> > * Running "maven" will compile fine, but does not copy the required
> >.properties and
> > .xml files needed by the tests.
> >
> >I don't know enough about Maven to determine whether this is configuration
> >issue or a bug.
> >
> >So, with that out of the way, what exactly is stopping us from releasing
> >commons-resources?
> >Do we need more tests? Is there a checklist somewhere that I'm missing?
> >
> >
> >
> James:
>
> Did anyone reply to this message, as to what needs to be done for a
> release ?
>
>
>
>
> --
> -----
> Rob Leland (703-525-3580)
>
>
> Choose a job you love, and you will never have to work a day of your life.
> -Confucius.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Resources] When is the next release?
Posted by Martin Cooper <ma...@apache.org>.
Here are a few things that need to happen:
1) The action items in STATUS.html need to be addressed. The first (Review
Abstractions) is especially important, since we need to set the right
"tone" for Resources before it goes out into the big wide world as an
official release. IMNSHO, there is still some serious work needed here
(which I'm willing to contribute to).
2) It looks like the build process needs to be sorted out. Currently, this
appears to be in a no-mans land, with a manually constructed Ant build
file, and a partially functional Maven build file. My preference would be
to move to a Maven build with a generated Ant build file. This really
makes the release process easier, and makes updating the web site a snap.
3) Once we feel that the overall architecture is in place, and the code is
in pretty good shape for a release, then we need to propose a vote to move
Resources out of the sandbox and into Commons Proper.
4) After we get to Commons Proper, we need to go through Beta and Release
Candidate stages to make sure we're addressing the needs of those clients
who will pick us up in Proper who would not have paid attention to us in
the Sandbox. (My experience with other Commons components has taught me
just how important this is to a successful release.)
It's really important to realise that a lack of bug reports does not mean
the software is ready for a public release, especially when that software
is in the sandbox. The sandbox is a playground for experimentation, and
lots of (potentially drastic) changes can happen before the component is
deemed ready for public consumption.
Don't get me wrong - I would really like to see a Resources 1.0 release.
In fact, I'd be quite happy to be the Release Manager for it. I just think
we have some work ahead of us before we're ready for that.
--
Martin Cooper
On Mon, 4 Aug 2003, Rob Leland wrote:
> James Mitchell wrote:
>
> >Unless I did something wrong, my search for issues on bugzilla turns up
> >nothing, and I'm not sure what to make of <issueTrackingUrl> in project.xml.
> >Does it mean that we should be using
> >http://nagoya.apache.org/scarab/servlet/scarab/ or is it something that was
> >just carried over when someone was creating this file?
> >
> >Using Maven to build and run the tests on this project fails.
> > * Running "ant test" (with appropriate build.properties) will compile and
> >test fine.
> > * Running "maven" will compile fine, but does not copy the required
> >.properties and
> > .xml files needed by the tests.
> >
> >I don't know enough about Maven to determine whether this is configuration
> >issue or a bug.
> >
> >So, with that out of the way, what exactly is stopping us from releasing
> >commons-resources?
> >Do we need more tests? Is there a checklist somewhere that I'm missing?
> >
> >
> >
> James:
>
> Did anyone reply to this message, as to what needs to be done for a
> release ?
>
>
>
>
> --
> -----
> Rob Leland (703-525-3580)
>
>
> Choose a job you love, and you will never have to work a day of your life.
> -Confucius.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
Re: [Resources] When is the next release?
Posted by Rob Leland <rl...@apache.org>.
James Mitchell wrote:
>Unless I did something wrong, my search for issues on bugzilla turns up
>nothing, and I'm not sure what to make of <issueTrackingUrl> in project.xml.
>Does it mean that we should be using
>http://nagoya.apache.org/scarab/servlet/scarab/ or is it something that was
>just carried over when someone was creating this file?
>
>Using Maven to build and run the tests on this project fails.
> * Running "ant test" (with appropriate build.properties) will compile and
>test fine.
> * Running "maven" will compile fine, but does not copy the required
>.properties and
> .xml files needed by the tests.
>
>I don't know enough about Maven to determine whether this is configuration
>issue or a bug.
>
>So, with that out of the way, what exactly is stopping us from releasing
>commons-resources?
>Do we need more tests? Is there a checklist somewhere that I'm missing?
>
>
>
James:
Did anyone reply to this message, as to what needs to be done for a
release ?
--
-----
Rob Leland (703-525-3580)
Choose a job you love, and you will never have to work a day of your life.
-Confucius.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Resources] When is the next release?
Posted by Rob Leland <rl...@apache.org>.
James Mitchell wrote:
>Unless I did something wrong, my search for issues on bugzilla turns up
>nothing, and I'm not sure what to make of <issueTrackingUrl> in project.xml.
>Does it mean that we should be using
>http://nagoya.apache.org/scarab/servlet/scarab/ or is it something that was
>just carried over when someone was creating this file?
>
>Using Maven to build and run the tests on this project fails.
> * Running "ant test" (with appropriate build.properties) will compile and
>test fine.
> * Running "maven" will compile fine, but does not copy the required
>.properties and
> .xml files needed by the tests.
>
>I don't know enough about Maven to determine whether this is configuration
>issue or a bug.
>
>So, with that out of the way, what exactly is stopping us from releasing
>commons-resources?
>Do we need more tests? Is there a checklist somewhere that I'm missing?
>
>
>
James:
Did anyone reply to this message, as to what needs to be done for a
release ?
--
-----
Rob Leland (703-525-3580)
Choose a job you love, and you will never have to work a day of your life.
-Confucius.