Proposal for the new releasing policy.

[Ryo Dairiki-2]

Hi all,

Today, I propose the new releasing policy of this project.
What I suggest is three-month-cycle scheduling.

At the first month, bug reports and patches are collected at this list.
Developers should respond the issues at this month.

At the second month, reported issue are fixed or imported, or rejected.
Developers should fixe the issues, or reject the reports at this month.
Reporters and testers should check the cvs latest,
to see the issues are properly solved.

At the last month, the new release and the summary report are published.
At this month, developers should make a summary report for this merge
window.
All the remaining issues are send to the next month.

The main idea is, making a strict merge window helps us (me)
to keep release cycle constant.
I can concentrate on one thing every month under the new developing
policy. :)

I also think of closing forums and trackers at the same time,
because they are no good for this small number of developers.
I suggest all the reports be post directly here.

Regards,
Ryo Dairiki <[hidden email]>

P.S.
I'll setup this month as the third month, if nobody argues.

------------------------------------------------------------------------------
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel

[liucougar]

+1

although I don't see the reason to close the forum: that forum is a
mirror of this mailing list (new post there will appear here, and vice
versa)

On Sun, Jan 4, 2009 at 03:36, Ryo Dairiki
<[hidden email]> wrote:

> Hi all,
>
> Today, I propose the new releasing policy of this project.
> What I suggest is three-month-cycle scheduling.
>
> At the first month, bug reports and patches are collected at this list.
> Developers should respond the issues at this month.
>
> At the second month, reported issue are fixed or imported, or rejected.
> Developers should fixe the issues, or reject the reports at this month.
> Reporters and testers should check the cvs latest,
> to see the issues are properly solved.
>
> At the last month, the new release and the summary report are published.
> At this month, developers should make a summary report for this merge
> window.
> All the remaining issues are send to the next month.
>
> The main idea is, making a strict merge window helps us (me)
> to keep release cycle constant.
> I can concentrate on one thing every month under the new developing
> policy. :)
>
> I also think of closing forums and trackers at the same time,
> because they are no good for this small number of developers.
> I suggest all the reports be post directly here.
>
> Regards,
> Ryo Dairiki <[hidden email]>
>
> P.S.
> I'll setup this month as the third month, if nobody argues.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Scim-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/scim-devel
>

--
生于忧患，死于安乐
"People's characters are strengthened through struggle against
difficulties; they are weakened by comfort."
- Old Chinese adage
------------------------------------------------------------------------------
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel

[Choe Hwanjin]

On Sun, Jan 4, 2009 at 8:36 PM, Ryo Dairiki
<[hidden email]> wrote:

> Hi all,
>
> Today, I propose the new releasing policy of this project.
> What I suggest is three-month-cycle scheduling.
>
> At the first month, bug reports and patches are collected at this list.
> Developers should respond the issues at this month.
>
> At the second month, reported issue are fixed or imported, or rejected.
> Developers should fixe the issues, or reject the reports at this month.
> Reporters and testers should check the cvs latest,
> to see the issues are properly solved.
>
> At the last month, the new release and the summary report are published.
> At this month, developers should make a summary report for this merge
> window.
> All the remaining issues are send to the next month.
>
> The main idea is, making a strict merge window helps us (me)
> to keep release cycle constant.
> I can concentrate on one thing every month under the new developing
> policy. :)

Good.

> I also think of closing forums and trackers at the same time,
> because they are no good for this small number of developers.
> I suggest all the reports be post directly here.

Do you mean that you will not use bug tracker of sourceforge and use
mailing list only?

------------------------------------------------------------------------------
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel

[Ryo Dairiki-2]

Hi,

Choe Hwanjin wrote:

> On Sun, Jan 4, 2009 at 8:36 PM, Ryo Dairiki
> <[hidden email]> wrote:
>  
>> Hi all,
>>
>> Today, I propose the new releasing policy of this project.
>> What I suggest is three-month-cycle scheduling.
>>
>> At the first month, bug reports and patches are collected at this list.
>> Developers should respond the issues at this month.
>>
>> At the second month, reported issue are fixed or imported, or rejected.
>> Developers should fixe the issues, or reject the reports at this month.
>> Reporters and testers should check the cvs latest,
>> to see the issues are properly solved.
>>
>> At the last month, the new release and the summary report are published.
>> At this month, developers should make a summary report for this merge
>> window.
>> All the remaining issues are send to the next month.
>>
>> The main idea is, making a strict merge window helps us (me)
>> to keep release cycle constant.
>> I can concentrate on one thing every month under the new developing
>> policy. :)
>>    
>
> Good.
>
>  
>> I also think of closing forums and trackers at the same time,
>> because they are no good for this small number of developers.
>> I suggest all the reports be post directly here.
>>    
>
> Do you mean that you will not use bug tracker of sourceforge and use
> mailing list only?
>  

Yes, I do.

Bug tracking systems are for cases there are many developers.
It's useless if there are few people to assign the issues. :(
Or, could anybody volunteer to check and sync them with new release cycle?

Ryo


------------------------------------------------------------------------------
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel

[Choe Hwanjin]

On Mon, Jan 5, 2009 at 11:26 PM, Ryo Dairiki
<[hidden email]> wrote:

> Hi,
>
> Choe Hwanjin wrote:
>> On Sun, Jan 4, 2009 at 8:36 PM, Ryo Dairiki
>> <[hidden email]> wrote:
>>> I also think of closing forums and trackers at the same time,
>>> because they are no good for this small number of developers.
>>> I suggest all the reports be post directly here.
>>>
>>
>> Do you mean that you will not use bug tracker of sourceforge and use
>> mailing list only?
>>
>
> Yes, I do.
>
> Bug tracking systems are for cases there are many developers.
> It's useless if there are few people to assign the issues. :(

I suppose that many normal users prefer bug tracker to mailing list to
report a bug.
Tracking issues is important. Without bug tracker, it is quite
difficult to maintain bug list and history.

------------------------------------------------------------------------------
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel

[Ryo Dairiki-2]

Choe Hwanjin wrote:

> On Mon, Jan 5, 2009 at 11:26 PM, Ryo Dairiki
> <[hidden email]> wrote:
>  
>> Hi,
>>
>> Choe Hwanjin wrote:
>>    
>>> On Sun, Jan 4, 2009 at 8:36 PM, Ryo Dairiki
>>> <[hidden email]> wrote:
>>>      
>>>> I also think of closing forums and trackers at the same time,
>>>> because they are no good for this small number of developers.
>>>> I suggest all the reports be post directly here.
>>>>
>>>>        
>>> Do you mean that you will not use bug tracker of sourceforge and use
>>> mailing list only?
>>>
>>>      
>> Yes, I do.
>>
>> Bug tracking systems are for cases there are many developers.
>> It's useless if there are few people to assign the issues. :(
>>    
>
> I suppose that many normal users prefer bug tracker to mailing list to
> report a bug.
> Tracking issues is important. Without bug tracker, it is quite
> difficult to maintain bug list and history.
>  

It seems to me that you don't really understand that
*somebody* must maintain bug list and history, with or without the bug
tracker.
If you dare to put me in charge of it, I would claim the following things.

- Notification mails of the tracker should send to scim-devel-list, not
to scim-users-list.
- Posting bug reports on mailing lists should be banned.

Ryo

------------------------------------------------------------------------------
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel

[liucougar]

On Tue, Jan 6, 2009 at 07:21, Ryo Dairiki
<[hidden email]> wrote:

> Choe Hwanjin wrote:
>> On Mon, Jan 5, 2009 at 11:26 PM, Ryo Dairiki
>> <[hidden email]> wrote:
>>
>>> Hi,
>>>
>>> Choe Hwanjin wrote:
>>>
>>>> On Sun, Jan 4, 2009 at 8:36 PM, Ryo Dairiki
>>>> <[hidden email]> wrote:
>>>>
>>>>> I also think of closing forums and trackers at the same time,
>>>>> because they are no good for this small number of developers.
>>>>> I suggest all the reports be post directly here.
>>>>>
>>>>>
>>>> Do you mean that you will not use bug tracker of sourceforge and use
>>>> mailing list only?
>>>>
>>>>
>>> Yes, I do.
>>>
>>> Bug tracking systems are for cases there are many developers.
>>> It's useless if there are few people to assign the issues. :(
>>>
>>
>> I suppose that many normal users prefer bug tracker to mailing list to
>> report a bug.
>> Tracking issues is important. Without bug tracker, it is quite
>> difficult to maintain bug list and history.
>>
>
> It seems to me that you don't really understand that
> *somebody* must maintain bug list and history, with or without the bug
> tracker.
> If you dare to put me in charge of it, I would claim the following things.
>
> - Notification mails of the tracker should send to scim-devel-list, not
> to scim-users-list.

that can be changed in SF project management page

> - Posting bug reports on mailing lists should be banned.
>
> Ryo
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Scim-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/scim-devel
>

--
生于忧患，死于安乐
"People's characters are strengthened through struggle against
difficulties; they are weakened by comfort."
- Old Chinese adage
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel

[Choe Hwanjin]

On Wed, Jan 7, 2009 at 12:21 AM, Ryo Dairiki
<[hidden email]> wrote:

> Choe Hwanjin wrote:
>> On Mon, Jan 5, 2009 at 11:26 PM, Ryo Dairiki
>> <[hidden email]> wrote:
>>
>>> Hi,
>>>
>>> Choe Hwanjin wrote:
>>>
>>>> On Sun, Jan 4, 2009 at 8:36 PM, Ryo Dairiki
>>>> <[hidden email]> wrote:
>>>>
>>>>> I also think of closing forums and trackers at the same time,
>>>>> because they are no good for this small number of developers.
>>>>> I suggest all the reports be post directly here.
>>>>>
>>>>>
>>>> Do you mean that you will not use bug tracker of sourceforge and use
>>>> mailing list only?
>>>>
>>>>
>>> Yes, I do.
>>>
>>> Bug tracking systems are for cases there are many developers.
>>> It's useless if there are few people to assign the issues. :(
>>>
>>
>> I suppose that many normal users prefer bug tracker to mailing list to
>> report a bug.
>> Tracking issues is important. Without bug tracker, it is quite
>> difficult to maintain bug list and history.
>>
>
> It seems to me that you don't really understand that
> *somebody* must maintain bug list and history, with or without the bug
> tracker.
> If you dare to put me in charge of it, I would claim the following things.
>
> - Notification mails of the tracker should send to scim-devel-list, not
> to scim-users-list.
> - Posting bug reports on mailing lists should be banned.

I think these things are reasonable.

But anyway, if you don't like bug tracker so much, don't use it.

------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel

[Jens Petersen]

> The main idea is, making a strict merge window helps us (me)
> to keep release cycle constant.
> I can concentrate on one thing every month under the new developing
> policy. :)

Sounds very good to me.  Thanks for proposing this process. :)

Jens

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel