[ros-users] serial_communication release

[Ken Conley]

2012/2/9 Gonçalo Cabrita <goncabrita at gmail.com>:
>
> Thanks Ken, I'm trying to be very careful about this since I've read something about blacklisting n' all and this is all new to me! :D

Sounds like what you read is more fearful than reality.

If your stack builds, we keep building it.  If it stops building for a
prolonged period of time, we stop building it.  That's about it.

Separately, we do remove repositories from our indexer if:

 a) they get really, really huge (i.e. 1GB checkout size)
 b) they contain package names that collide with pre-existing packages

In either of those cases, the repository maintainer is notified, and
the repo is reindexed once those issues are corrected.

 - Ken

>
> I've just finished re-structuring the repository to allow for the same rules to apply to all the stacks, also it looks cleaner now.
>
> Thanks for the help,
>
> Gonçalo Cabrita
> ISR University of Coimbra
> Portugal
>
>
> On Feb 9, 2012, at 7:17 PM, Ken Conley wrote:
>
>> 2012/2/9 Gonçalo Cabrita <goncabrita at gmail.com>:
>>> Hi Ken,
>>>
>>> Thanks for your reply!
>>>
>>> So let me see if I got this right, if I use the $STACK_NAME variable this will work for all the stack in the repository that I release in the future right?
>>
>> Yes, assuming that the URL patterns are consistent for all of those stacks.
>>
>> - Ken
>>
>>> In that case the rules apply for all the repository and not just for a specific stack, depending ofc on the stacks I choose to release using rosrun release …, right?
>>>
>>> Thanks and best regards,
>>>
>>> Gonçalo Cabrita
>>> ISR University of Coimbra
>>> Portugal
>>>
>>>
>>> On Feb 9, 2012, at 6:54 PM, Ken Conley wrote:
>>>
>>>> The rules look fine.  You could always save yourself future effort by
>>>> using $STACK_NAME instead of 'serial_communication' in the rule.
>>>>
>>>> - Ken
>>>>
>>>> 2012/2/9 Gonçalo Cabrita <goncabrita at gmail.com>:
>>>>> Hi everyone,
>>>>>
>>>>> I'm trying to do a release of serial_communication
>>>>> (http://www.ros.org/wiki/serial_communication) but I'm having some doubts
>>>>> about the whole process (and I'd love not to screw up on my first release!).
>>>>>
>>>>> I still need to re-arrange the repository to match the following URLs, still
>>>>> would the following rules be correct to add to the unstable.rosdistro file?
>>>>>
>>>>> serial_communication:
>>>>>    svn: {dev:
>>>>> 'https://isr-uc-ros-pkg.googlecode.com/svn/stacks/serial_communication/trunk',
>>>>> distro-tag:
>>>>> 'https://isr-uc-ros-pkg.googlecode.com/svn/stacks/serial_communication/tags/$RELEASE_NAME',
>>>>>      release-tag:
>>>>> 'https://isr-uc-ros-pkg.googlecode.com/svn/stacks/serial_communication/tags/serial_communication-$STACK_VERSION'}
>>>>>
>>>>>
>>>>> I dont intend to release the whole repo, only the serial_communication stack
>>>>> so I'm using the stack name instead of a variable. However I'm keeping the
>>>>> variables for the release version and for the stack version. Is this
>>>>> correct?
>>>>>
>>>>> Thanks for the help in advance!
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Gonçalo Cabrita
>>>>> ISR University of Coimbra
>>>>> Portugal
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> ros-users mailing list
>>>>> ros-users at code.ros.org
>>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>>>
>>>> _______________________________________________
>>>> ros-users mailing list
>>>> ros-users at code.ros.org
>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>
>>> _______________________________________________
>>> ros-users mailing list
>>> ros-users at code.ros.org
>>> https://code.ros.org/mailman/listinfo/ros-users
>> _______________________________________________
>> ros-users mailing list
>> ros-users at code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users