Re: M3 on Wednesday?
On Nov 8, 2004, at 3:51 PM, Aaron Mulder wrote: On Mon, 8 Nov 2004, David Blevins wrote: Here is the filter settings you should use to create the "Unfinished" section of the changelog: Project: Apache Geronimo Status: Open, In Progress, Reopened Fix Version/s: No versions Affects Version/s: 1.0-M1,1.0-M2 Sorted by: Key descending I think I mentioned this before, but I was hoping to cover this with text instead of specific issue ID's. There are too many of them, and many are internal-use-only (not real meaningful to an end user). But that is a good query to get this list that I need to summarize as text. If we have time I really love the release notes Mozilla puts out http://www.mozilla.org/products/firefox/releases/ I also think we should have the detailed change log, but a summary like mozilla does would be spectacular. -dain
Re: M3 on Wednesday?
On Nov 8, 2004, at 3:50 PM, Bruce Snyder wrote: David Blevins wrote: Don't sweat the binary work. I've got a few hacked up scripts to tar,zip, md5, sha, pgp, and scp the source and binary distros. Though after all this is over, I would *love* get your help in converting them to jelly/maven so it would be easy for any of us to cut a release. I'd also like to automate the creation of the changelog. I have part of a stylesheet for it, but nothing working. This is exactly why I asked earlier if this stuff was in the Maven scripts. I guess this is the answer I was seeking. I'd be willing to help with this effort. Cool. Sorry if I missed it. Let's hook up at ApacheCon. Jason van Zyl will be there too, so it will be great timing. -David
Re: M3 on Wednesday?
On Nov 8, 2004, at 3:51 PM, Aaron Mulder wrote: On Mon, 8 Nov 2004, David Blevins wrote: Here is the filter settings you should use to create the "Unfinished" section of the changelog: Project: Apache Geronimo Status: Open, In Progress, Reopened Fix Version/s: No versions Affects Version/s: 1.0-M1,1.0-M2 Sorted by: Key descending I think I mentioned this before, but I was hoping to cover this with text instead of specific issue ID's. There are too many of them, and many are internal-use-only (not real meaningful to an end user). But that is a good query to get this list that I need to summarize as text. We should come up with a way to filter those out or use more "unbrella" issues in Jira so we don't have to tweak them by hand. Though after all this is over, I would *love* get your help in converting them to jelly/maven so it would be easy for any of us to cut a release. I'd also like to automate the creation of the changelog. I have part of a stylesheet for it, but nothing working. Well, you're really asking the wrong guy for help with Jelly/Maven. I spend 10N hours confused, frustrated, and griping for every N hours of productivity when working with them. Same here. That's why it's all in bash now and tied to my system. Looks like Bruce is willing to chip in here. The change log automation would be cool. Does JIRA have any kind of API or would we really need to screen scrape? Yes, xml output for any filter. The "Work completed this week" email I send out is done with a stylesheet using XML straight from Jira. We should be able to do the same thing with the release notes. -David
Re: M3 on Wednesday?
David Blevins wrote:
Wednesday is good for me. More below
On Nov 8, 2004, at 2:29 PM, Aaron Mulder wrote:
The vote to do a M3 release before ApacheCon was positive. Now
the question is when. I know many of us are travelling on Friday. I
suggest we prepare the release on Wednesday, so we have a bit of time to
look it over before anyone hops on a plane.
I'm not really looking for another vote, just speak up if you have
a problem with Wednesday being "the day".
Hopefully there won't be any trouble getting a stable build for
the M3 release, but if there is, we may need to revert some changes and
ask them to be re-applied after the M3.
So my plan is to continue to work on the release notes and, umm,
last-minute features until Wednesday and then get a stable build and
capture a "modules/assembly/target/geronimo-1.0-SNAPSHOT.jar" as the
official M3 and then change it into a tarball and zip instead of a JAR
and
sign it and post the release notes and download archives...
David B, if you're bored and want to take charge of this, you're
more than welcome to. :)
Here is the filter settings you should use to create the "Unfinished"
section of the changelog:
Project: Apache Geronimo
Status: Open, In Progress, Reopened
Fix Version/s: No versions
Affects Version/s: 1.0-M1,1.0-M2
Sorted by: Key descending
Don't sweat the binary work. I've got a few hacked up scripts to
tar,zip, md5, sha, pgp, and scp the source and binary distros.
Though after all this is over, I would *love* get your help in
converting them to jelly/maven so it would be easy for any of us to cut
a release. I'd also like to automate the creation of the changelog. I
have part of a stylesheet for it, but nothing working.
This is exactly why I asked earlier if this stuff was in the Maven
scripts. I guess this is the answer I was seeking. I'd be willing to
help with this effort.
Bruce
--
perl -e 'print
unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
Re: M3 on Wednesday?
On Mon, 8 Nov 2004, David Blevins wrote: > Here is the filter settings you should use to create the "Unfinished" > section of the changelog: > > Project: Apache Geronimo > Status: Open, In Progress, Reopened > Fix Version/s: No versions > Affects Version/s: 1.0-M1,1.0-M2 > Sorted by: Key descending I think I mentioned this before, but I was hoping to cover this with text instead of specific issue ID's. There are too many of them, and many are internal-use-only (not real meaningful to an end user). But that is a good query to get this list that I need to summarize as text. > Don't sweat the binary work. I've got a few hacked up scripts to > tar,zip, md5, sha, pgp, and scp the source and binary distros. Cool. > Though after all this is over, I would *love* get your help in > converting them to jelly/maven so it would be easy for any of us to cut > a release. I'd also like to automate the creation of the changelog. I > have part of a stylesheet for it, but nothing working. Well, you're really asking the wrong guy for help with Jelly/Maven. I spend 10N hours confused, frustrated, and griping for every N hours of productivity when working with them. The change log automation would be cool. Does JIRA have any kind of API or would we really need to screen scrape? Aaron
Re: M3 on Wednesday?
Aaron Mulder wrote:
The vote to do a M3 release before ApacheCon was positive. Now
the question is when. I know many of us are travelling on Friday. I
suggest we prepare the release on Wednesday, so we have a bit of time to
look it over before anyone hops on a plane.
I'm not really looking for another vote, just speak up if you have
a problem with Wednesday being "the day".
Hopefully there won't be any trouble getting a stable build for
the M3 release, but if there is, we may need to revert some changes and
ask them to be re-applied after the M3.
So my plan is to continue to work on the release notes and, umm,
last-minute features until Wednesday and then get a stable build and
capture a "modules/assembly/target/geronimo-1.0-SNAPSHOT.jar" as the
official M3 and then change it into a tarball and zip instead of a JAR and
sign it and post the release notes and download archives...
David B, if you're bored and want to take charge of this, you're
more than welcome to. :)
+1
Bruce
--
perl -e 'print
unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
Re: M3 on Wednesday?
Wednesday is good for me. More below On Nov 8, 2004, at 2:29 PM, Aaron Mulder wrote: The vote to do a M3 release before ApacheCon was positive. Now the question is when. I know many of us are travelling on Friday. I suggest we prepare the release on Wednesday, so we have a bit of time to look it over before anyone hops on a plane. I'm not really looking for another vote, just speak up if you have a problem with Wednesday being "the day". Hopefully there won't be any trouble getting a stable build for the M3 release, but if there is, we may need to revert some changes and ask them to be re-applied after the M3. So my plan is to continue to work on the release notes and, umm, last-minute features until Wednesday and then get a stable build and capture a "modules/assembly/target/geronimo-1.0-SNAPSHOT.jar" as the official M3 and then change it into a tarball and zip instead of a JAR and sign it and post the release notes and download archives... David B, if you're bored and want to take charge of this, you're more than welcome to. :) Here is the filter settings you should use to create the "Unfinished" section of the changelog: Project: Apache Geronimo Status: Open, In Progress, Reopened Fix Version/s: No versions Affects Version/s: 1.0-M1,1.0-M2 Sorted by: Key descending Don't sweat the binary work. I've got a few hacked up scripts to tar,zip, md5, sha, pgp, and scp the source and binary distros. Though after all this is over, I would *love* get your help in converting them to jelly/maven so it would be easy for any of us to cut a release. I'd also like to automate the creation of the changelog. I have part of a stylesheet for it, but nothing working. -David
Re: M3 on Wednesday?
+1 Wednesday I think the most important thing is we all agree to whined down development as Wednesday approaches. I know that normally there is a flood extra activity as a release approaches, which would make this release impossible, but I'm concerned that even at our current rate of change we will be unable to cut a release. I'd also like to try a dry run on Tuesday -dain On Nov 8, 2004, at 2:29 PM, Aaron Mulder wrote: The vote to do a M3 release before ApacheCon was positive. Now the question is when. I know many of us are travelling on Friday. I suggest we prepare the release on Wednesday, so we have a bit of time to look it over before anyone hops on a plane. I'm not really looking for another vote, just speak up if you have a problem with Wednesday being "the day". Hopefully there won't be any trouble getting a stable build for the M3 release, but if there is, we may need to revert some changes and ask them to be re-applied after the M3. So my plan is to continue to work on the release notes and, umm, last-minute features until Wednesday and then get a stable build and capture a "modules/assembly/target/geronimo-1.0-SNAPSHOT.jar" as the official M3 and then change it into a tarball and zip instead of a JAR and sign it and post the release notes and download archives... David B, if you're bored and want to take charge of this, you're more than welcome to. :) Thanks, Aaron
M3 on Wednesday?
The vote to do a M3 release before ApacheCon was positive. Now the question is when. I know many of us are travelling on Friday. I suggest we prepare the release on Wednesday, so we have a bit of time to look it over before anyone hops on a plane. I'm not really looking for another vote, just speak up if you have a problem with Wednesday being "the day". Hopefully there won't be any trouble getting a stable build for the M3 release, but if there is, we may need to revert some changes and ask them to be re-applied after the M3. So my plan is to continue to work on the release notes and, umm, last-minute features until Wednesday and then get a stable build and capture a "modules/assembly/target/geronimo-1.0-SNAPSHOT.jar" as the official M3 and then change it into a tarball and zip instead of a JAR and sign it and post the release notes and download archives... David B, if you're bored and want to take charge of this, you're more than welcome to. :) Thanks, Aaron
