Re: [Pyblosxom-devel] pyblosxom maintenance

[Akai <ope...@gm...>]

my username is AkaiKitsune

On 6/22/2012 2:28 AM, will kahn-greene wrote:
> The release process I used is documented here:
>
> http://pyblosxom.bluesock.org/1.5/dev_release.html
>
> For that, you need a PyPI account and permisions to push new versions.
> If you have a PyPI account, I can add you.
>
> /will
>
>
> On 06/21/2012 07:07 PM, Akai wrote:
>> Do we need anything do a new release?
>> I imagine we need something to make a new version of the PIP package.
>>
>> On 6/22/2012 12:16 AM, will kahn-greene wrote:
>>> On 06/21/2012 05:00 PM, Akai wrote:
>>>> Will - If we move the site to GH-pages, could you point the old site to
>>>> the new one, or do you plan to take down the domain completely?
>>> I can redirect all traffic to the new site. That's fine.
>>>
>>>
>>>> is there a way to just backup the issue tracker?  that way we could
>>>> start fresh without all the legacy mess, but still refer back to it if
>>>> we find ourselves needing to fix something and nothing in the new
>>>> tracker or wanting to migrate more issues and you wouldn't have to host
>>>> it [and it wouldn't confuse users]
>>> I think there are like 100 users total. I don't think "confusing users"
>>> is really a problem you're going to have once the search engines figure
>>> out that things have moved.
>>>
>>> I don't think there's much useful acrhival data in the roundup tracker.
>>> I think it's best to look through it, move over whatever you think is
>>> useful, and otherwise ditch it. The useful commentary is in the git
>>> commit comments. The bug data is pretty meh.
>>>
>>> I'm not sure how I feel about backing it up and making it available.
>>> It's non-trivial work to separate out the user data from the issue data
>>> and I don't think it's responsible to be providing the user data in a
>>> public form. So I think if you can get along without it, that's the best
>>> option. If you really can't, then I'll add "figure out how to back up
>>> the roundup tracker keeping peoples' privacy in mind" to my todo list.
>>>
>>> /will
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Pyblosxom-devel mailing list
>>> Pyb...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Pyblosxom-devel mailing list
>> Pyb...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel