phpbt-dev

[phpBT-dev] phpBT 1.1 vs 1.0.2

[Ulf E. <ulf...@fa...>]

Benjamin,

Is the plan still to have a v1.0.2 update? Should I keep flagging bugs 
as interesting for that release? or is it time to focus on 1.1?

What do you think of branching over two weeks? (november 1st?)

/Ulf

Re: [phpBT-dev] phpBT 1.1 vs 1.0.2

[Benjamin C. <php...@be...>]

Yeah, I've been thinking for the last week or so that we should just  
do 1.1.  Branching around the 1st sounds good to me.

On Oct 18, 2005, at 12:13 PM, Ulf Erikson wrote:


> Benjamin,
>
> Is the plan still to have a v1.0.2 update? Should I keep flagging  
> bugs as interesting for that release? or is it time to focus on 1.1?
>
> What do you think of branching over two weeks? (november 1st?)
>
> /Ulf
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,  
> discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> phpbt-dev mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbt-dev
>
>

Re: [phpBT-dev] phpBT 1.1

[Ulf E. <ulf...@fa...>]

Sorry that it toke a while. The upgrade scripts should be ready now. 
They are all disabled until I hear from someone that they work safely.. 
Please be careful with your data while testing.

Benjamin, what is the plan now? I would suggest:
  1) Ask people at phpbt-dev to test the CVS version
    a) first by a fresh install into an empty database and add some 
dummy users and bugs.
    b) by upgrading a dummy v1.0.1 database (or a copy! of an existing 
v1.0.1 database)
  2) Fix some bugs found
  3) Make a tar-ball and ask people at phpbt-users to test it
  4) Fix some bugs found
  5) release? or iterate steps 3+4 a few times?


Benjamin Curtis wrote:
> Yeah, I've been thinking for the last week or so that we should just  do 
> 1.1.  Branching around the 1st sounds good to me.
> 
> On Oct 18, 2005, at 12:13 PM, Ulf Erikson wrote:
>> Benjamin,
>>
>> Is the plan still to have a v1.0.2 update? Should I keep flagging  
>> bugs as interesting for that release? or is it time to focus on 1.1?
>>
>> What do you think of branching over two weeks? (november 1st?)

Re: [phpBT-dev] phpBT 1.1

[Benjamin C. <php...@be...>]

That sounds good to me.

On Nov 9, 2005, at 12:49 PM, Ulf Erikson wrote:

> Sorry that it toke a while. The upgrade scripts should be ready  
> now. They are all disabled until I hear from someone that they work  
> safely.. Please be careful with your data while testing.
>
> Benjamin, what is the plan now? I would suggest:
>  1) Ask people at phpbt-dev to test the CVS version
>    a) first by a fresh install into an empty database and add some  
> dummy users and bugs.
>    b) by upgrading a dummy v1.0.1 database (or a copy! of an  
> existing v1.0.1 database)
>  2) Fix some bugs found
>  3) Make a tar-ball and ask people at phpbt-users to test it
>  4) Fix some bugs found
>  5) release? or iterate steps 3+4 a few times?
>
>
> Benjamin Curtis wrote:
>> Yeah, I've been thinking for the last week or so that we should  
>> just  do 1.1.  Branching around the 1st sounds good to me.
>> On Oct 18, 2005, at 12:13 PM, Ulf Erikson wrote:
>>> Benjamin,
>>>
>>> Is the plan still to have a v1.0.2 update? Should I keep  
>>> flagging  bugs as interesting for that release? or is it time to  
>>> focus on 1.1?
>>>
>>> What do you think of branching over two weeks? (november 1st?)
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.  
> Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> phpbt-dev mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbt-dev

[phpBT-dev] Testing of pre-phpBT 1.1

[Ulf E. <ulf...@fa...>]

Hi All!

Enough features and fixes have been added to phpBugTracker since the 1.0
release. It is time to prepare for a v1.1 release. Hopefully this can be
done quickly.

First step will be a rough functionality test. Download the CVS HEAD
version and start with a fresh, empty, database. Add some users, add
some bugs, try out the new features.

I would like to hear from as many testers as possible what system you
are using (OS+version, web server+version, database+version and php
version) and what your results are. If you would be able to check
whether upgrades from 1.0.1 work too that would be great.

Note: Upgrades are currently disabled. Unless you know what you do (and
are working with a copy of your backed-up data) don't enable it ;-)

As soon as it looks like the code is stable enough to benefit from more
serious testing there will be a beta available for download and an
announcement to the phpbt-users mailing list.

Below is the CHANGELOG since 1.0.1

Thanks
/Ulf


-- 1.x -- 
: Moved priority levels into a table
: Changed the 'Assignable' bit to a group permission
: Added sort-order to components and versions
: Added support to bookmark/monitor a set of bugs
: Added a simple UI to edit group permissions
: Added support to (re)edit a query
: Added support for sending smtp mail
: Made the group "User" less special
: Fixed some permissions related issues for project admins
: Added "priority" and "dependency" to the bug history
: Added the ability to update several bugs at once
: Allow admins and project admins to delete bugs
: Allow admins and project admins to change reporter
: Added support to mark bugs as duplicates of each other
: Added several new permissions and a set of "user roles"



