On Jan 27, 2007, at 2:01 PM, Henning P. Schmiedehausen wrote:
"Geir Magnusson Jr." <[EMAIL PROTECTED]> writes:
Normally yes - you vote on the final software that's going to be
released, not just the concept.
At the moment, I have no clue what would actually go out the door wrt
the binary (included libs, LICENSE and NOTICE files, etc)
Should be easy.
Hm. That *is* a strong imbalance IMHO between projects that ship docs
as part of their distribution (like we do) and others that simply keep
and update their docs online and ship just e.g. javadocs.
It's not just about docs - it's about the whole thing. How else can
we say we did proper oversight for things such as the license,
copyrights, notices and included 3rd party dependencies when we can't
see it?
In that case, I'd actually like to discuss removing all docs except
automatically created docs from source (e.g. Javadocs, Changelog etc.)
from the distribution archives.
Why? Aren't our docs checked in too somewhere, or can be
mechanically re-created from checked-in sources?
We do have to discuss the actual release process. Other projects
(e.g. httpd) do it differently, they roll their distribution archives
first and then vote on them. We do it the other way around.
So here's my suggestion - choose some process that in the end
produces a build that a) can be re-created by anyone based on knowing
the svn revision and b) outputs the binary packaging that we can vote
on to be our released artifacts.
geir
Best regards
Henning
geir
On Jan 27, 2007, at 6:20 AM, Henning P. Schmiedehausen wrote:
"Geir Magnusson Jr." <[EMAIL PROTECTED]> writes:
I assume we'll have another vote on the final binary?
geir
Do we need to? The code itself will not change, just some doc file,
change logs etc.
Best regards
Henning
On Jan 27, 2007, at 3:52 AM, Henning P. Schmiedehausen wrote:
"Will Glass-Husain" <[EMAIL PROTECTED]> writes:
Hi,
I'd say that I fully agree with your points. This is part of the
"docs
cleanup" before we release the code.
Best regards
Henning
Hi Henning,
+1, with a caveat...
Users will want to see specifics of what's new with the system.
Where's the change list? Will Maven generate this
automatically? I
suggest we have two items
* a copy of the release notes from the Wiki, moved into the main
distro as "RELEASE-NOTES.txt". This summarizes key changes and
more
importantly, dependency changes.
* a maven generated list from changes.xml
I'm +1 if we have those two things.
As an aside, It's incredible all the work you've done,
especially in
the past few months.
WILL
On 1/24/07, Malcolm Edgar <[EMAIL PROTECTED]> wrote:
Been waiting for this day for a while now :)
+1
On 1/25/07, Nathan Bubna <[EMAIL PROTECTED]> wrote:
+1
On 1/24/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote:
Let's do it.
The list of changes
(http://issues.apache.org/jira/secure/ReleaseNote.jspa?
version=12310253&styleName=Text&projectId=12310104&Create=Crea
te
)
is much longer than it ought to be, the number of open issues
is more or less down to zero and no new issues have been
reported with beta 2. I think, it is time now.
Stuff that I do expect to change between "now" (CfV) and
"then" (Relase)
are all non code:
- Further work on the docs
- A Maven 2 POM so that the Mavenatics don't need to pull
velocity.jar
and velocity-dep.jar in all the time
- Updates on the xdocs themselves.
[ ] +1 Let's do it
[ ] 0 I don't care
[ ] -1 No, because __________________
The vote will go for ~72 hours, that is Saturday, 27th, 18:00
MET
(http://www.timeanddate.com/worldclock/fixedtime.html?
month=1&day=27&year=2007&hour=18&min=0&sec=0&p1=37)
My vote is +1
Best regards
Henning
--------------------------------------------------------------
--
--
---
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------
--
--
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
----------------------------------------------------------------
--
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Forio Business Simulations
Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com
-----------------------------------------------------------------
--
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity -
Turbine guy
"Save the cheerleader. Save the world."
------------------------------------------------------------------
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy
"Save the cheerleader. Save the world."
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
