[Ns-developers] How to maintain a repository for merge

[Mirko Banchi]

Tom Henderson ha scritto:
> Mirko Banchi wrote:
>> Hi all,
>>
>> i'm working to 802.11e/n support and i'd like to know how you prefer i
>> maintain my mercurial repository in order to make a possible future
>> merge easier than possible. Could a tag for every milestone be enough?
>> Or do you prefer a single repository for each feature?
>>
>> at http://code.nsnam.org/mirko/ns-3-80211n/
>> you can find the code.
>>
>> Thank you all,
>>
>> Mirko
>>
> 
> I would suggest the following:
> 
> - try to keep your repository in sync with ns-3-dev
> 
> - work with the maintainer to ask how he or she would like to proceed.
> For instance, do you agree on features, API, and general design? Can you
> define some merge points or milestones?  The maintainer should be able
> to help with overall schedule and merge considerations, deciding on
> whether separate repos are needed for each mergeable chunk, etc.
> 
> In your case, are you at the "agree on features, API, and general design
> stage" still?  I recall that you had asked some questions in your
> earlier post:
> http://mailman.isi.edu/pipermail/ns-developers/2008-December/004973.html
> and I am not sure what discussions you may have had at wns3 about some
> of these issues.
>
> Can you suggest some natural milestones in the development that might
> make smaller and earlier merges possible?
> 
> - Tom
> 

At the moment my repository includes these new features:

Edca mechanism
Frame aggregation (A-MSDU)

Clearly some examples and docs will be added.

For now i could suggest this possible milestones:

1. Edca mechanism and Frame Aggregation (A-MSDU) (current)
2. Block ack mechanism
3. Frame aggregation (A-MPDU)
4. Support for transmission of multiple frames in the same txop.

What do you think about?

Regards,
Mirko

-- 
Mirko Banchi

e-mail:    mk.banchi at gmail.com
e-mail:    mk.banchi at virgilio.it
id-jabber: mk.banchi at jabber.org
id-msn:    mb11684 at hotmail.com

PGP key fingerprint:

308F BFB1 4E67 2522 C88E
DC69 7631 52ED 32A5 6456

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3410 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mailman.isi.edu/pipermail/ns-developers/attachments/20090314/973d97ec/smime.bin