Re: Moving HWPF out of scratchpad
Lets go with the traditional thing >Label things beta1, beta2 etc for development releases and full version >numbers for final versions. >Increase the major revision number for big changes. Ryan, you'll have to take a call on where you want to make a release from, HEAD or 2.0BRANCH. Currently all the HWPF code lives in HEAD. however, HSSF on HEAD does not pass even the existing unit tests. Do you want to make a copy of the HWPF code in Branch to make a release? Your call. I'll help the best I can. If we release from branch, lets call it 2.6beta1. If we release from head, call it 3.0beta1. Right? Regards - Avik On Thu, 2004-03-25 at 16:18, Glen Stampoultzis wrote: > At 04:51 PM 25/03/2004, you wrote: > >I am very keen to see HWPF move out of scratchpad, it seems to have a > >lot of momentum recently. I was about to write a mail on this, Ryan beat > >me to it. So lets do that ASAP, i think. > > > >We should also do a dev release with this in, but I am -1 to calling it > >a 2.6. And I certainly disagree to adding HWPF to a bugfix release of > >2.5.1. I dont think our long-suffering users would appreciate that :) > > Alternatives? > > >Guys, I really think we really have to get our version numbering sane. > >We seem to have introduced a few regressions in 2.5, tho we called it a > >prod release. So I am all for doing a release, but calling it dev/beta > >whatever. What do you think? > > Absolutely. I think we all agree that the current way of doing things is > silly. I'm really not bothered exactly what scheme we choose as long as > it's sane. I figured for the 3.0 stuff we could decide on something > sensible then document it as a standard. > > Options: > > Linux style: > > Odd minor numbers for development versions. Even numbers for production > versions. Major numbers when big changes happen. > > Traditional: > > Label things beta1, beta2 etc for development releases and full version > numbers for final versions. Increase the major revision number for big > changes. > > Other: > > ??? > > I think I prefer traditional style but as I said I'm not really bothered. > > > Regards, > > > Glen Stampoultzis > [EMAIL PROTECTED] > http://members.iinet.net.au/~gstamp/glen/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving HWPF out of scratchpad
Timescale for moving out of scratchpad, I would hope immediately. The dev release, hopefully before the JDJ article. - Original Message - From: "Piers Taylor" <[EMAIL PROTECTED]> To: "'POI Developers List'" <[EMAIL PROTECTED]> Sent: Thursday, March 25, 2004 3:43 AM Subject: RE: Moving HWPF out of scratchpad > Hi Ryan, > > What would be the timescale for this? > As you know, we're working on getting the tables code > sorted out, and then will be looking into the 'special' strings > (hyperlinks, embedded objects etc). > > Regards, > Piers > > Piers Taylor - Senior Developer > Goss Interactive Ltd > http://www.gossinteractive.com > Telephone: +44 1752 517350 > > > -- > This e-mail contains proprietary information, some or all of > which may be legally privileged. It is for the intended recipient > only. If an addressing or transmission error has misdirected this > e-mail, please notify the author by replying to this e-mail. > If you are not the intended recipient you may not use, disclose, > distribute, copy, print or rely on this e-mail. > > Email transmission cannot be guaranteed to be secure or error free > as information may be intercepted, corrupted, lost, destroyed, > arrive late or incomplete or contain viruses. This email and any > files attached to it have been checked with virus detection software > before transmission. You should nonetheless carry out your own virus > check before opening any attachment. Goss Interactive Ltd accepts no > liability for any loss or damage which may be caused by software > viruses. > > -Original Message- > From: Ryan Ackley [mailto:[EMAIL PROTECTED] > Sent: 24 March 2004 19:01 > To: POI Developers List > Subject: Moving HWPF out of scratchpad > > > To all committers, > > I would like to get feel out everyones thoughts on moving HWPF out of > scratchpad. More specifically, what requirements do you want me to meet > before you would be willing to vote for this to happen? > > Avik and I are writing an article for JDJ and it will contain material on > HWPF. For this article to have the maximum benefit, I feel that HWPF should > be as easily accessible as possible. How about a 2.6 release containing > HWPF? thoughts? > > -Ryan > > > - > 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]
Re: Moving HWPF out of scratchpad
> Guys, I really think we really have to get our version numbering sane. > We seem to have introduced a few regressions in 2.5, tho we called it a > prod release. So I am all for doing a release, but calling it dev/beta > whatever. What do you think? Thats fine, the only thing I care about is having a jar that people can download. -Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving HWPF out of scratchpad
At 04:51 PM 25/03/2004, you wrote: I am very keen to see HWPF move out of scratchpad, it seems to have a lot of momentum recently. I was about to write a mail on this, Ryan beat me to it. So lets do that ASAP, i think. We should also do a dev release with this in, but I am -1 to calling it a 2.6. And I certainly disagree to adding HWPF to a bugfix release of 2.5.1. I dont think our long-suffering users would appreciate that :) Alternatives? Guys, I really think we really have to get our version numbering sane. We seem to have introduced a few regressions in 2.5, tho we called it a prod release. So I am all for doing a release, but calling it dev/beta whatever. What do you think? Absolutely. I think we all agree that the current way of doing things is silly. I'm really not bothered exactly what scheme we choose as long as it's sane. I figured for the 3.0 stuff we could decide on something sensible then document it as a standard. Options: Linux style: Odd minor numbers for development versions. Even numbers for production versions. Major numbers when big changes happen. Traditional: Label things beta1, beta2 etc for development releases and full version numbers for final versions. Increase the major revision number for big changes. Other: ??? I think I prefer traditional style but as I said I'm not really bothered. Regards, Glen Stampoultzis [EMAIL PROTECTED] http://members.iinet.net.au/~gstamp/glen/
RE: Moving HWPF out of scratchpad
Hi Ryan, What would be the timescale for this? As you know, we're working on getting the tables code sorted out, and then will be looking into the 'special' strings (hyperlinks, embedded objects etc). Regards, Piers Piers Taylor - Senior Developer Goss Interactive Ltd http://www.gossinteractive.com Telephone: +44 1752 517350 -- This e-mail contains proprietary information, some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on this e-mail. Email transmission cannot be guaranteed to be secure or error free as information may be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. This email and any files attached to it have been checked with virus detection software before transmission. You should nonetheless carry out your own virus check before opening any attachment. Goss Interactive Ltd accepts no liability for any loss or damage which may be caused by software viruses. -Original Message- From: Ryan Ackley [mailto:[EMAIL PROTECTED] Sent: 24 March 2004 19:01 To: POI Developers List Subject: Moving HWPF out of scratchpad To all committers, I would like to get feel out everyones thoughts on moving HWPF out of scratchpad. More specifically, what requirements do you want me to meet before you would be willing to vote for this to happen? Avik and I are writing an article for JDJ and it will contain material on HWPF. For this article to have the maximum benefit, I feel that HWPF should be as easily accessible as possible. How about a 2.6 release containing HWPF? thoughts? -Ryan - 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]
Re: Moving HWPF out of scratchpad
I am very keen to see HWPF move out of scratchpad, it seems to have a lot of momentum recently. I was about to write a mail on this, Ryan beat me to it. So lets do that ASAP, i think. We should also do a dev release with this in, but I am -1 to calling it a 2.6. And I certainly disagree to adding HWPF to a bugfix release of 2.5.1. I dont think our long-suffering users would appreciate that :) Guys, I really think we really have to get our version numbering sane. We seem to have introduced a few regressions in 2.5, tho we called it a prod release. So I am all for doing a release, but calling it dev/beta whatever. What do you think? On Thu, 2004-03-25 at 00:30, Ryan Ackley wrote: > To all committers, > > I would like to get feel out everyones thoughts on moving HWPF out of > scratchpad. More specifically, what requirements do you want me to meet > before you would be willing to vote for this to happen? > > Avik and I are writing an article for JDJ and it will contain material on > HWPF. For this article to have the maximum benefit, I feel that HWPF should > be as easily accessible as possible. How about a 2.6 release containing > HWPF? thoughts? > > -Ryan > > > - > 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]
Re: Moving HWPF out of scratchpad
Am Mit, 2004-03-24 um 20.00 schrieb Ryan Ackley: > I would like to get feel out everyones thoughts on moving HWPF out of > scratchpad. +0 Best regards Rainer Klute Rainer Klute IT-Consulting GmbH Dipl.-Inform. Rainer Klute E-Mail: [EMAIL PROTECTED] Körner Grund 24 Telefon: +49 172 2324824 D-44143 Dortmund Telefax: +49 231 5349423 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving HWPF out of scratchpad
I'm +1 on moving it out. Well done on the massive effort to get it where it is today. Regarding a 2.6. I guess we can do that. I was planning for a 2.5.1 to include some bug fixes so I suppose we can include HWPF and call it 2.6 instead. I really want the 2.0 branch to go away but I can't see that happening until HEAD is fixed. Regards, Glen At 06:00 AM 25/03/2004, you wrote: To all committers, I would like to get feel out everyones thoughts on moving HWPF out of scratchpad. More specifically, what requirements do you want me to meet before you would be willing to vote for this to happen? Avik and I are writing an article for JDJ and it will contain material on HWPF. For this article to have the maximum benefit, I feel that HWPF should be as easily accessible as possible. How about a 2.6 release containing HWPF? thoughts? -Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Glen Stampoultzis [EMAIL PROTECTED] http://members.iinet.net.au/~gstamp/glen/
RE: Moving HWPF out of scratchpad
+0 Whilst I haven't a need to use HWPF, from what I have seen in the last few weeks it has some momentum behind it, and at a seemingly fit state for it to be promoted. Certainly judging by the number of bug reports filed against HSSF recently it couldn't be any worse ;-) Jason -Original Message- From: Ryan Ackley [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 5:31 AM To: POI Developers List Subject: Moving HWPF out of scratchpad To all committers, I would like to get feel out everyones thoughts on moving HWPF out of scratchpad. More specifically, what requirements do you want me to meet before you would be willing to vote for this to happen? Avik and I are writing an article for JDJ and it will contain material on HWPF. For this article to have the maximum benefit, I feel that HWPF should be as easily accessible as possible. How about a 2.6 release containing HWPF? thoughts? -Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail (including attachments) is confidential information of Australian Submarine Corporation Pty Limited (ASC). It may also be legally privileged. Unauthorised use and disclosure is prohibited. ASC is not taken to have waived confidentiality or privilege if this e-mail was sent to you in error. If you have received it in error, please notify the sender promptly. While ASC takes steps to identify and eliminate viruses, it cannot confirm that this e-mail is free from them. You should scan this e-mail for viruses before it is used. The statements in this e-mail are those of the sender only, unless specifically stated to be those of ASC by someone with authority to do so.
Moving HWPF out of scratchpad
To all committers, I would like to get feel out everyones thoughts on moving HWPF out of scratchpad. More specifically, what requirements do you want me to meet before you would be willing to vote for this to happen? Avik and I are writing an article for JDJ and it will contain material on HWPF. For this article to have the maximum benefit, I feel that HWPF should be as easily accessible as possible. How about a 2.6 release containing HWPF? thoughts? -Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