On Mon, 21 Nov 2005 20:44:04 -0800, Benjamin Curtis wrote:
> That sounds good to me.
> 
> On Nov 9, 2005, at 12:49 PM, Ulf Erikson wrote:
> 
>> Sorry that it toke a while. The upgrade scripts should be ready  
>> now. They are all disabled until I hear from someone that they work  
>> safely.. Please be careful with your data while testing.
>>
>> Benjamin, what is the plan now? I would suggest:
>>  1) Ask people at phpbt-dev to test the CVS version
>>    a) first by a fresh install into an empty database and add some  
>> dummy users and bugs.
>>    b) by upgrading a dummy v1.0.1 database (or a copy! of an  
>> existing v1.0.1 database)
>>  2) Fix some bugs found
>>  3) Make a tar-ball and ask people at phpbt-users to test it
>>  4) Fix some bugs found
>>  5) release? or iterate steps 3+4 a few times?
>>
>>
>> Benjamin Curtis wrote:
>>> Yeah, I've been thinking for the last week or so that we should  
>>> just  do 1.1.  Branching around the 1st sounds good to me.
>>> On Oct 18, 2005, at 12:13 PM, Ulf Erikson wrote:
>>>> Benjamin,
>>>>
>>>> Is the plan still to have a v1.0.2 update? Should I keep  
>>>> flagging  bugs as interesting for that release? or is it time to  
>>>> focus on 1.1?
>>>>
>>>> What do you think of branching over two weeks? (november 1st?)

Re: [phpBT-dev] Testing of pre-phpBT 1.1

[Marco K. <kuh...@we...>]

hi all,

i tried to download the cvs version, 
but i got no access to download it.

Tried:
phpbt_CVS # cvs -d:pserver:ano...@cv...:/cvsroot/phpbt login
Logging in to :pserver:ano...@cv...:2401/cvsroot/phpbt
CVS password:
cvs [login aborted]: connect to cvs.sourceforge.net(66.35.250.207):2401 
failed: Connection timed out

does anyone have the same experience?

by

marco




Am Dienstag, 22. November 2005 16:36 schrieb Ulf Erikson:
> Hi All!
>
> Enough features and fixes have been added to phpBugTracker since the 1.0
> release. It is time to prepare for a v1.1 release. Hopefully this can be
> done quickly.
>
> First step will be a rough functionality test. Download the CVS HEAD
> version and start with a fresh, empty, database. Add some users, add
> some bugs, try out the new features.
>
> I would like to hear from as many testers as possible what system you
> are using (OS+version, web server+version, database+version and php
> version) and what your results are. If you would be able to check
> whether upgrades from 1.0.1 work too that would be great.
>
> Note: Upgrades are currently disabled. Unless you know what you do (and
> are working with a copy of your backed-up data) don't enable it ;-)
>
> As soon as it looks like the code is stable enough to benefit from more
> serious testing there will be a beta available for download and an
> announcement to the phpbt-users mailing list.
>
> Below is the CHANGELOG since 1.0.1
>
> Thanks
> /Ulf
>
>
> -- 1.x --
>
> : Moved priority levels into a table
> : Changed the 'Assignable' bit to a group permission
> : Added sort-order to components and versions
> : Added support to bookmark/monitor a set of bugs
> : Added a simple UI to edit group permissions
> : Added support to (re)edit a query
> : Added support for sending smtp mail
> : Made the group "User" less special
> : Fixed some permissions related issues for project admins
> : Added "priority" and "dependency" to the bug history
> : Added the ability to update several bugs at once
> : Allow admins and project admins to delete bugs
> : Allow admins and project admins to change reporter
> : Added support to mark bugs as duplicates of each other
> : Added several new permissions and a set of "user roles"
>
> On Mon, 21 Nov 2005 20:44:04 -0800, Benjamin Curtis wrote:
> > That sounds good to me.
> >
> > On Nov 9, 2005, at 12:49 PM, Ulf Erikson wrote:
> >> Sorry that it toke a while. The upgrade scripts should be ready
> >> now. They are all disabled until I hear from someone that they work
> >> safely.. Please be careful with your data while testing.
> >>
> >> Benjamin, what is the plan now? I would suggest:
> >>  1) Ask people at phpbt-dev to test the CVS version
> >>    a) first by a fresh install into an empty database and add some
> >> dummy users and bugs.
> >>    b) by upgrading a dummy v1.0.1 database (or a copy! of an
> >> existing v1.0.1 database)
> >>  2) Fix some bugs found
> >>  3) Make a tar-ball and ask people at phpbt-users to test it
> >>  4) Fix some bugs found
> >>  5) release? or iterate steps 3+4 a few times?
> >>
> >> Benjamin Curtis wrote:
> >>> Yeah, I've been thinking for the last week or so that we should
> >>> just  do 1.1.  Branching around the 1st sounds good to me.
> >>>
> >>> On Oct 18, 2005, at 12:13 PM, Ulf Erikson wrote:
> >>>> Benjamin,
> >>>>
> >>>> Is the plan still to have a v1.0.2 update? Should I keep
> >>>> flagging  bugs as interesting for that release? or is it time to
> >>>> focus on 1.1?
> >>>>
> >>>> What do you think of branching over two weeks? (november 1st?)
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
> _______________________________________________
> phpbt-dev mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbt-dev