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.