You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Daniel John Debrunner <dj...@debrunners.com> on 2004/08/31 20:44:28 UTC
[VOTE] Establish development model based on Apache DB guidelines
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Derby is being sponsored by the Apache DB project and the Derby status
page states 'The Apache DB project will own the Derby subproject, and
the subproject will follow the Apache DB PMC's direction'. I assume the
'will own' means if Derby graduates from incubation.
(http://incubator.apache.org/projects/derby.html)
I propose a consensus approval vote that the Derby development model
follows the guidelines defined by the Apache DB project. This will set
the initial rules for development, changes to the model could
subsequently be called for and voted on using the Derby developer
mailing list.
The guidelines are defined at http://db.apache.org/guidelines.html
There is one difference that the Derby code is in SVN and not CVS.
Note the decision making page at http://db.apache.org/decisions.html
and the Changes section on this page http://db.apache.org/source.html.
The Changes section indicates the commit model is:
(quote)
Simple patches to fix bugs can be committed then reviewed. With a
commit-then-review process, the Committer is trusted to have a high
degree of confidence in the change.
Doubtful changes, new features, and large scale overhauls need to be
discussed before committing them into the repository. Any change that
affects the semantics of an existing API function, the size of the
program, configuration data formats, or other major areas must receive
consensus approval before being committed.
(end-quote)
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBNMcLIv0S4qsbfuQRApFuAKCeBQpAaMV1+4Cf0dGZuFMWW7wBtwCgwsFk
CXOrSWMUkuY0AFfU9SpQqx8=
=PWFa
-----END PGP SIGNATURE-----
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1
I'll tally the votes on Tuesday 2004/9/7 am US/Pacific time (after the
long weekend in the USA).
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBNmAvIv0S4qsbfuQRAgOtAJ9Hu/x6fiIJxPPOiGUkeUOSDpEHSQCfd/7V
MV+A7EbZdb+BLFBSJbOkP9I=
=iZp6
-----END PGP SIGNATURE-----
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Satheesh Bandaram <sa...@Sourcery.Org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1
Satheesh
Daniel John Debrunner wrote:
| Derby is being sponsored by the Apache DB project and the Derby status
| page states 'The Apache DB project will own the Derby subproject, and
| the subproject will follow the Apache DB PMC's direction'. I assume the
| 'will own' means if Derby graduates from incubation.
| (http://incubator.apache.org/projects/derby.html)
|
| I propose a consensus approval vote that the Derby development model
| follows the guidelines defined by the Apache DB project. This will set
| the initial rules for development, changes to the model could
| subsequently be called for and voted on using the Derby developer
| mailing list.
|
| The guidelines are defined at http://db.apache.org/guidelines.html
|
| There is one difference that the Derby code is in SVN and not CVS.
|
| Note the decision making page at http://db.apache.org/decisions.html
| and the Changes section on this page http://db.apache.org/source.html.
|
| The Changes section indicates the commit model is:
|
| (quote)
|
| Simple patches to fix bugs can be committed then reviewed. With a
| commit-then-review process, the Committer is trusted to have a high
| degree of confidence in the change.
|
| Doubtful changes, new features, and large scale overhauls need to be
| discussed before committing them into the repository. Any change that
| affects the semantics of an existing API function, the size of the
| program, configuration data formats, or other major areas must receive
| consensus approval before being committed.
|
| (end-quote)
|
| Dan.
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBNhz4ENVNIY6DZ7ERAlUkAJ9VDImIvRjeLNq2blZQAm2TXacyawCgtunj
wI3zZufJa6ID75Sv5q/jfPg=
=zvjd
-----END PGP SIGNATURE-----
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Rodney Waldhoff <rw...@apache.org>.
On Wed, 1 Sep 2004, Rodent of Unusual Size wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> Daniel John Debrunner wrote:
>>
>> Ken, obviously as you know I'm new to Apache voting and so I'm not
>> really understanding your post.
>>
>> The first question is are you starting a new vote or trying to add an
>> item to the vote I started?
>
> neither, actually. :-) as podling mentor, i'm providing advice based
> on my experience. the db project has a documented and designed disparity
> between the pmc and the committer list. during incubation, podlings
> emulate pmc operation and become familiar with it via a 'ppmc' list.
> i am suggesting that the derby podling adopt a policy that all committers
> are automatically on the ppmc.
>
> i bring this up because i think the db project pages could be viewed as
> recommending that the members of the ppmc be a subset of the committer
> list.
>
>> The second is, are you voting on your issue only, or voting for the
>> issue I started the vote on? The URL after your vote is confusing me as
>> I would guess the appropriate URL for "my" vote would be
>> http://db.apache.org/guidelines.html.
>
> i am not voting; i am a mentor only, and a committer only by courtesy during
> incubation. if/when derby graduates, i expect i will no longer be a committer,
> which is appropriate since i don't know java and certainly not a db in java.
> the podling needs to be self-defining; it's part of my function to help that
> happen. i *don't* think it's part of my job to try to steer it by voting.
>
> the point i raise may not be considered directly relevant to the issue being
> voted, but i mention it because it's related. i don't think emulating *all*
> of the db project procedures is necessarily appropriate during incubation,
> since subsetting for the ppmc could be a barrier to community building.
Agreed. For the record, the committee-info file lists 11 members of the
DB-PMC. The bylaw page is outdated. I've started a thread on pmc@db to
correct that.
>
>> Sorry if these are dumb questions.
>
> no dumb questions. ignorance is curable. i only hope i have some
> appropriate medicine. :-)
> - --
> #ken P-)}
>
> Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/
> Author, developer, opinionist http://Apache-Server.Com/
>
> "Millennium hand and shrimp!"
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iQCVAwUBQTYfCZrNPMCpn3XdAQFtbQQAoekwE1VJgbuU/c8o1r183hI4Yl6d1uU6
> NLow+yY2Fb72LFOTnHbpCWkXnzkXHJiMWyYkcc29a7bkBxZ/6qTzGliB3j1KxNX4
> VmX+z+gWPfmRaj2VxFGx4jNRurpEMBWHdE0/TKU/Dv6vDEz6i9OPBC8b+2SG2IB6
> AHb1foyFo74=
> =Tms5
> -----END PGP SIGNATURE-----
>
Re: Hello
Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dibyendu Majumdar wrote:
| Dibyendu Majumdar wrote:
|
|
| Thanks for responding to my query. I had read above overview document
| already. I have started with services/cache package. Is my understanding
| correct that this implements the Buffer Cache?
The services/cache code is a component used by the buffer cache.
The services/cache is a general purpose caching mechanism that simply
caches objects that implement the Cacheable interface. It is used by the
store for buffer caching, but it is also used to cache compiled plans
for SQL statements, open containers and their file descriptors, string
conversions, table descriptors and maybe more.
The interface/implementation split ensures that the cache algorithm is
not known by the users of the cache and can be changed with affecting
them. The currrent algorithm is a "clock or ring" based algorithm.
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBOkGiIv0S4qsbfuQRAkwpAJ9qYDh6BOTHLpa9PtQ+mVelQgmp5wCgl9Bm
Wg+oa7CDngjrzfaKbezLL8w=
=oz0+
-----END PGP SIGNATURE-----
Re: Hello
Posted by Dibyendu Majumdar <di...@mazumdar.demon.co.uk>.
Dibyendu Majumdar wrote:
>
> | Hello,
> |
> | My name is Dibyendu Majumdar. I am keen on working on the Store and
> | Services layer in Derby. I would grateful for any tips on where to
> | start the process of understanding the code/design.
>
Jean wrote:
> Hi, Dibyendu,
>
> I didn't spot any followups to your question. One starting point is an
> early architecture thread here (that will hopefully get consolidated
> soon into a white paper for the site to make it easier to find):
>
>
>
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=derby-dev@db.apache.org&msgNo=18
Thanks for responding to my query. I had read above overview document
already. I have started with services/cache package. Is my understanding
correct that this implements the Buffer Cache?
Regards
Dibyendu
Re: Hello
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dibyendu Majumdar wrote:
| Hello,
|
| My name is Dibyendu Majumdar. I am keen on working on the Store and
| Services layer in Derby. I would grateful for any tips on where to
| start the process of understanding the code/design.
Hi, Dibyendu,
I didn't spot any followups to your question. One starting point is an
early architecture thread here (that will hopefully get consolidated
soon into a white paper for the site to make it easier to find):
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=derby-dev@db.apache.org&msgNo=18
regards,
~ -jean
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBOPJrF0L6u5lYbCYRAjLKAJ0WXa3m6ZeWcnb3WQZwuNstiiqAYACeNZ0C
K6dm4EMIgNldYbqJQ81kCGA=
=kg7R
-----END PGP SIGNATURE-----
Hello
Posted by Dibyendu Majumdar <di...@mazumdar.demon.co.uk>.
Hello,
My name is Dibyendu Majumdar. I am keen on working on the Store and Services
layer in Derby. I would grateful for any tips on where to start the process
of understanding the code/design.
Thanks and Regards
Dibyendu
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rodent of Unusual Size wrote:
|
| i am not voting;
OK - I see now, maybe the Peet's coffee hadn't kicked in before.
I read this line in your e-mail as a vote, not a reference.
| [1] http://db.apache.org/management.html
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBNiFJIv0S4qsbfuQRAoF9AKCuhUSZ9eZzM4b0IgKfAVkmBT/66gCeMRN0
fIZp+guMP7vgS9T+s/R5DqQ=
=3hqH
-----END PGP SIGNATURE-----
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
-----BEGIN PGP SIGNED MESSAGE-----
Daniel John Debrunner wrote:
>
> Ken, obviously as you know I'm new to Apache voting and so I'm not
> really understanding your post.
>
> The first question is are you starting a new vote or trying to add an
> item to the vote I started?
neither, actually. :-) as podling mentor, i'm providing advice based
on my experience. the db project has a documented and designed disparity
between the pmc and the committer list. during incubation, podlings
emulate pmc operation and become familiar with it via a 'ppmc' list.
i am suggesting that the derby podling adopt a policy that all committers
are automatically on the ppmc.
i bring this up because i think the db project pages could be viewed as
recommending that the members of the ppmc be a subset of the committer
list.
> The second is, are you voting on your issue only, or voting for the
> issue I started the vote on? The URL after your vote is confusing me as
> I would guess the appropriate URL for "my" vote would be
> http://db.apache.org/guidelines.html.
i am not voting; i am a mentor only, and a committer only by courtesy during
incubation. if/when derby graduates, i expect i will no longer be a committer,
which is appropriate since i don't know java and certainly not a db in java.
the podling needs to be self-defining; it's part of my function to help that
happen. i *don't* think it's part of my job to try to steer it by voting.
the point i raise may not be considered directly relevant to the issue being
voted, but i mention it because it's related. i don't think emulating *all*
of the db project procedures is necessarily appropriate during incubation,
since subsetting for the ppmc could be a barrier to community building.
> Sorry if these are dumb questions.
no dumb questions. ignorance is curable. i only hope i have some
appropriate medicine. :-)
- --
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/
Author, developer, opinionist http://Apache-Server.Com/
"Millennium hand and shrimp!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBQTYfCZrNPMCpn3XdAQFtbQQAoekwE1VJgbuU/c8o1r183hI4Yl6d1uU6
NLow+yY2Fb72LFOTnHbpCWkXnzkXHJiMWyYkcc29a7bkBxZ/6qTzGliB3j1KxNX4
VmX+z+gWPfmRaj2VxFGx4jNRurpEMBWHdE0/TKU/Dv6vDEz6i9OPBC8b+2SG2IB6
AHb1foyFo74=
=Tms5
-----END PGP SIGNATURE-----
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rodent of Unusual Size wrote:
| Daniel John Debrunner wrote:
|
|
|>Derby is being sponsored by the Apache DB project and the Derby status
|>page states 'The Apache DB project will own the Derby subproject, and
|>the subproject will follow the Apache DB PMC's direction'. I assume the
|>'will own' means if Derby graduates from incubation.
|>(http://incubator.apache.org/projects/derby.html)
|>
|>I propose a consensus approval vote that the Derby development model
|>follows the guidelines defined by the Apache DB project. This will set
|>the initial rules for development, changes to the model could
|>subsequently be called for and voted on using the Derby developer
|>mailing list.
|
|
| i personally would recommend that all committers also be part of the
| ppmc (podling pmc) whilst in the incubator. after a successful exit
| and adoption into the db project, the db project's fixed-seat
| five-person pmc[1] will ultimately have total control of all non-technical
| issues and decisions. i don't recommend that any such subsetting is
either
| appropriate or advisable while still incubating.
|
| so i would recommend the adoption of a 'the ppmc shall consist of all
| derby committers' policy for the duration of the incubation.
|
| [1] http://db.apache.org/management.html
Ken, obviously as you know I'm new to Apache voting and so I'm not
really understanding your post.
The first question is are you starting a new vote or trying to add an
item to the vote I started?
The second is, are you voting on your issue only, or voting for the
issue I started the vote on? The URL after your vote is confusing me as
I would guess the appropriate URL for "my" vote would be
http://db.apache.org/guidelines.html.
Sorry if these are dumb questions.
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBNfHOIv0S4qsbfuQRAmVqAKCJE7AGE9ikle0wYcIGfh1lNv3N8ACgyza3
swW/aBDEpx27Vao7vbUX82w=
=w2ii
-----END PGP SIGNATURE-----
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
-----BEGIN PGP SIGNED MESSAGE-----
Daniel John Debrunner wrote:
> Derby is being sponsored by the Apache DB project and the Derby status
> page states 'The Apache DB project will own the Derby subproject, and
> the subproject will follow the Apache DB PMC's direction'. I assume the
> 'will own' means if Derby graduates from incubation.
> (http://incubator.apache.org/projects/derby.html)
>
> I propose a consensus approval vote that the Derby development model
> follows the guidelines defined by the Apache DB project. This will set
> the initial rules for development, changes to the model could
> subsequently be called for and voted on using the Derby developer
> mailing list.
i personally would recommend that all committers also be part of the
ppmc (podling pmc) whilst in the incubator. after a successful exit
and adoption into the db project, the db project's fixed-seat
five-person pmc[1] will ultimately have total control of all non-technical
issues and decisions. i don't recommend that any such subsetting is either
appropriate or advisable while still incubating.
so i would recommend the adoption of a 'the ppmc shall consist of all
derby committers' policy for the duration of the incubation.
[1] http://db.apache.org/management.html
- --
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/
Author, developer, opinionist http://Apache-Server.Com/
"Millennium hand and shrimp!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBQTXdPZrNPMCpn3XdAQEbqQQAqVyHTQzKV+6+8DeFjWrfDm4UGgPofvV+
192e+PISl7Qskk1If3+1j9B1HLu/IhPjBClACWhwdFIU2MRUxTJBSrq0FHPr/V17
7odarkTJbM4P8unlQkw58M8Tx4Po6SSmSjgQwxN2KGMode5iTW52omA60rBBj1QW
Cmh9xSPyBa0=
=3GrK
-----END PGP SIGNATURE-----
[RESULT] [VOTE] Establish development model based on Apache DB guidelines
Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Six +1 votes - thus the development model is established.
Dan.
Daniel John Debrunner wrote:
> Derby is being sponsored by the Apache DB project and the Derby status
> page states 'The Apache DB project will own the Derby subproject, and
> the subproject will follow the Apache DB PMC's direction'. I assume the
> 'will own' means if Derby graduates from incubation.
> (http://incubator.apache.org/projects/derby.html)
>
> I propose a consensus approval vote that the Derby development model
> follows the guidelines defined by the Apache DB project. This will set
> the initial rules for development, changes to the model could
> subsequently be called for and voted on using the Derby developer
> mailing list.
>
> The guidelines are defined at http://db.apache.org/guidelines.html
>
> There is one difference that the Derby code is in SVN and not CVS.
>
> Note the decision making page at http://db.apache.org/decisions.html
> and the Changes section on this page http://db.apache.org/source.html.
>
> The Changes section indicates the commit model is:
>
> (quote)
>
> Simple patches to fix bugs can be committed then reviewed. With a
> commit-then-review process, the Committer is trusted to have a high
> degree of confidence in the change.
>
> Doubtful changes, new features, and large scale overhauls need to be
> discussed before committing them into the repository. Any change that
> affects the semantics of an existing API function, the size of the
> program, configuration data formats, or other major areas must receive
> consensus approval before being committed.
>
> (end-quote)
>
> Dan.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBPepLIv0S4qsbfuQRAsdTAKCWluao9aLBxoYhwV66UlgTLCfvjQCgwssm
0gwpxLLw2vKfhyMNLAZA6kc=
=TTDd
-----END PGP SIGNATURE-----
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Mike Matrigali <mi...@sbcglobal.net>.
+1
Daniel John Debrunner wrote:
> Derby is being sponsored by the Apache DB project and the Derby status
> page states 'The Apache DB project will own the Derby subproject, and
> the subproject will follow the Apache DB PMC's direction'. I assume the
> 'will own' means if Derby graduates from incubation.
> (http://incubator.apache.org/projects/derby.html)
>
> I propose a consensus approval vote that the Derby development model
> follows the guidelines defined by the Apache DB project. This will set
> the initial rules for development, changes to the model could
> subsequently be called for and voted on using the Derby developer
> mailing list.
>
> The guidelines are defined at http://db.apache.org/guidelines.html
>
> There is one difference that the Derby code is in SVN and not CVS.
>
> Note the decision making page at http://db.apache.org/decisions.html
> and the Changes section on this page http://db.apache.org/source.html.
>
> The Changes section indicates the commit model is:
>
> (quote)
>
> Simple patches to fix bugs can be committed then reviewed. With a
> commit-then-review process, the Committer is trusted to have a high
> degree of confidence in the change.
>
> Doubtful changes, new features, and large scale overhauls need to be
> discussed before committing them into the repository. Any change that
> affects the semantics of an existing API function, the size of the
> program, configuration data formats, or other major areas must receive
> consensus approval before being committed.
>
> (end-quote)
>
> Dan.
>
>
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Kathey Marsden <km...@Sourcery.Org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel John Debrunner wrote:
| Derby is being sponsored by the Apache DB project and the Derby status
| page states 'The Apache DB project will own the Derby subproject, and
| the subproject will follow the Apache DB PMC's direction'. I assume the
| 'will own' means if Derby graduates from incubation.
| (http://incubator.apache.org/projects/derby.html)
|
| I propose a consensus approval vote that the Derby development model
| follows the guidelines defined by the Apache DB project. This will set
| the initial rules for development, changes to the model could
| subsequently be called for and voted on using the Derby developer
| mailing list.
|
| The guidelines are defined at http://db.apache.org/guidelines.html
|
| There is one difference that the Derby code is in SVN and not CVS.
|
| Note the decision making page at http://db.apache.org/decisions.html
| and the Changes section on this page http://db.apache.org/source.html.
|
| The Changes section indicates the commit model is:
|
| (quote)
|
| Simple patches to fix bugs can be committed then reviewed. With a
| commit-then-review process, the Committer is trusted to have a high
| degree of confidence in the change.
|
| Doubtful changes, new features, and large scale overhauls need to be
| discussed before committing them into the repository. Any change that
| affects the semantics of an existing API function, the size of the
| program, configuration data formats, or other major areas must receive
| consensus approval before being committed.
|
| (end-quote)
|
| Dan.
|
|
+1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBNfrGG0h36bFmkocRAkqhAJ9TDtcOgU3VmON/FW97oAPl5gosRQCfXqi/
rISBVSw0+rySmU+40SquvhY=
=t9OG
-----END PGP SIGNATURE-----
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by Samuel Andrew McIntyre <fu...@nonintuitive.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1 for following the db.apache.org model for changes.
On Aug 31, 2004, at 11:44 AM, Daniel John Debrunner wrote:
> Note the decision making page at http://db.apache.org/decisions.html
> and the Changes section on this page http://db.apache.org/source.html.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFBNSUbDfB0XauCH7wRAq2QAJ9tPEcFz21R2x6x3OhDktBCYLDTkwCeMq4+
vkbj11qer1rw8ZHjrewwmf4=
=uQ6M
-----END PGP SIGNATURE-----
Re: [VOTE] Establish development model based on Apache DB guidelines
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1
~ -jean
Daniel John Debrunner wrote:
| Derby is being sponsored by the Apache DB project and the Derby
| status page states 'The Apache DB project will own the Derby
| subproject, and the subproject will follow the Apache DB PMC's
| direction'. I assume the 'will own' means if Derby graduates from
| incubation. (http://incubator.apache.org/projects/derby.html)
|
| I propose a consensus approval vote that the Derby development
| model follows the guidelines defined by the Apache DB project. This
| will set the initial rules for development, changes to the model
| could subsequently be called for and voted on using the Derby
| developer mailing list.
|
| The guidelines are defined at http://db.apache.org/guidelines.html
|
| There is one difference that the Derby code is in SVN and not CVS.
|
| Note the decision making page at
| http://db.apache.org/decisions.html and the Changes section on this
| page http://db.apache.org/source.html.
|
| The Changes section indicates the commit model is:
|
| (quote)
|
| Simple patches to fix bugs can be committed then reviewed. With a
| commit-then-review process, the Committer is trusted to have a high
| degree of confidence in the change.
|
| Doubtful changes, new features, and large scale overhauls need to
| be discussed before committing them into the repository. Any change
| that affects the semantics of an existing API function, the size of
| the program, configuration data formats, or other major areas must
| receive consensus approval before being committed.
|
| (end-quote)
|
| Dan.
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBNf4HF0L6u5lYbCYRArUCAJ9lsfy38rPPjOI3sbDOlerCCf5i/wCfVpaa
0r25YGk36jOluruhmVvRz7Q=
=dLxK
-----END PGP SIGNATURE-----