number-format-developers

[Number::Format] Release 1.52

[Bill W. <bi...@wa...>]

To make release 1.52 I think we need to do:

1. Add release date to CHANGES file
2. Update README file
3. Add a test case for the patch which was just committed

Will someone do #3?  I can do #1 and #2.  Is there anything else I'm missing?

This is the first time I've done a release via SourceForge for any
project so I need to learn how to do that.  I'm planning to upload the
older versions as a test.  Have any of you done that before?  Any tips
if so?

-- 
Help bring back the San Jose Earthquakes - http://www.soccersiliconvalley.com/

[Number::Format] Release 1.52

[Bill W. <bi...@wa...>]

I have decided to release 1.52 with that \s+ to \s* change now, and
then we can concentrate on other features.

I have updated all the files such as README and CHANGES for the
release and am checking those in now, then I will be applying the CVS
label.  Please don't make any more commits until I give the word.

I also took the 3 issues listed in the TODO file and entered them in
the Feature Requests tracker.  You should all be able to access the
tracker now:
http://sourceforge.net/tracker/?group_id=175334&atid=872819

I think we should enter the bugs from RT under the Bugs or Support
Requests trackers, not the Tasks list.  Any thoughts on that?  I'm new
at this SourceForge admin stuff so if you think I should do it
differently please speak up.  Also don't hesitate to ask for access to
something that you may be blocked from doing currently.

-- 
Help bring back the San Jose Earthquakes - http://www.soccersiliconvalley.com/

Re: [Number::Format] Release 1.52

[Jonas B. N. <jo...@gm...>]

Hello,

See below,

On 21/09/2006, at 20.45, Bill Ward wrote:

> I have decided to release 1.52 with that \s+ to \s* change now, and
> then we can concentrate on other features.
>

Sounds good, I will skip the related tests then...

> I have updated all the files such as README and CHANGES for the
> release and am checking those in now, then I will be applying the CVS
> label.  Please don't make any more commits until I give the word.
>

Perhaps we should have a branching strategy? so we can work on issues  
in parallel

or we create a subproject aiming at a release - I think this is  
normally called a roadmap :)

> I also took the 3 issues listed in the TODO file and entered them in
> the Feature Requests tracker.  You should all be able to access the
> tracker now:
> http://sourceforge.net/tracker/?group_id=175334&atid=872819


> I think we should enter the bugs from RT under the Bugs or Support
> Requests trackers, not the Tasks list.  Any thoughts on that?  I'm new
> at this SourceForge admin stuff so if you think I should do it
> differently please speak up.  Also don't hesitate to ask for access to
> something that you may be blocked from doing currently.
>

Well it is all things which needs to be done, the task listing would  
enable us to plan when the bugs should be fixed and we keep them in  
RT until resolved.

Otherwise we should mention that bug reports should go to sf.net  
instead of rt.cpan.org.

> -- 
> Help bring back the San Jose Earthquakes - http:// 
> www.soccersiliconvalley.com/
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys -- and earn  
> cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Number-Format-Developers mailing list
> Num...@li...
> https://lists.sourceforge.net/lists/listinfo/number-format-developers

Just my 5 cents,

jonasbn

Re: [Number::Format] Release 1.52

[Bill W. <bi...@wa...>]

On 9/21/06, Jonas B. Nielsen <jo...@gm...> wrote:
> On 21/09/2006, at 20.45, Bill Ward wrote:
> > I have decided to release 1.52 with that \s+ to \s* change now, and
> > then we can concentrate on other features.
>
> Sounds good, I will skip the related tests then...

Yes, upon further reflection it would be silly to add a test for this,
as the existing format_price.t should cover the case.

> > I have updated all the files such as README and CHANGES for the
> > release and am checking those in now, then I will be applying the CVS
> > label.  Please don't make any more commits until I give the word.
>
> Perhaps we should have a branching strategy? so we can work on issues
> in parallel

My experience with CVS has been entirely as the sole developer so I
haven't had occasion to work with branches.  I know what they are and
have used them in ClearCase extensively, but not in CVS.  Do you have
a strategy in mind?

> or we create a subproject aiming at a release - I think this is
> normally called a roadmap :)

Not sure this project is big enough to require subprojects... but feel
free to explain in more depth.

> > I think we should enter the bugs from RT under the Bugs or Support
> > Requests trackers, not the Tasks list.  Any thoughts on that?  I'm new
> > at this SourceForge admin stuff so if you think I should do it
> > differently please speak up.  Also don't hesitate to ask for access to
> > something that you may be blocked from doing currently.
>
> Well it is all things which needs to be done, the task listing would
> enable us to plan when the bugs should be fixed and we keep them in
> RT until resolved.
>
> Otherwise we should mention that bug reports should go to sf.net
> instead of rt.cpan.org.

