lp:inkscape should be operational
Hey all,
Sorry to take so long on this. But, it turns out when you mess up one little thing -- you need to regen everything -- and that sucks :)
Currently there is a trunk branch from SVN in Launchpad and associated with the name "lp:inkscape". The other branches are currently uploading, and are likely to be available tonight.
I created a group for Inkscape developers: inkscape.dev[1]. Anyone in that group should have access to trunk. Anyone in the inkscape.admin[2] team should be able to add people, so if you have commit access in SF currently, grab someone on Jabber/IRC and get added to the inkscape.dev group.
If you want, you can get the same effect of the -cvs mailing list by subscribing to the trunk branch. You can then edit your e-mail settings for what mail you want to get.[3]
Lastly, some people might find the 5-minute tutorial on Bazaar.[4]
--Ted
[1] https://launchpad.net/~inkscape.dev [2] https://launchpad.net/~inkscape.admin [3] https://help.launchpad.net/Code/FindingAndDownloading#Staying%20up% 20to%20date [4] http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html
I'm currently branching locally, but assuming all goes well, we are back in business!
Ted, when branching it comments with the following: Format <RepositoryFormatKnit4> for http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
Should we avoid doing that? Just figured I would ask since I'm assuming that others will run into that message too.
Cheers, Josh
On Sat, 2009-11-28 at 14:41 -0600, Ted Gould wrote:
Hey all,
Sorry to take so long on this. But, it turns out when you mess up one little thing -- you need to regen everything -- and that sucks :)
Currently there is a trunk branch from SVN in Launchpad and associated with the name "lp:inkscape". The other branches are currently uploading, and are likely to be available tonight.
I created a group for Inkscape developers: inkscape.dev[1]. Anyone in that group should have access to trunk. Anyone in the inkscape.admin[2] team should be able to add people, so if you have commit access in SF currently, grab someone on Jabber/IRC and get added to the inkscape.dev group.
If you want, you can get the same effect of the -cvs mailing list by subscribing to the trunk branch. You can then edit your e-mail settings for what mail you want to get.[3]
Lastly, some people might find the 5-minute tutorial on Bazaar.[4]
--Ted[1] https://launchpad.net/~inkscape.dev [2] https://launchpad.net/~inkscape.admin [3] https://help.launchpad.net/Code/FindingAndDownloading#Staying%20up% 20to%20date [4] http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Sat, 2009-11-28 at 13:20 -0800, Joshua A. Andler wrote:
Ted, when branching it comments with the following: Format <RepositoryFormatKnit4> for http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
Should we avoid doing that? Just figured I would ask since I'm assuming that others will run into that message too.
Actually, probably most are not seeing it as it'll only come up with newer versions of Bazaar.
When choosing the repository format I went very conservative. Upgrading is pretty easy, but you can never go back. I figure we'd start tracking this like a dependency as it basically determines what version of Bazaar you have to have to be able to work on Inkscape. I'd like to keep that barrier as low as possible.
That being said, the new Bazaar 2.0 format is really, really sweet. I miss it already :) I hoping by the end of next year 2.0 will be common enough that we can reasonably switch.
I'm going to talk to the Bazaar team about suppressing the warning, it is annoying.
--Ted
participants (2)
-
Joshua A. Andler -
Ted Gould