I can create an "official" account and add everyone as contributors. We can make sure that the master is on the latest version. How do we want to handle changes queued up for the next release? Just make a Version X-RC branch that has approved but not released features/fixes?
Matt On Wed, Jan 14, 2009 at 2:27 PM, Doug Barth <[email protected]> wrote: > On Jan 14, 2009, at 2:19 PM, Greg Opaczewski wrote: > > So how do we setup the "official" repo then? One of us just creates an >> account and adds all of erma-core as collaborators? I think we basically >> want a similar setup to the rails / rails repo, it's kind of confusing now >> to know where the latest version / tag resides... >> >> It would be nice to get this done and update launchpad to reflect the code >> is now hosted on Github >> > > > Yep, that's how the Rails guys did it. Other projects just designate a > single person as the official owner, but it sounds like that isn't what you > want. > > -- > Doug Barth > > > _______________________________________________ > Mailing list: > https://launchpad.net/~erma-core<https://launchpad.net/%7Eerma-core> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~erma-core<https://launchpad.net/%7Eerma-core> > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~erma-core Post to : [email protected] Unsubscribe : https://launchpad.net/~erma-core More help : https://help.launchpad.net/ListHelp