I added a link to the sf.net tracker in the README file for 1.52.  I
wish there was some way to sync the two automatically.  I fear we may
have to just keep checking both places.

Bill.

Re: [Number::Format] Release 1.52

[Cees H. <ce...@gm...>]

On 9/21/06, Bill Ward <bi...@wa...> wrote:
> > Otherwise we should mention that bug reports should go to sf.net
> > instead of rt.cpan.org.
>
> I added a link to the sf.net tracker in the README file for 1.52.  I
> wish there was some way to sync the two automatically.  I fear we may
> have to just keep checking both places.

As the owner of Number::Format, you should get an email at the address
you registered with CPAN or rt.cpan.org whenever any bugs are reported
through RT (at least I get that for all of my modules).

Cheers,

Cees

Re: [Number::Format] Release 1.52

[Bill W. <bi...@wa...>]

On 9/21/06, Cees Hek <ce...@gm...> wrote:
> On 9/21/06, Bill Ward <bi...@wa...> wrote:
> > > Otherwise we should mention that bug reports should go to sf.net
> > > instead of rt.cpan.org.
> >
> > I added a link to the sf.net tracker in the README file for 1.52.  I
> > wish there was some way to sync the two automatically.  I fear we may
> > have to just keep checking both places.
>
> As the owner of Number::Format, you should get an email at the address
> you registered with CPAN or rt.cpan.org whenever any bugs are reported
> through RT (at least I get that for all of my modules).

Yes, and I can probably auto-fwd those to this list.

-- 
Help bring back the San Jose Earthquakes - http://www.soccersiliconvalley.com/

Re: [Number::Format] Release 1.52

[Jonas B. N. <jo...@gm...>]

Hi Bill,

And we need to update the VERSION number AFAIK

Well the patch fixed a problem with failling tests? - so that the  
tests are succesfull should suffice or?

It seems as if there has been a glitch in the release of 1.51?

jonasbn

On 19/09/2006, at 22.13, Bill Ward wrote:

> To make release 1.52 I think we need to do:
>
> 1. Add release date to CHANGES file
> 2. Update README file
> 3. Add a test case for the patch which was just committed
>
> Will someone do #3?  I can do #1 and #2.  Is there anything else  
> I'm missing?
>
> This is the first time I've done a release via SourceForge for any
> project so I need to learn how to do that.  I'm planning to upload the
> older versions as a test.  Have any of you done that before?  Any tips
> if so?
>
> -- 
> Help bring back the San Jose Earthquakes - http:// 
> www.soccersiliconvalley.com/
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys -- and earn  
> cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Number-Format-Developers mailing list
> Num...@li...
> https://lists.sourceforge.net/lists/listinfo/number-format-developers

Re: [Number::Format] Release 1.52

[Bill W. <bi...@wa...>]

Damnit, the version number!  I thought it was automatically converted
from the CVS version but I see that it is hard coded.  So I guess
version 1.52 now has to include CVS version 1.53.  Ugh.

As for the test, I like to follow the policy that any change made
should have a test explicitly designed to cover that change.  In this
case we could test both with and without the space in int_curr_symbol.

On 9/19/06, Jonas B. Nielsen <jo...@gm...> wrote:
> Hi Bill,
>
> And we need to update the VERSION number AFAIK
>
> Well the patch fixed a problem with failling tests? - so that the
> tests are succesfull should suffice or?
>
> It seems as if there has been a glitch in the release of 1.51?
>
> jonasbn
>
> On 19/09/2006, at 22.13, Bill Ward wrote:
>
> > To make release 1.52 I think we need to do:
> >
> > 1. Add release date to CHANGES file
> > 2. Update README file
> > 3. Add a test case for the patch which was just committed
> >
> > Will someone do #3?  I can do #1 and #2.  Is there anything else
> > I'm missing?
> >
> > This is the first time I've done a release via SourceForge for any
> > project so I need to learn how to do that.  I'm planning to upload the
> > older versions as a test.  Have any of you done that before?  Any tips
> > if so?
> >
> > --
> > Help bring back the San Jose Earthquakes - http://
> > www.soccersiliconvalley.com/
> >
> > ----------------------------------------------------------------------
> > ---
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to
> > share your
> > opinions on IT & business topics through brief surveys -- and earn
> > cash
> > http://www.techsay.com/default.php?
> > page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Number-Format-Developers mailing list
> > Num...@li...
> > https://lists.sourceforge.net/lists/listinfo/number-format-developers
>
>


-- 
Help bring back the San Jose Earthquakes - http://www.soccersiliconvalley.com/

Re: [Number::Format] Release 1.52

[Jonas B. N. <jo...@gm...>]

Hi Bill,

Well you do not have to use the revision number, I just expected you  
auto-incremented the version number based on the revision number, I  
can see now that this is not the case, we might as well call this  
release 1.52 or we could roll back to 1.51 and try again?

I will look into writing a test for the patch.

jonasbn

On 19/09/2006, at 22.46, Bill Ward wrote:

> Damnit, the version number!  I thought it was automatically converted
> from the CVS version but I see that it is hard coded.  So I guess
> version 1.52 now has to include CVS version 1.53.  Ugh.
>
> As for the test, I like to follow the policy that any change made
> should have a test explicitly designed to cover that change.  In this
> case we could test both with and without the space in int_curr_symbol.
>
> On 9/19/06, Jonas B. Nielsen <jo...@gm...> wrote:
>> Hi Bill,
>>
>> And we need to update the VERSION number AFAIK
>>
>> Well the patch fixed a problem with failling tests? - so that the
>> tests are succesfull should suffice or?
>>
>> It seems as if there has been a glitch in the release of 1.51?
>>
>> jonasbn
>>
>> On 19/09/2006, at 22.13, Bill Ward wrote:
>>
>> > To make release 1.52 I think we need to do:
>> >
>> > 1. Add release date to CHANGES file
>> > 2. Update README file
>> > 3. Add a test case for the patch which was just committed
>> >
>> > Will someone do #3?  I can do #1 and #2.  Is there anything else
>> > I'm missing?
>> >
>> > This is the first time I've done a release via SourceForge for any
>> > project so I need to learn how to do that.  I'm planning to  
>> upload the
>> > older versions as a test.  Have any of you done that before?   
>> Any tips
>> > if so?
>> >
>> > --
>> > Help bring back the San Jose Earthquakes - http://
>> > www.soccersiliconvalley.com/
>> >
>> >  
>> --------------------------------------------------------------------- 
>> -
>> > ---
>> > Take Surveys. Earn Cash. Influence the Future of IT
>> > Join SourceForge.net's Techsay panel and you'll get the chance to
>> > share your
>> > opinions on IT & business topics through brief surveys -- and earn
>> > cash
>> > http://www.techsay.com/default.php?
>> > page=join.php&p=sourceforge&CID=DEVDEV
>> > _______________________________________________
>> > Number-Format-Developers mailing list
>> > Num...@li...
>> > https://lists.sourceforge.net/lists/listinfo/number-format- 
>> developers
>>
>>
>
>
> -- 
> Help bring back the San Jose Earthquakes - http:// 
> www.soccersiliconvalley.com/

Re: [Number::Format] Release 1.52

[Bill W. <bi...@wa...>]

Not sure how we would roll it back without access to the CVS
repository itself...?
Never mind ... let's just go to 1.6 as the next release.  Are there
any other low-hanging fruit type changes that anyone wants to make for
this?

On 9/19/06, Jonas B. Nielsen <jo...@gm...> wrote:
> Hi Bill,
>
> Well you do not have to use the revision number, I just expected you
> auto-incremented the version number based on the revision number, I
> can see now that this is not the case, we might as well call this
> release 1.52 or we could roll back to 1.51 and try again?
>
> I will look into writing a test for the patch.
>
> jonasbn
>
> On 19/09/2006, at 22.46, Bill Ward wrote:
>
> > Damnit, the version number!  I thought it was automatically converted
> > from the CVS version but I see that it is hard coded.  So I guess
> > version 1.52 now has to include CVS version 1.53.  Ugh.
> >
> > As for the test, I like to follow the policy that any change made
> > should have a test explicitly designed to cover that change.  In this
> > case we could test both with and without the space in int_curr_symbol.
> >
> > On 9/19/06, Jonas B. Nielsen <jo...@gm...> wrote:
> >> Hi Bill,
> >>
> >> And we need to update the VERSION number AFAIK
> >>
> >> Well the patch fixed a problem with failling tests? - so that the
> >> tests are succesfull should suffice or?
> >>
> >> It seems as if there has been a glitch in the release of 1.51?
> >>
> >> jonasbn
> >>
> >> On 19/09/2006, at 22.13, Bill Ward wrote:
> >>
> >> > To make release 1.52 I think we need to do:
> >> >
> >> > 1. Add release date to CHANGES file
> >> > 2. Update README file
> >> > 3. Add a test case for the patch which was just committed
> >> >
> >> > Will someone do #3?  I can do #1 and #2.  Is there anything else
> >> > I'm missing?
> >> >
> >> > This is the first time I've done a release via SourceForge for any
> >> > project so I need to learn how to do that.  I'm planning to
> >> upload the
> >> > older versions as a test.  Have any of you done that before?
> >> Any tips
> >> > if so?
> >> >
> >> > --
> >> > Help bring back the San Jose Earthquakes - http://
> >> > www.soccersiliconvalley.com/
> >> >
> >> >
> >> ---------------------------------------------------------------------
> >> -
> >> > ---
> >> > Take Surveys. Earn Cash. Influence the Future of IT
> >> > Join SourceForge.net's Techsay panel and you'll get the chance to
> >> > share your
> >> > opinions on IT & business topics through brief surveys -- and earn
> >> > cash
> >> > http://www.techsay.com/default.php?
> >> > page=join.php&p=sourceforge&CID=DEVDEV
> >> > _______________________________________________
> >> > Number-Format-Developers mailing list
> >> > Num...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/number-format-
> >> developers
> >>
> >>
> >
> >
> > --
> > Help bring back the San Jose Earthquakes - http://
> > www.soccersiliconvalley.com/
>
>


-- 
Help bring back the San Jose Earthquakes - http://www.soccersiliconvalley.com/

Re: [Number::Format] Release 1.52

[Jonas B. N. <jo...@gm...>]

Hi Bill,

If that is the case, I say we wait a few days and try to eliminate as  
many as the reported issues as possible.

I still cannot create tasks on sf.net, or perhaps I just do not  
understand how to, but else we could just go over the list I wroteup.

As far as I can tell we are already two requests down :-)

jonasbn

On 19/09/2006, at 22.56, Bill Ward wrote:

> Not sure how we would roll it back without access to the CVS
> repository itself...?
> Never mind ... let's just go to 1.6 as the next release.  Are there
> any other low-hanging fruit type changes that anyone wants to make for
> this?
>
> On 9/19/06, Jonas B. Nielsen <jo...@gm...> wrote:
>> Hi Bill,
>>
>> Well you do not have to use the revision number, I just expected you
>> auto-incremented the version number based on the revision number, I
>> can see now that this is not the case, we might as well call this
>> release 1.52 or we could roll back to 1.51 and try again?
>>
>> I will look into writing a test for the patch.
>>
>> jonasbn
>>
>> On 19/09/2006, at 22.46, Bill Ward wrote:
>>
>> > Damnit, the version number!  I thought it was automatically  
>> converted
>> > from the CVS version but I see that it is hard coded.  So I guess
>> > version 1.52 now has to include CVS version 1.53.  Ugh.
>> >
>> > As for the test, I like to follow the policy that any change made
>> > should have a test explicitly designed to cover that change.  In  
>> this
>> > case we could test both with and without the space in  
>> int_curr_symbol.
>> >
>> > On 9/19/06, Jonas B. Nielsen <jo...@gm...> wrote:
>> >> Hi Bill,
>> >>
>> >> And we need to update the VERSION number AFAIK
>> >>
>> >> Well the patch fixed a problem with failling tests? - so that the
>> >> tests are succesfull should suffice or?
>> >>
>> >> It seems as if there has been a glitch in the release of 1.51?
>> >>
>> >> jonasbn
>> >>
>> >> On 19/09/2006, at 22.13, Bill Ward wrote:
>> >>
>> >> > To make release 1.52 I think we need to do:
>> >> >
>> >> > 1. Add release date to CHANGES file
>> >> > 2. Update README file
>> >> > 3. Add a test case for the patch which was just committed
>> >> >
>> >> > Will someone do #3?  I can do #1 and #2.  Is there anything else
>> >> > I'm missing?
>> >> >
>> >> > This is the first time I've done a release via SourceForge  
>> for any
>> >> > project so I need to learn how to do that.  I'm planning to
>> >> upload the
>> >> > older versions as a test.  Have any of you done that before?
>> >> Any tips
>> >> > if so?
>> >> >
>> >> > --
>> >> > Help bring back the San Jose Earthquakes - http://
>> >> > www.soccersiliconvalley.com/
>> >> >
>> >> >
>> >>  
>> ---------------------------------------------------------------------
>> >> -
>> >> > ---
>> >> > Take Surveys. Earn Cash. Influence the Future of IT
>> >> > Join SourceForge.net's Techsay panel and you'll get the  
>> chance to
>> >> > share your
>> >> > opinions on IT & business topics through brief surveys -- and  
>> earn
>> >> > cash
>> >> > http://www.techsay.com/default.php?
>> >> > page=join.php&p=sourceforge&CID=DEVDEV
>> >> > _______________________________________________
>> >> > Number-Format-Developers mailing list
>> >> > Num...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/number-format-
>> >> developers
>> >>
>> >>
>> >
>> >
>> > --
>> > Help bring back the San Jose Earthquakes - http://
>> > www.soccersiliconvalley.com/
>>
>>
>
>
> -- 
> Help bring back the San Jose Earthquakes - http:// 
> www.soccersiliconvalley.com/